| Re: [sisu-users] Maven Cli -> Plexus -> Sisu Woes |
Stuart, Thank you so much for the help! Your solution was spot on. I am not sure why the context classloader would change over the lifetime of the akka actor, but caching it, as you suggested, seems to do the trick! Thanks again for the insight! Kindest Regards, jm ---------
Whenever MavenCLI constructs the DefaultPlexusContainer it will look for any plexus.xml / components.xml on the classpath defined by the “classWorld” in the cliRequest. The EventSpyDispatcher component is defined in the components.xml from maven-core. Unless specified otherwise, the “classWorld” in the cliRequest is based on the current thread’s context classloader: Thread.currentThread().getContextClassLoader() - which is initially set to the application classpath and will therefore contain the maven-core jar. However, if another piece of code has reset the context classloader between requests then you could end up with a “classWorld” that doesn’t contain maven-core in which case it would then fail. The solution for this would be to set the “classWorld” explicitly in the request and either save the initial context classloader, or use the classloader of your class that’s calling MavenCLI: // save this somewhere ClassWorld myClassWorld = new ClassWorld( "plexus.core", getClass().getClassLoader() ); // or Thread.currentThread().getContextClassLoader() if you know it’s correct at this point mavenCLI.doMain( new CliRequest( args, myClassWorld ) ); // …etc... mavenCLI.doMain( new CliRequest( args, myClassWorld ) );
|