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. -- 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
