You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/01/21 22:49:18 UTC
[jira] Updated: (SUREFIRE-71) Forking documentation improvement to
help with class loader constrainst issues
[ http://jira.codehaus.org/browse/SUREFIRE-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-71:
---------------------------------
Affects Version/s: 1.5.3 (2.1.3 plugin)
Fix Version/s: 2.0 (2.2 plugin)
> Forking documentation improvement to help with class loader constrainst issues
> ------------------------------------------------------------------------------
>
> Key: SUREFIRE-71
> URL: http://jira.codehaus.org/browse/SUREFIRE-71
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 1.5.3 (2.1.3 plugin)
> Environment: maven 2.0.2
> Reporter: Ben Gidley
> Assigned To: Brett Porter
> Priority: Minor
> Fix For: 2.0 (2.2 plugin)
>
> Attachments: maven-surefire-plugin-374325.patch
>
>
> With (for example) JAXB2 forking surefire causes a
> java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class
> This is because by default when forking an Isolated class loader is used. this can be resovled by turning child delegation on.
> The documentation does not mention this and should be improved.
--
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