[ http://jira.codehaus.org/browse/MPJALOPY-9?page=comments#action_61414 ]
Lukas Theussl commented on MPJALOPY-9: -------------------------------------- I am not sure this is the right fix for this problem: how can the root classloader fix a ClassCastException? I checked that going back to the configuration of the 1.3.1 release of the jalopy plugin, everything works for me without having to specify the root class loader. I have no idea though where the CCE above is coming from. I'd suspect a configuration problem, since, as Wendy points out herself, it still works for other people. On the other hand, the jalopy plugin 1.4 seems completely borked, see my comment at MPJALOPY-10. > Jalopy Classes not found > ------------------------ > > Key: MPJALOPY-9 > URL: http://jira.codehaus.org/browse/MPJALOPY-9 > Project: maven-jalopy-plugin > Type: Bug > Versions: 1.3.1, 1.4 > Reporter: Arnaud Heritier > Assignee: Arnaud Heritier > Priority: Blocker > Fix For: 1.4.1 > > > Mail from Wendy Smoak : > Twice now, on two different machines (same codebase, though,) the > Jalopy plugin was working fine and then suddenly stopped working with > the error below. > Full output of maven jalopy -X is here: > http://wiki.wsmoak.net/cgi-bin/wiki.pl?Maven/Jalopy > The only thing that changed was Jalopy's config file. Reverting those > changes to a known good state didn't help. Other developers on the > project aren't having any trouble. Obviously I've done *something* to > it (twice!) but I have no idea what. > Does anyone see anything that looks suspicious? > -Wendy > /svn/struts/current/action > $ maven jalopy > __ __ > | \/ |__ _Apache__ ___ > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > |_| |_\__,_|\_/\___|_||_| v. 1.0.2 > java.lang.ClassCastException: java.lang.String > at > de.hunsicker.jalopy.storage.Convention.synchronize(Convention.java:24 > 19) > at > de.hunsicker.jalopy.storage.Convention.synchronize(Convention.java:24 > 45) > at de.hunsicker.jalopy.storage.Convention.<clinit>(Convention.java:211) > at de.hunsicker.jalopy.plugin.ant.AntPlugin.<clinit>(AntPlugin.java:60) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct > orAccessorImpl.java:39) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC > onstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:494) > at > org.apache.tools.ant.AntClassLoader.initializeClass(AntClassLoader.ja > va:490) > at > org.apache.tools.ant.taskdefs.Definer.addDefinition(Definer.java:231) > at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:162) > at org.apache.tools.ant.Task.perform(Task.java:341) > at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:185) > ... > build:start: > jalopy:taskdef: > java:prepare-filesystem: > java:compile: > [echo] Compiling to c:\svn\struts\current\action/target/classes > BUILD FAILED > File...... c:\java\m1-repository\cache\maven-jalopy-plugin-1.3.1\plugin.jelly > Element... ant:jalopy > Line...... 64 > Column.... 46 > java.lang.NoClassDefFoundError > Total time: 2 seconds > Finished at: Tue Feb 07 22:20:09 GMT-07:00 2006 > Arnaud's note : > I have a similar error with the jalopy plugin 1.4 and maven 1.1 beta 3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
