You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2006/01/25 22:58:07 UTC
[jira] Created: (MSUREFIRE-51) Add a configuration element which
allows artifact exclusions
Add a configuration element which allows artifact exclusions
------------------------------------------------------------
Key: MSUREFIRE-51
URL: http://jira.codehaus.org/browse/MSUREFIRE-51
Project: Maven 2.x Surefire Plugin
Type: New Feature
Reporter: Jason van Zyl
Taken from the message on the users mailing list:
This smells like a scoping problem. ASM is not required for test execution (runtime) by Cobertura, ASM is only needed for swizzling the class files and that part is run during the process-classes phase. Cobertura itself needs it to compile and to instrument but ASM shouldn't end up in the test or runtime scopes/classpaths. I think this points to a tool scope or something akin to it.
If that proves to be the case it's probably not going to be fixed for 2.0.3.
A solution might be to add an artifact exclusion configuration to surefire (possibly only for forking mode). Then the lifecycle.xml for the Cobertura plug-in which controls the execution of surefire could exclude ASM during test runs. That could probably make it into the surefire plug-in's next release if that solution works. That's all I can think of off the top of my head.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MSUREFIRE-51) Add a configuration element which
allows artifact exclusions
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-51?page=all ]
Brett Porter closed MSUREFIRE-51:
---------------------------------
Assign To: Brett Porter
Resolution: Won't Fix
this was a problem in cobertura, which has been fixed.
> Add a configuration element which allows artifact exclusions
> ------------------------------------------------------------
>
> Key: MSUREFIRE-51
> URL: http://jira.codehaus.org/browse/MSUREFIRE-51
> Project: Maven 2.x Surefire Plugin
> Type: New Feature
> Reporter: Jason van Zyl
> Assignee: Brett Porter
>
>
> Taken from the message on the users mailing list:
> This smells like a scoping problem. ASM is not required for test execution (runtime) by Cobertura, ASM is only needed for swizzling the class files and that part is run during the process-classes phase. Cobertura itself needs it to compile and to instrument but ASM shouldn't end up in the test or runtime scopes/classpaths. I think this points to a tool scope or something akin to it.
> If that proves to be the case it's probably not going to be fixed for 2.0.3.
> A solution might be to add an artifact exclusion configuration to surefire (possibly only for forking mode). Then the lifecycle.xml for the Cobertura plug-in which controls the execution of surefire could exclude ASM during test runs. That could probably make it into the surefire plug-in's next release if that solution works. That's all I can think of off the top of my head.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org