The production and consumption of maven-specific version strings should live entirely with the maven-specific code: - POM generation should translate our 'Gradle' version string to maven version string - POM parsing should translate maven version strings to the 'Gradle' format
This is the first change I would make, and it would solve the actual problem at hand. Ideally, we'd do something similar when translating to/from Ivy descriptor files, but for now the 'Gradle' format and the 'Ivy' format are the same. To start to address this, we'd start using a class to represent a parsed version string, and use that everywhere internally. Then, we'd only need to parse the version strings once when resolving (with POM, Ivy, and Gradle-specific parsing), and render the version strings when publishing. But since this is a much bigger change, I'd start with just working on the POM parsing/production code. Daz On Thu, Aug 28, 2014 at 1:47 AM, WonderCsabo <kozakcs...@gmail.com> wrote: > I see, but now what is not clear for me is the role the proposed > VersionSelector class. In this POM generation, it will be called with an > Ivy > version string as an input, as well as all other parts of the Gradle > codebase. So VersionSelector only has to know the Ivy syntax for parsing. > > But if you use it for POMs and Maven version string as input, we have to > add > Maven version syntax support too. > > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Translating-Ivy-dep-version-syntax-to-Maven-in-POM-generation-tp5712755p5713072.html > Sent from the gradle-dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Darrell (Daz) DeBoer http://www.gradleware.com
