You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Bruce Phillips (JIRA)" <ji...@apache.org> on 2013/07/17 16:48:52 UTC

[jira] [Comment Edited] (WW-4127) different commons-io versions in struts2-core

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

Bruce Phillips edited comment on WW-4127 at 7/17/13 2:46 PM:
-------------------------------------------------------------

struts2/pom.xml updated version to 2.2 for commons-io
                
      was (Author: bphillips):
    struts2/pom.xml updated version to 2.2 for commons-ii
                  
> different commons-io versions in struts2-core
> ---------------------------------------------
>
>                 Key: WW-4127
>                 URL: https://issues.apache.org/jira/browse/WW-4127
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Build Management
>    Affects Versions: 2.3.15
>         Environment: Maven
>            Reporter: Gabriel Belingueres
>            Assignee: Bruce Phillips
>            Priority: Minor
>             Fix For: 2.3.16
>
>
> Hi!
> the commons-io component is a dependency of both commons-fileupload-1.3 (commons-io-2.2) and struts2-core (commons-io 2.0.1) which is inherited from struts2-parent's pom.xml file.
> This may lead to subtle bugs since maven select by default the "highest in the tree" of dependencies (which in this case resolves to version 2.0.1).
> A workaround exists by adding the correct commons-io version in the dependencyManagement section of your project's pom.xml file:
>   <dependencyManagement>
>     <dependencies>
>       <dependency>
>         <groupId>commons-io</groupId>
>         <artifactId>commons-io</artifactId>
>         <version>2.2</version>
>       </dependency>
>     </dependencies>
>   </dependencyManagement>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira