You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/19 19:51:00 UTC

[jira] [Commented] (SUREFIRE-1298) surefire-junit4 contains commons-io 2.2 pom.xml

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

Elliotte Rusty Harold commented on SUREFIRE-1298:
-------------------------------------------------

we shouldn't need to shade commons-io. We can just use it directly.

> surefire-junit4 contains commons-io 2.2 pom.xml
> -----------------------------------------------
>
>                 Key: SUREFIRE-1298
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1298
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.x support
>    Affects Versions: 2.19.1
>            Reporter: Thomas Mortagne
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: Backlog
>
>
> For some reason surefire-junit4 jar ends up with {{/META-INF/maven/commons-io/commons-io/pom.xml}} (and {{pom.properties}}).
> The issue is that I have some code scanning classloader jars to find out what's there and I end up with a conflict in all my unit tests between commons-io 2.9 in commons-io jar I'm depending on and commons-io 2.2 which is supposed to be in surefire-junit4 jar.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)