I think this is the same issue that I circumvented with an artifactMapping map in my own builds: http://github.com/huxi/lilith/blob/master/config.gradle
Search for "artifactMapping" in that file, it is used at two locations... Some better way of handling this would be much appreciated! Cheers, Joern. On 27.02.2011, at 19:45, Peter Niederwieser wrote: > Dependency entries in the POM seem to be constructed from their corresponding > org.gradle.api.Project objects. So the only solution I can see at the moment > is to change the projects' names to match the desired artifact IDs. Probably > worth an issue. > > -- > Peter Niederwieser > Developer, Gradle > http://www.gradle.org > Trainer & Consultant, Gradle Inc. > http://www.gradle.biz > Creator, Spock Framework > http://spockframework.org > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Maven-generated-artifacts-are-incorrect-tp3401931p3402423.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 > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
