[ http://jira.codehaus.org/browse/MSITE-60?page=all ]
Carlos Sanchez moved MNG-1901 to MSITE-60:
------------------------------------------
Version: (was: 2.0.1)
Fix Version: (was: 2.0.2)
Component: (was: Plugins and Lifecycle)
Complexity: (was: Intermediate)
Key: MSITE-60 (was: MNG-1901)
Project: Maven 2.x Site Plugin (was: Maven 2)
> Report Classloaders out of sync when executed from within the site:site goal.
> -----------------------------------------------------------------------------
>
> Key: MSITE-60
> URL: http://jira.codehaus.org/browse/MSITE-60
> Project: Maven 2.x Site Plugin
> Type: Bug
> Reporter: Joakim Erdfelt
> Priority: Critical
> Attachments: MNG-1901.patch, dummy-maven-plugin.tar.bz2
>
>
> When testing the classloaders from within a mojo and a report the following
> is discovered.
> ## Direct Mojo execution from command line.
> mvn -e dummy:dump
> Thread.currentThread().getContextClassLoader() = RealmDelegatingClassLoader
> for dummy:dump.
> this.getClass().getClassLoader() = RealmClassLoader for dummy:dump.
> ## Report execution via site:site
> mvn -e site:site
> Thread.currentThread().getContextClassLoader() = RealmDelegatingClassLoader
> for site:site.
> this.getClass().getClassLoader() = RealmClassLoader for dummy:report.
> When a report is executing, relying on the
> Thread.currentThread().getContextClassLoader() to obtain resources out of jar
> files (for example) will fail.
> This discovery was as a result of debugging MCHECKSTYLE-10
--
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, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
