You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jean-Laurent (JIRA)" <ji...@codehaus.org> on 2005/10/09 18:56:11 UTC
[jira] Created: (MEV-106) Wront JUnit scope dependency in some poms
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
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
[jira] Commented: (MEV-106) Wront JUnit scope dependency in some poms
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-106?page=comments#action_48264 ]
Carlos Sanchez commented on MEV-106:
------------------------------------
http://issues.apache.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=casesubstring&short_desc=Improvements+to+maven+build&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=
> 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
>
>
> 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
[jira] Updated: (MEV-106) Wront JUnit scope dependency in some poms
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-106?page=all ]
Carlos Sanchez updated MEV-106:
-------------------------------
Comment: was deleted
> 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
>
>
> 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
[jira] Commented: (MEV-106) Wront JUnit scope dependency in some poms
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-106?page=comments#action_48265 ]
Carlos Sanchez commented on MEV-106:
------------------------------------
http://issues.apache.org/bugzilla/show_bug.cgi?id=37007
http://issues.apache.org/bugzilla/show_bug.cgi?id=37011
http://issues.apache.org/bugzilla/show_bug.cgi?id=37012
http://issues.apache.org/bugzilla/show_bug.cgi?id=37013
http://issues.apache.org/bugzilla/show_bug.cgi?id=37014
> 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
>
>
> 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
[jira] Closed: (MEV-106) Wront JUnit scope dependency in some poms
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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