tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Lamy (*$^¨%`£) (JIRA) <>
Subject [jira] [Commented] (MTOMCAT-208) JaCoCo instrumentation errors when running StandaloneWarMojo
Date Mon, 18 Feb 2013 20:47:12 GMT


Olivier Lamy (*$^¨%`£) commented on MTOMCAT-208:

standalone-war-only sounds a better approach for me.
The current one fork a lifecycle which is correct for when you use: mvn tomcat7:standalone-war

Can you provide a patch ? (for both tomcat 6 and 7)
> JaCoCo instrumentation errors when running StandaloneWarMojo
> ------------------------------------------------------------
>                 Key: MTOMCAT-208
>                 URL:
>             Project: Apache Tomcat Maven Plugin
>          Issue Type: Improvement
>          Components: tomcat7
>    Affects Versions: 2.1
>            Reporter: Tim Astle
>            Assignee: Olivier Lamy (*$^¨%`£)
>         Attachments:
> 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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message