[
http://jira.codehaus.org/browse/MCLIRR-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99939
]
Grégory Joseph commented on MCLIRR-6:
-------------------------------------
Somehow this seems to contradict the fact that MCLIRR-5 was properly resolved.
Can't check right now - will do.
> Classloader for current version not built properly
> --------------------------------------------------
>
> Key: MCLIRR-6
> URL: http://jira.codehaus.org/browse/MCLIRR-6
> Project: Maven 2.x Clirr Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Grégory Joseph
> Attachments: clirr-classloader.patch
>
>
> When trying to use the clirr mojo, I get ClassNotFoundExceptions, in exactly
> the same vein as others have had [1]. After some debugging, I realized this
> was due to the fact that clirr was fed with a classloader for the "current"
> classes that missed the dependencies. The fix for this was pretty trivial
> (see attachment), but one might want to change the condition at line 474 of
> the createClassLoader() method instead.
> I might be doing something wrong, but I really don't see what; with this fix,
> I get the expected report.
> [1]
> http://www.google.com/search?q=%22at+org.apache.bcel.classfile.JavaClass.getAllInterfaces%28JavaClass.java%3A808%29%22
--
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
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
