On Wed, Jul 2, 2014 at 7:15 AM, WonderCsabo <kozakcs...@gmail.com> wrote:
> Then, i propose a module which takes the version declared in the dependency > in the .gradle file. > > 1. If the version cannot be translated to Maven format, because the feature > is non-existent in Maven, we should just leave it as is (for example: > dynamic versions). > 2. If version format is not compatible but can be translated, we transform > it so we produce a valid POM (this is for the + notation and the different > range syntax). > 3. If it is already a Maven format we leave it as is. > This sounds good. But for clarity, I reiterate that in our terminology a "dynamic version" refers to any version criteria that doesn't specify an exact version. So "1.+", "[1.0,2.0)", "latest.integration" are all "dynamic versions" in our terminology. > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Translating-Ivy-dep-version-syntax-to-Maven-in-POM-generation-tp5712755p5712788.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 Principal Software Engineer, *Gradleware <http://gradleware.com>* Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: http://www.gradlesummit.com
