[
http://jira.codehaus.org/browse/MNG-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100025
]
Julien S commented on MNG-2795:
-------------------------------
I believe I has the same issue as reported by Fabrice, in a very similar
setting (own conventions.xml and custom checker).
However, the funny part is:
mvn checkstyle:checkstyle works
mvn site fails with the above error
mvn checkstyle:checkstyle site works
I should also say and moved my custom jar from an extension to a plugin
dependency too.
Hope this helps.
> Classloader problem loading a resource from a build extension Jar :
> difference between 2.0.4 and (future) 2.0.5
> ---------------------------------------------------------------------------------------------------------------
>
> Key: MNG-2795
> URL: http://jira.codehaus.org/browse/MNG-2795
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.5
> Reporter: Fabrice BELLINGARD
> Assignee: Jason van Zyl
> Fix For: 2.0.5
>
> Attachments: Checkstyle-2.0.4.txt, Checkstyle-2.0.5.txt,
> Test-BuildExtension.zip
>
>
> I had a problem when executing the Checkstyle plugin (version 2.1) with the
> pre-release of Maven 2.0.5. So I dug a bit to see if this could be related to
> maven core or not, and here is what I found.
> I isolated the code that breaks the build in the checkstyle plugin: it
> happens when the plugin tries to load my Checkstyle configuration file, which
> is actually located in a JAR that is specified in the build extensions. The
> code lies in the Locator#resolveLocation() method:
> // Attempt a Resource.
> URL url = this.getClass().getClassLoader().getResource(
> location );
> This code returns null for the "url" variable, which in turns breaks the
> plugin because it doesn't find any configuration file.
> I haven't had the time to dig more into it, but I found the following issue
> that might be related to this problem: "MNG-2228 : Classloader problem
> loading jars from build extensions". Brett and Carlos worked on it and fixed
> it, so maybe they could tell more about it.
> I attached the logs of the execution with Maven 2.0.4 (which works fine) and
> Maven 2.0.5 (which breaks). I haven't had the time yet to dig further into
> that problem.
--
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
