You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Falko Modler (JIRA)" <ji...@apache.org> on 2011/02/17 22:06:12 UTC

[jira] Commented: (WW-3528) Move maven dependency junit:junit:3.8.2 from scope 'compile' to scope 'test'

    [ https://issues.apache.org/jira/browse/WW-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996074#comment-12996074 ] 

Falko Modler commented on WW-3528:
----------------------------------

I just came across that when checking the contents of our webproject's lib folder.

Struts 2.2.1.1, struts2-sitemesh-plugin.


Please fix this.

> Move maven dependency junit:junit:3.8.2 from scope 'compile' to scope 'test'
> ----------------------------------------------------------------------------
>
>                 Key: WW-3528
>                 URL: https://issues.apache.org/jira/browse/WW-3528
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Build Management
>         Environment: All
>            Reporter: rrrrutdk
>
> org.apache.struts:struts2-plugins:pom
> adds
> junit:junit:3.8.2
> as a test dependency, but declared the dependency in scope 'compile'.
> all my projects using or referencing struts2-plugins.pom have to exclude the annoying test dependency like this:
> <exclusions>
>      <exclusion>
>          <groupId>junit</groupId>
>          <artifactId>junit</artifactId>
>      </exclusion>
> </exclusions>
> i had been troubled by this issue since struts2 2.0.x.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira