Hi Martin
Afraid I don't have a solution, but I do seem to be experiencing a similar
issue.
In my case, I am trying to stop acegi and spring-richclient from dragging in
older versions of spring with exclusions and getting mixed results.
Excluding spring on acegi dependency seems to block it from transitively
downloading spring 1.2.7.
However, excluding both acegi and spring on the spring-richclient
dependencies, suddenly causes maven2 to throw compiler errors - despite
the fact that I have explicity added the spring dependencies to the
project - both before and after the exclusions (in desperation).
"The type ...HttpInvokerProxyFactoryBean cannot be resolved.
It is indirectly referenced from required .class files"
at org.apache.maven.lifecycle.DefaultLifecycleExecutor
.executeGoals(DefaultLifecycleExecutor.java:559)
...
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException:
Compiler errors : error at public abstract class RemoteServiceBaseFactory
extends ...BasicAuthHttpInvokerProxyFactoryBean
One difference between the two is that acegi depends on spring, but
spring-richclient depends on spring and it depends on acegi (which
depends on spring).
So, basically it looks like maven2's exclusions is broken in some scenarios.
Explicitly including spring-remoting has no affect on the compiler error.
Perhaps classworlds is creating a special class loader for the dependency
and its exclusions, which is unaware of the parent class loader that should
contain the version you require.
Best regards
Byron
P.S. mvn -X helps to see dependency chains
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
