On 27 Aug 2014, at 7:48 pm, WonderCsabo <kozakcs...@gmail.com> wrote:
> Sorry guys for being silent for almost two months, but i am back to work now. > > I have two questions: > > * i figured out that Maven actually has a counterpart of the Ivy `latest` > selector: `LATEST`. Should we use that? Possibly. It’s not entirely clear if this is still supported or not. Perhaps you could try it out with a recent maven version? > * i started to think about implementation. This conversion is in > `org.gradle.api.publication.maven.internal.ant.DefaultPomDependenciesConverter`, > am i right? Yes. > Here we just simple write out the version String we get from > org.gradle.api.artifacts.Dependency#getVersion(). Do we have a class > somewhere which interprets an Ivy version string to some Java structure? No, but I’d really like to move to this approach. If you like, you might add a method to VersionMatcher that can parse a string to some new type VersionSelector (say) that represents the version criteria and we can ask questions of. You can then make use of this in DefaultPomDependenciesConverter. Later, we can then roll this out more widely, so that all version selectors are parsed early and passed around as a VersionSelector instead of a String. -- Adam Murdoch Gradle Co-founder http://www.gradle.org CTO Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
