Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Date: Mon, 18 Feb 2013 20:47:13 +0000 (UTC)
From: =?utf-8?Q?Olivier_Lamy_=28*=24=5E=C2=A8=25=60=C2=A3=29_=28JIRA=29?=
 <jira@apache.org>
To: dev@tomcat.apache.org
Message-ID: <JIRA.12632867.1361209851555.302645.1361220433078@arcas>
In-Reply-To: <JIRA.12632867.1361209851555@arcas>
References: <JIRA.12632867.1361209851555@arcas>
Subject: [jira] [Updated] (MTOMCAT-208) JaCoCo instrumentation errors when
 running StandaloneWarMojo
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/MTOMCAT-208?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy (*$^=C2=A8%`=C2=A3) updated MTOMCAT-208:
-------------------------------------------

      Component/s: tomcat6
    Fix Version/s: 2.1
   =20
> 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: tomcat6, tomcat7
>    Affects Versions: 2.1
>            Reporter: Tim Astle
>            Assignee: Olivier Lamy (*$^=C2=A8%`=C2=A3)
>             Fix For: 2.1
>
>         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 ins=
trumented).  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 fr=
om what I've read that's what they're doing), so it's getting executed twic=
e and the second time when it tries to instrument the classes it gets the e=
rrors.  I found this doesn't occur with the exec-war-only goal, so I update=
d the StandaloneWarMojo class to not have the @Execute(phase =3D LifeCycleP=
hase.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-w=
ar-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 administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org