• Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: Low Low
    • 3.1.12
    • 3.1.7
    • Groovy, Maven plugin
    • None

          [CLOV-1278] test forked-lifecycle

          Marek Parfianowicz added a comment - - edited

          tested with clover-instr and:

          • .java in src/main/java, no groovy
          • .java/.groovy in src/main/java
          • .java in src/main/java, .groovy in src/main/groovy, no build-helper-maven-plugin
          • .java in src/main/java, .groovy in src/main/groovy, with build-helper-maven-plugin
          • .java in src/main/java, .groovy in src/main/groovy, with build-helper-maven-plugin, with JAXB sources generated in target/generated-sources/xjc
            does not work in a forked lifecycle, reason: JAXB is adding source folder after clover2:instrument goal, thus Clover is unable to filter it out, we end up with classes in two folders passed to compiler; workaround: just use clover2:setup

          Marek Parfianowicz added a comment - - edited tested with clover-instr and: .java in src/main/java, no groovy .java/.groovy in src/main/java .java in src/main/java, .groovy in src/main/groovy, no build-helper-maven-plugin .java in src/main/java, .groovy in src/main/groovy, with build-helper-maven-plugin .java in src/main/java, .groovy in src/main/groovy, with build-helper-maven-plugin, with JAXB sources generated in target/generated-sources/xjc does not work in a forked lifecycle, reason: JAXB is adding source folder after clover2:instrument goal, thus Clover is unable to filter it out, we end up with classes in two folders passed to compiler; workaround: just use clover2:setup

            mparfianowicz Marek Parfianowicz
            mparfianowicz Marek Parfianowicz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: