On 14/07/2011, at 8:00 AM, Rene Groeschke wrote: > Hi, > >> >> Rene Groeschke wrote: >>> >>> Anybody an idea how to solve this? any known workarounds? >>> >> >> Gradle intentionally no longer puts Maven classes on the build script >> class >> path, so you can't reference them anymore. For your use case, Gradle >> should >> really offer a solution that doesn't require you to do this. Instead, you >> should be able to add in the excludes in a POM builder style fashion. >> Please >> raise an issue for this. In the mean time, you'll have to work around it >> in >> some way. For example, you could try to declare those dependencies with >> the >> POM builder. Or you could get hold of an exclude that's already there, get >> its Class, and create a new instance reflectively. >> >> Out of curiosity, why do you post-process the POM rather than setting the >> excludes in Gradle's dependencies section? > > I had some problems on defining the excludes (group:'*' module'*') for > groovy in the dependency section. When trying to reproduce the problem to > post it here, I just failed. It works now. > But Adding the possibility to modify the pom exclusions in a pom builder > style for different publish tasks may be a eligible use case. I've created > a jira issue at http://issues.gradle.org/browse/GRADLE-1673
Be aware that Maven doesn't understand wildcards at all for exclusions, so if your pom is using '*' for exclusions maven treats this as literally excluding the artifact with group id '*' and name '*'. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
