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

Andy Seaborne commented on JENA-2137:
-------------------------------------

There are several of these: all to do with "scope=provided" in dependency jars.

Related to org.osgi.core: log4j, commons-codec, 

Related to the servlet API: commons-fileupload, Shiro web, Eclipse jetty

The build breaking because of unused scope=provided in dependencies somewhat 
devalues the {{<dependencyConvergence/>}} rule in maven-enforcer-plugin v3.0.0.


> Enforcer plugin dependency convergence errors on scope=provider
> ---------------------------------------------------------------
>
>                 Key: JENA-2137
>                 URL: https://issues.apache.org/jira/browse/JENA-2137
>             Project: Apache Jena
>          Issue Type: Bug
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Major
>             Fix For: Jena 4.2.0
>
>
> After updating: (probably the enforce plugin itself - the non-convergence 
> seems to be there before)
> Updating has causes an enforcer violation:
> {noformat}
> Dependency convergence error for org.osgi:org.osgi.core:jar:4.3.1:provided 
> paths to dependency are:
> +-org.apache.jena:jena-base:jar:4.2.0-SNAPSHOT
>   +-org.apache.logging.log4j:log4j-api:jar:2.14.1:compile
>     +-org.osgi:org.osgi.core:jar:4.3.1:provided
> and
> +-org.apache.jena:jena-base:jar:4.2.0-SNAPSHOT
>   +-org.apache.logging.log4j:log4j-core:jar:2.14.1:compile
>     +-org.osgi:org.osgi.core:jar:4.3.1:provided
> and
> +-org.apache.jena:jena-base:jar:4.2.0-SNAPSHOT
>   +-org.apache.commons:commons-compress:jar:1.21:compile
>     +-org.osgi:org.osgi.core:jar:6.0.0:provided
> {noformat}
> Looking at the log4j2 POM, the OSGi dependency is intentionally an old 
> version - minimum supported.



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

Reply via email to