It looks like I can work around this by putting jdom.jar in gradle's library. Is there anything that this will obviously mess up? Is there a better workaround that anybody can think of?
Thank you, Jerod John Murph wrote: > > On Tue, Aug 25, 2009 at 11:15 AM, JerodLass <[email protected]> wrote: > >> >> It might take a little time to make a test project that produces this >> without >> getting fired :) >> Before I do, I noticed this, and I was wondering if you thought it might >> be >> related: >> http://www.nabble.com/G2.1-class-loader-error-td15875538s134.html >> Since I saw a lot of similar stuff in the debug output with the >> parentLoader >> class loading. >> >> Thoughts? >> Jerod >> >> > I think this is your problem. Jaxen is in Gradle's lib directory, and so > would be in a "higher" classloader than what the build script defines. > Even > though your buildscript declares Jaxen as well, normal classloader > delegation will cause the higher classloader's Jaxen to get used. Then, > as > the referenced bug describes, JDOM cannot be referenced by Jaxen's > classes. > > I don't know enough to offer a suggestion for how to fix this, however. > > > -- > John Murph > Automated Logic Research Team > > -- View this message in context: http://www.nabble.com/trouble-with-ant.taskdef-classpath-tp25116786p25153005.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
