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.

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

maven code coverage needs fixing #226

Open
tcurdt opened this issue Jan 16, 2016 · 5 comments
Open

maven code coverage needs fixing #226

tcurdt opened this issue Jan 16, 2016 · 5 comments

Comments

@tcurdt
Copy link
Owner

tcurdt commented Jan 16, 2016

test are being called multiple times.
the test from the invoker plugin does not generate coverage.

@tmortagne
Copy link
Collaborator

the test from the invoker plugin do not generate coverage.

Those are probably executed in a different Maven/JVM build.

@tcurdt
Copy link
Owner Author

tcurdt commented Jan 17, 2016

@tmortagne Yes, that's probably what it is - but that build just also needs the java agent specified and should work. I found a couple of different examples around and tried to mimic their config - no luck so far.

I think https://github.com/tcurdt/jdeb/blob/master/pom.xml#L284 is what should make it work.

@cvgaviao
Copy link

Normally this kind of issue is related to a duplication of execution tag. when instead of overriding a parent execution (with same id) a new one is added.

@tcurdt
Copy link
Owner Author

tcurdt commented Jan 17, 2016

@cvgaviao the lack of integration test coverage is the main issue though

@cvgaviao
Copy link

@tcurdt have you heard about takari testing (https://github.com/takari/takari-plugin-testing-project)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants