Using multiple uploadXXX tasks solves the problem and attached artifacts are uploaded correctly.
Talking on maven deployment, another thing for which I had to introduce pretty ugly code is adding a dependency to the pom. I can iterate and modify existing ones in "whenConfgured" closure, but did not find a way to add a new one (except to instantiate MavenDependency, using class of an existing dependency object to avoid class loading problem). As for the custom local maven repository location, my ultimate goal is to get rid of local maven repository, so that mavenDeploer does not use it at all. Then I will not need to configure custom m2 location. -- View this message in context: http://gradle.1045684.n5.nabble.com/Issues-with-deploying-multiple-artifacts-to-maven-tp4341354p4341600.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
