[ http://issues.apache.org/struts/browse/WW-1431?page=comments#action_38194
]
Wendy Smoak commented on WW-1431:
---------------------------------
Then I think it should be marked 'optional'. You don't want to bring JUnit
into every project that uses XWork. In most cases people will already have
JUnit declared in test scope and Maven will do the right thing, but if someone
is using some other test framework, they will have to use an exclusion to get
rid of junit.
>From the Struts 1 struts-core (which also includes test classes) pom:
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<optional>true</optional>
</dependency>
> xwork 2.0's pom.xml has junit listed as a compile-time dependency, should be
> test (?)
> -------------------------------------------------------------------------------------
>
> Key: WW-1431
> URL: http://issues.apache.org/struts/browse/WW-1431
> Project: Struts 2
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.0.0
> Reporter: Matt Raible
> Assigned To: Don Brown
>
> When I run mvn in my project, I see:
> [WARNING]
> Artifact junit:junit:jar:3.8.1:test retains local scope 'test'
> overriding broader scope 'compile'
> given by a dependency. If this is not intended, modify or remove the
> local scope.
> This seems to be caused by XWork:
> opensymphony:xwork:jar:2.0-SNAPSHOT:compile (selected for compile)
> [DEBUG] junit:junit:jar:3.8.1:compile (selected for compile)
> [DEBUG] opensymphony:oscore:jar:2.2.4:compile (selected for compile)
> [DEBUG] ognl:ognl:jar:2.6.7:compile (selected for compile)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
