How to solve dependency convergence issue

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

How to solve dependency convergence issue

Niranjan Rao-2
Greetings,


I am using maven-enforcer-plugin to ensure only one version of jar files
is loaded. In case of conflicts, I normally would use exclusions to weed
out unwanted jars. Normally I would pick latest version of library.

I am not clear how to solve following problem reported by maven enforcer
plugin. I am adding dependency on org.hibernate:hibernate-core which in
turn has dependency on
org.hibernate.common:hibernate-commons-annotations. Both these are
pulling different versions on jboss-logging.


If I add exclusion on jboss-logging, which will get dropped? How do I
force to drop dependency from
org.hibernate.common:hibernate-commons-annotations where it seems to be
using older version.


Dependency convergence error for
org.jboss.logging:jboss-logging:3.3.1.Final paths to dependency are:
+group:artifcat:version
   +-org.hibernate:hibernate-core:5.2.14.Final
     +-org.jboss.logging:jboss-logging:3.3.1.Final
and
+group:artifcat:version
   +-org.hibernate:hibernate-core:5.2.14.Final
+-org.hibernate.common:hibernate-commons-annotations:5.0.1.Final
       +-org.jboss.logging:jboss-logging:3.3.0.Final


Thanks,


Niranjan


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How to solve dependency convergence issue

Anders Hammar
This shouldn't be solved via exclusions but rather by specifying the wanted
version in the dependencyManagement section of your project.

/Anders

On Tue, Mar 6, 2018 at 10:37 PM, Niranjan Rao <[hidden email]> wrote:

> Greetings,
>
>
> I am using maven-enforcer-plugin to ensure only one version of jar files
> is loaded. In case of conflicts, I normally would use exclusions to weed
> out unwanted jars. Normally I would pick latest version of library.
>
> I am not clear how to solve following problem reported by maven enforcer
> plugin. I am adding dependency on org.hibernate:hibernate-core which in
> turn has dependency on org.hibernate.common:hibernate-commons-annotations.
> Both these are pulling different versions on jboss-logging.
>
>
> If I add exclusion on jboss-logging, which will get dropped? How do I
> force to drop dependency from org.hibernate.common:hibernate-commons-annotations
> where it seems to be using older version.
>
>
> Dependency convergence error for org.jboss.logging:jboss-logging:3.3.1.Final
> paths to dependency are:
> +group:artifcat:version
>   +-org.hibernate:hibernate-core:5.2.14.Final
>     +-org.jboss.logging:jboss-logging:3.3.1.Final
> and
> +group:artifcat:version
>   +-org.hibernate:hibernate-core:5.2.14.Final
> +-org.hibernate.common:hibernate-commons-annotations:5.0.1.Final
>       +-org.jboss.logging:jboss-logging:3.3.0.Final
>
>
> Thanks,
>
>
> Niranjan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: How to solve dependency convergence issue

Mirko Friedenhagen-2
Hello Niranja,

you may find more details at
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html.

Basically a version you manage in your project is more important than
one managed in your project's parent which is more important than a
version coming into the tree transitively.

Regards
Mirko
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/


On Wed, Mar 7, 2018 at 8:26 AM, Anders Hammar <[hidden email]> wrote:

> This shouldn't be solved via exclusions but rather by specifying the wanted
> version in the dependencyManagement section of your project.
>
> /Anders
>
> On Tue, Mar 6, 2018 at 10:37 PM, Niranjan Rao <[hidden email]> wrote:
>
>> Greetings,
>>
>>
>> I am using maven-enforcer-plugin to ensure only one version of jar files
>> is loaded. In case of conflicts, I normally would use exclusions to weed
>> out unwanted jars. Normally I would pick latest version of library.
>>
>> I am not clear how to solve following problem reported by maven enforcer
>> plugin. I am adding dependency on org.hibernate:hibernate-core which in
>> turn has dependency on org.hibernate.common:hibernate-commons-annotations.
>> Both these are pulling different versions on jboss-logging.
>>
>>
>> If I add exclusion on jboss-logging, which will get dropped? How do I
>> force to drop dependency from org.hibernate.common:hibernate-commons-annotations
>> where it seems to be using older version.
>>
>>
>> Dependency convergence error for org.jboss.logging:jboss-logging:3.3.1.Final
>> paths to dependency are:
>> +group:artifcat:version
>>   +-org.hibernate:hibernate-core:5.2.14.Final
>>     +-org.jboss.logging:jboss-logging:3.3.1.Final
>> and
>> +group:artifcat:version
>>   +-org.hibernate:hibernate-core:5.2.14.Final
>> +-org.hibernate.common:hibernate-commons-annotations:5.0.1.Final
>>       +-org.jboss.logging:jboss-logging:3.3.0.Final
>>
>>
>> Thanks,
>>
>>
>> Niranjan
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]