Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Sample maven config doesn't output default artifact #18

Open
JJWTimmer opened this issue Aug 29, 2017 · 1 comment
Open

Sample maven config doesn't output default artifact #18

JJWTimmer opened this issue Aug 29, 2017 · 1 comment

Comments

@JJWTimmer
Copy link

I believe that, at least with the multi module maven example, there is something wrong. When I execute mvn clean install I end up with scoverage-module1-1.0.0.jar and not module1-1.0.0.jar so I guess this is either the instrumented version or the file suddenly has a wrong name.

Is this expected behavior? How do I get my production ready jars again?
@JJWTimmer
Copy link
Author

I have to correct myself. I changed scoverage-maven-plugin version from 1.0.4 to 1.1.0-1.3.0 and all those versions output the 'wrong' artifact name. I reverted to 1.0.4 for now, but I'm not sure what is in the jar now, is that instrumented? How to output instrumented and non-instrumented jars?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JJWTimmer