I hadn't seen that bootstrapping recently, but it starts working again if checkstyle is removed. That is one of the notes in the .txt file.
That leaves the current list of plugins not working at all at simian and checkstyle.
I'm pretty clueless about this one myself. Time to dig into the classloaders.
If you are going to be diving into the ClassLoaders, try working this one out. Create a plugin with a dependency on a jar file that is newer than the core product / plugins. (For example commons-lang-2.0.jar) and use a new class/method provided in that jar (for example org.apache.commons.lang.StringEscapeUtils.escapeHtml()) and watch what happens if you attempt to USE that plugin. (instant ClassLoader issue).
When it's time for the plugin to run, the core level jar (commons-lang-1.0.1.jar) takes precendence over the defined internal jar (commons-lang-2.0.jar). Even specifing the 'root.maven' dependency property doesn't allow for overriding of this effect.
Also, this effect holds true even for local maven.xml / jelly usage of objects / classes from a newer jar than what is in the core. (try <j:useBean var="obj" className="org.apache.commons.lang.StringEscapeUtils" />
http://jakarta.apache.org/commons/lang/api/org/apache/commons/lang/StringEscapeUtils.html
I hope to provide a unit test for this once I can understand how TouchStone works.
/* Joakim Erdfelt - Cingular Wireless */
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
