[
https://issues.apache.org/jira/browse/WW-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13711145#comment-13711145
]
Bruce Phillips commented on WW-4127:
------------------------------------
I updated struts2/pom.xml -
<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<version>2.0.1</version>
</dependency>
to
<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<version>2.2</version>
</dependency>
I ran all the unit tests and everything passed except these 6 (which I don't
believe is related to the change to commons-io version as they failed before
the change also).
testIndexPage(org.apache.struts2.portlet.test.Struts2PortletTest)
testFormExample(org.apache.struts2.portlet.test.Struts2PortletTest)
testValidationExample(org.apache.struts2.portlet.test.Struts2PortletTest)
testValidationErrorMessagesStickBetweenWindowStateChanges(org.apache.struts2.portlet.test.Struts2PortletTest)
testTokenExample(org.apache.struts2.portlet.test.Struts2PortletTest)
testSwitchFromViewToEditShouldGoToDefaultEditPage(org.apache.struts2.portlet.test.Struts2PortletTest)
The 2.2 version of commons-io does have a dependency on junit 4.10 instead of
junit 4.8.2 but the scope is test so that should not cause any issues.
I've committed the struts2/pom.xml change to svn.
> 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
