Le samedi 20 septembre 2014 11:35:56 William Ferguson a écrit : > 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: > http://search.maven.org/#artifactdetails%7Ccom.squareup%7Cfest-android%7C1.0 > .8%7Cjar > > 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. +1 actual POM syntax is an esperanto necessary for the whole ecosystem, independently from the build tool used: it has to be enforced => central should reject such malformed POMs
notice there should be a bug report to the tool which built the POM: it has to rephrase 19.1+ to [19.1,) (or any more precise traduction) can someone open an issue (I don't know where) and give the url? Regards, Hervé > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
