> Classworlds isn't being used yet - forehead is managing the main > classloaders.
Ok, but (then) for what purpose? > What CLASSPATH do you set? You don't need to do the project dependencies - > these have to be done by JAR overrides. The only thing would be if you are > running a gumped Maven and need to override the JARs it uses. In that case, > you'll need to generate a new forehead.conf (quite simple). I'd like Gump to control the classpath, and not have forehead in the way (not just to avoid writing more file, but to handle all issues). If I avoid forehead, [for the simple build w/ jar override use case] what will be the downside? I get confused between 'endorsed' jars and bootclasspath. I know Gump manages the system classpath (for runtime for builders, like ant/maven & for dependent jars) and bootclasspath (for things like XML libraries). Right now Gump would set the CLASSPATH environment variable, call the JVM w/ JVM arguments (including -Xbootclasspath if needed), and then Maven's CLI class w/ arguments. I'm going to give this a shot. Let me know if you can see anything obviously wrong with it. regards, Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
