I'm not able to have code coverage and deploy un-instrumented jars on same maven build
By what says here:
I should able to achieve that by using clover2:intstrument and / or clover2:instrument-test but it does not provides much more details.
If I execute something like this:
mvn -e -U -Pcoverage clean compile clover2:instrument-test test clover2:clover package
maven only produces instarumented jars in a specific location but no un-instrumented jars are produced (so packaging fails)
How can I have instrumented classes for clover to provide coverage but package un-instrumented classes in the default location ?
instrument-testgoal forks the lifecycle and runs only to
testphase because of which it's not present during
packagephase, in order to generate jar with cloverized source code you shall use
instrumentmay cause calling this phase multiple times which is not necessary, because
instrumentforks the build lifecycle.
If that won't help, here's couple of additional questions to help determining what's going wrong in your env:
coverageprofile ? Could you pass a snippet here ?
Instrumentmojo forks a lifecycle so it should not affect your normal build.
If you want to use newest Clover (currently 4.1.1) you have to redefine all references to
clover-maven-plugin and call Clover goals by
clover name, e.g
clover:instrument, more info accessible here
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs