You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/10/15 09:45:11 UTC
[jira] Closed: (MEV-106) Wront JUnit scope dependency in some poms
[ http://jira.codehaus.org/browse/MEV-106?page=all ]
Brett Porter closed MEV-106:
----------------------------
Assign To: Brett Porter
Resolution: Fixed
> Wront JUnit scope dependency in some poms
> -----------------------------------------
>
> Key: MEV-106
> URL: http://jira.codehaus.org/browse/MEV-106
> Project: Maven Evangelism
> Type: Improvement
> Components: Dependencies
> Reporter: Jean-Laurent
> Assignee: Brett Porter
>
>
> JUnit is stated as a compile dependency (no scope tag) where is should be under the "test" scope.
> At least in the following poms :
> - commons-beanutils-1.6.1.pom
> - commons-collections-3.0.pom
> - commons-digester-1.5.pom
> - commons-logging-1.0.3.pom
> This leads JUnit jar to be bundled within war file on maven2 enabled web project.
> Workaround :
> Modifying locally the above poms by adding <scope>test</scope> within the dependencies JUnit dependency.
--
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