Uploaded image for project: 'Clover'
  1. Clover
  2. CLOV-106

Allow <testsources/> fileset to also take a path ref

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • won't fix
    • Ant Tasks
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Investigate the possibility of allowing the testsources fileset to also take path refid.

            [CLOV-106] Allow <testsources/> fileset to also take a path ref

            Nick added a comment -

            An nested PatternSet should be used to do this.

            Also, the need to specify <testsources/> is now longer necessary in most cases.

            Nick added a comment - An nested PatternSet should be used to do this. Also, the need to specify <testsources/> is now longer necessary in most cases.

            Greg Allen added a comment -

            Already able to do something equivalent using fileset id/refid:

            <clover-setup enabled="${clover.enabled}" initstring="${clover.db}">
            <testsources id="clover.testsources" dir="${basedir}">
            <include name="/test/java//.java" />

            <clover-report>
            <current ...>
            <testsources refid="clover.testsources" />

            Greg Allen added a comment - Already able to do something equivalent using fileset id/refid: <clover-setup enabled="${clover.enabled}" initstring="${clover.db}"> <testsources id="clover.testsources" dir="${basedir}"> <include name=" /test/java/ / .java" /> <clover-report> <current ...> <testsources refid="clover.testsources" />

              npellow Nick
              npellow Nick
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: