Maven conflicting library versions

[Sandesh Hegde <sa...@datatorrent.com>]

Hello Team,

How about including Dependency Convergence plug-in the maven archetype used
to create the Apex application?

http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html

This plugin checks for conflicting library versions in the dependencies.

Thanks
Sandesh

Re: Maven conflicting library versions

[Thomas Weise <th...@datatorrent.com>]

I agree, dependency updates and additons need to be carefully reviewed for
side effects. Those include potential licensing issues, conflicts and
compatibility concerns.


On Sun, Feb 14, 2016 at 9:19 PM, Chinmay Kolhatkar <ch...@apache.org>
wrote:

> This is certainly a good idea.
> But here is my 2 cents about dealing with this in general:
>
> By including dependency convergence plugin we're trying to provide a
> workaround/fix for an "effect" and not the "cause". Effect is conflicting
> library versions but cause might be including incorrect library as mvn
> dependency.
>
> I believe that along with adding dependency convergence plugin (fix for
> "effect"), we also need to be very careful while including additional
> dependencies in maven for both core+malhar (prevention of "cause").
>
> Thanks,
> Chinmay.
>
>
>
>
> On Mon, Feb 15, 2016 at 10:40 AM, Priyanka Gugale <
> priyanka@datatorrent.com>
> wrote:
>
> > That would be a great idea.
> > Errors due to wrong version getting loaded by class loader are very hard
> to
> > debug. Nice to have some tool to catch up such conflicts.
> >
> > -Priyanka
> >
> > On Sat, Feb 13, 2016 at 12:12 AM, Sandesh Hegde <sandesh@datatorrent.com
> >
> > wrote:
> >
> > > Hello Team,
> > >
> > > How about including Dependency Convergence plug-in the maven archetype
> > used
> > > to create the Apex application?
> > >
> > >
> >
> http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html
> > >
> > > This plugin checks for conflicting library versions in the
> dependencies.
> > >
> > > Thanks
> > > Sandesh
> > >
> >
>

Re: Maven conflicting library versions

[Chinmay Kolhatkar <ch...@apache.org>]

This is certainly a good idea.
But here is my 2 cents about dealing with this in general:

By including dependency convergence plugin we're trying to provide a
workaround/fix for an "effect" and not the "cause". Effect is conflicting
library versions but cause might be including incorrect library as mvn
dependency.

I believe that along with adding dependency convergence plugin (fix for
"effect"), we also need to be very careful while including additional
dependencies in maven for both core+malhar (prevention of "cause").

Thanks,
Chinmay.




On Mon, Feb 15, 2016 at 10:40 AM, Priyanka Gugale <pr...@datatorrent.com>
wrote:

> That would be a great idea.
> Errors due to wrong version getting loaded by class loader are very hard to
> debug. Nice to have some tool to catch up such conflicts.
>
> -Priyanka
>
> On Sat, Feb 13, 2016 at 12:12 AM, Sandesh Hegde <sa...@datatorrent.com>
> wrote:
>
> > Hello Team,
> >
> > How about including Dependency Convergence plug-in the maven archetype
> used
> > to create the Apex application?
> >
> >
> http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html
> >
> > This plugin checks for conflicting library versions in the dependencies.
> >
> > Thanks
> > Sandesh
> >
>

Re: Maven conflicting library versions

[Priyanka Gugale <pr...@datatorrent.com>]

That would be a great idea.
Errors due to wrong version getting loaded by class loader are very hard to
debug. Nice to have some tool to catch up such conflicts.

-Priyanka

On Sat, Feb 13, 2016 at 12:12 AM, Sandesh Hegde <sa...@datatorrent.com>
wrote:

> Hello Team,
>
> How about including Dependency Convergence plug-in the maven archetype used
> to create the Apex application?
>
> http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html
>
> This plugin checks for conflicting library versions in the dependencies.
>
> Thanks
> Sandesh
>