Hi Yes it would be good if Gradle produced POM files that were valid to use in Maven! There are a few current limitations noted in https://github.com/gradle/gradle/blob/master/design-docs/publication-model.md#fix-pom-generation-issues, one of which is dynamic versions. It would be ok if any fix only applied to the 'maven-publish' plugin, but if it worked for the 'maven' plugin as well, that would be cool.
If you want to contribute this change, that would be great. A few pointers to start with: 1. Read https://github.com/gradle/gradle/blob/master/README.md to get started. Do NOT import the project into IntelliJ (this doesn't yet work), but instead use `.gradlew idea` to generate the idea project file that can be opened directly. 2. Take a look at this recent pull request for an idea of the tests and production code that might be involved: https://github.com/gradle/gradle/pull/274. It's important that any contribution include unit tests and integration tests. 3. To test that your changes are good and the tests are passing, run '.gradlew :maven:check'. 3. Any questions regarding getting Gradle to build or design considerations, just post them to this list. cheers Daz On Sun, Jun 29, 2014 at 12:20 PM, WonderCsabo <[email protected]> wrote: > I found out that the gradle maven plugins can generate invalid POMs due to > invalid version syntax. This is becuase most gradle users use the Ivy > syntax, but that is illegal in the maven POM. Since Gradle supports both > Ivy > and Maven dependency version syntax, we could translate the version to > maven > when generating the pom. > > I would be glad to help implementing this, because i use lot of projects > with both maven and gradle users. I created this thread on the advice of > Peter in the initial forums topic > < > http://forums.gradle.org/gradle/topics/maven_publish_creates_invalid_dependency_version_numbers > > > . But i am really new to Gradle development, actually i am also not deeply > experienced as a user, and i could not even get IntelliJ to import the > Gradle codebase correctly. :S > > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Translating-Ivy-dep-version-syntax-to-Maven-in-POM-generation-tp5712755.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
