[
https://issues.apache.org/jira/browse/MTOMCAT-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580736#comment-13580736
]
Tim Astle commented on MTOMCAT-208:
-----------------------------------
If anyone has any suggestions on the best way to approach this, let me know.
We're willing to put some time into fixing this. Ideally we'd like to get this
into the 2.1 release.
> JaCoCo instrumentation errors when running StandaloneWarMojo
> ------------------------------------------------------------
>
> Key: MTOMCAT-208
> URL: https://issues.apache.org/jira/browse/MTOMCAT-208
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
> Components: tomcat7
> Affects Versions: 2.1
> Reporter: Tim Astle
> Assignee: Olivier Lamy (*$^¨%`£)
> Attachments: StandaloneWarMojo.java.patch
>
>
> We've run into issues with using the plugin with jacoco for code coverage
> getting instrumentation errors on classes (saying they've already been
> instrumented). We found that this was due to how the exec-war and
> standalone-war goals work because they fork and start a new package phase (at
> least from what I've read that's what they're doing), so it's getting
> executed twice and the second time when it tries to instrument the classes it
> gets the errors. I found this doesn't occur with the exec-war-only goal, so
> I updated the StandaloneWarMojo class to not have the @Execute(phase =
> LifeCyclePhase.PACKAGE) annotation on it and that appeared to resolve the
> issue. Not sure if it would make more sense to add another goal such as
> 'standalone-war-only' and keep the existing standalone-war or not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
