Not sure if this is a known issue or not, though I did search around a bit.
Section 15.3.1 of the user guide suggests a way to set the pom.artifactId to change the name of the archive that us used to generate the pom.xml, etc.. In multi-module builds, I find that the pom dependencies are using the directory (project) name instead. I was able to work around it in my settings.gradle file by changing all of my project names to match the artifactId and remapping the directories. That's kind of painful in the long run. Wondering if I've missed something simple or if this is a bug or something. -Paul -- View this message in context: http://www.nabble.com/Broken-pom-dependencies-with-custom-artifactId-tp22985993p22985993.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
