maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason van Zyl <>
Subject Re: Ivy style versions propagating in Maven central
Date Sat, 20 Sep 2014 02:22:15 GMT

On Sep 19, 2014, at 9:35 PM, William Ferguson <> wrote:

> Because of the rise of Gradle usage to its inclusion as the build tool in
> Android Studio, there are more and more artifacts making their way into
> Maven Central whose POMs contain elements that do not conform to Maven
> expectations.
> A good example is this POM:
> It has a dependency that uses the Gradle/Ivy version syntax of 19.1+ to
> indicate a range.
> Maven does not parse this version string and dies.
> So the question is what should be done about it.
> Some ideas:
>   1. Maven central starts verifying and rejecting malformed POMs with a
>   reason for rejection.


This is just terrible syntax and doesn't follow any normal set notation established by any
existing systems. Normal set notation works perfectly fine and using something else is not
really a boon for anyone.

>   2. Maven starts handling the Gradle/Ivy version syntax either as
>      1. an optional extra
>      2. a permanent move forward (configurable to support backward
>      compatibility)
> William



Jason van Zyl
Founder,  Apache Maven

I never make the mistake of arguing with people for whose opinions I have no respect.

-- Edward Gibbon

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