Hi there,
In our griffon build we define some exclusions manually by having:
----------------------
pom.whenConfigured { pom ->
def depsWithExcluded =
pom.dependencies.findAll{dependency ->
dependency.artifactId == 'groovy-all' ||
dependency.artifactId == 'gant_groovy1.7' ||
dependency.artifactId == 'log4j' ||
dependency.artifactId.contains('slf4j')
}
def exclusion = new
org.apache.maven.model.Exclusion(groupId:'*', artifactId:'*');
depsWithExcluded*.addExclusion(exclusion)
}
----------------------
Running this snippet with latest 1.0 M3 milestone ends up in a
classloader problem as you can see in my stacktrace:
----------------------
* Where:
Script
'/Users/Rene/workspaces/github/griffon/griffon/gradle/maven.gradle'
line: 168
* What went wrong:
Execution failed for task ':griffon-cli:install'.
Cause: Could not publish configurations [configuration
':griffon-cli:archives'].
Cause: Failed to notify action.
Cause: groovy.lang.MissingMethodException: No signature of method:
org.apache.maven.model.Dependency.addExclusion() is applicable for
argument types: (org.apache.maven.model.Exclusion) values:
[org.apache.maven.model.Exclusion@5abc30ad]
Possible solutions: addExclusion(org.apache.maven.model.Exclusion),
getExclusions(), setExclusions(java.util.List)
The following classes appear as argument class and as parameter class,
but are defined by different class loader:
org.apache.maven.model.Exclusion (defined by
'java.net.URLClassLoader@d032cf5' and 'java.net.URLClassLoader@56acdd02')
If one of the method suggestions matches the method you wanted to call,
then check your class loader setup.
----------------------
Anybody an idea how to solve this? any known workarounds?
regards,
René
--
-----------------------
regards René
rene groeschke
http://www.breskeby.com
@breskeby
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
