maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Curtis Rueden <>
Subject Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)
Date Fri, 19 Aug 2016 15:53:49 GMT
Hi Christian,

This is awesome.

== What works ==

With model version 4.0.0, Maven 3.4.0 now behaves exactly as before. And
the property overriding bug no longer occurs, either. This maintains build
reproducibility for my projects, for which I am very thankful.

With model version 4.1.0, Maven 3.4.0 complains about my project thusly:

    [ERROR] Cannot inherit from parent 'org.scijava:pom-scijava:pom:10.6.0'
with different model version '4.0.0'. Expected model version '4.0.0'.

Followed by many of:

    [WARNING] Multiple conflicting imports of dependency ...

And after updating all POM ancestors to model 4.1.0, the build succeeds
again, but with the new Maven 3.4.0 behavior.

== What doesn't work ==

The only remaining problem is that with model version 4.1.0, version
property overrides in the POM still do not win over imported BOMs.

That is, with the addition of something like:

    $ git diff -U1
    diff --git a/pom.xml b/pom.xml
    index d04c102..c75eb45 100644
    --- a/pom.xml
    +++ b/pom.xml
    @@ -38,2 +38,3 @@
    +               <imagej.version>2.0.0-rc-49</imagej.version>

With model version 4.0.0 the override works:

    $ mvn dependency:list|grep 'net.imagej:imagej:'
    [INFO]    net.imagej:imagej:jar:2.0.0-rc-49:compile

Whereas with model version 4.1.0 there is no override anymore:

    $ mvn340 dependency:list|grep 'net.imagej:imagej:'
    [WARNING] Multiple conflicting imports of dependency
'net.imagej:imagej:jar' into model '[inherited]:fiji:jar:2.0.0-SNAPSHOT' @
'/Users/curtis/code/fiji/fiji/pom.xml' ('256 : 16,
'256 : 16, net.imagej:pom-imagej:15.6.0
To resolve this conflict, either declare the dependency directly in the
dependency management of model '[inherited]:fiji:jar:2.0.0-SNAPSHOT' to
override what gets imported or, as of Maven 3.4, rearrange the causing
imports in the inheritance hierarchy to apply standard override logic based
on artifact coordinates. Without resolving this conflict, your build relies
on indeterministic behaviour.
    [INFO]    net.imagej:imagej:jar:2.0.0-rc-48:compile

I can create an MCVE if that would be helpful; just let me know.


P.S. Thanks and kudos to Herve Boutemy et al. for the colorized output. So

Curtis Rueden
LOCI software architect -
ImageJ2 lead, Fiji maintainer -
Did you know ImageJ has a forum?

On Fri, Aug 19, 2016 at 3:05 AM, Christian Schulte <> wrote:

> Am 08/17/16 um 22:16 schrieb Curtis Rueden:
> > One question: for POM hierarchies with mixed model versions -- a 4.0.0
> > which imports or extends a 4.1.0 POM or vice versa -- do you foresee any
> > complications?
> Parent and child need to use the same model version. There is no way to
> support inheritable import scope when a parent is 4.0.0 and a child is
> 4.1.0. Importing a 4.0.0 model into a 4.1.0 and vice versa is possible.
> Current master already has been updated. You can grab a recent
> 3.4.0-SNAPSHOT from here:
> <>
> It would be great if you could test that existing 4.0.0 projects behave
> exactly as before and that updating the model version to 4.1.0 you get
> the new behaviour. Thanks.
> Regards,
> --
> Christian
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message