You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2020/08/20 15:23:00 UTC
[jira] [Commented] (SLING-9607) Fix conflicting dependency to
commons-io where two different versions are listed
[ https://issues.apache.org/jira/browse/SLING-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181266#comment-17181266 ]
Radu Cotescu commented on SLING-9607:
-------------------------------------
[~enorman], is there a reason to release this fix in 2.3.4? :D
> Fix conflicting dependency to commons-io where two different versions are listed
> --------------------------------------------------------------------------------
>
> Key: SLING-9607
> URL: https://issues.apache.org/jira/browse/SLING-9607
> Project: Sling
> Issue Type: Bug
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
> Fix For: Scripting Core 2.3.2
>
>
> Fix conflicting dependency to commons-io where two different versions are listed causing the following warning in the build:
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for org.apache.sling:org.apache.sling.scripting.core:jar:2.3.1-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: commons-io:commons-io:jar -> version 2.6 vs 2.4 @ line 209, column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
> [WARNING]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)