[jira] Updated: (MPHIBERNATE-3) When the class loader for the thread context is null hibernate plugin does not find all the classes

[ji...@codehaus.org]

The following issue has been updated:

    Updater: Jeff Prickett (mailto:prickett@neighborhood.info)
       Date: Sat, 28 Feb 2004 5:03 PM
    Comment:
Here is the patch. If the thread context class loader is null it creates a new class loader that has all the urls of the maven project class loader plus the build directory.
    Changes:
             Attachment changed to classloader.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPHIBERNATE-3&page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPHIBERNATE-3

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPHIBERNATE-3
    Summary: When the class loader for the thread context is null hibernate plugin does not find all the classes
       Type: Bug

     Status: Unassigned
   Priority: Major

 Original Estimate: 0 minutes
 Time Spent: Unknown
  Remaining: 0 minutes

    Project: maven-hibernate-plugin

   Assignee: 
   Reporter: Jeff Prickett

    Created: Sat, 28 Feb 2004 4:54 PM
    Updated: Sat, 28 Feb 2004 5:03 PM
Environment: Suse Linux, Java 1.4.2-rc1, Current CVS snapshot of maven

Description:
The class loader for the thread that runs the hibernate plugin is somehow getting set to null. When this happens the class loader used by the plugin only finds classes that are in the build directory.

I have researched this issue and found that the class loaders for the individual dependencies are null and that if this is the case the core maven program adds them to the project class loader.

So the solution seems to be to set the thread class loader to the project class loader if the thread context loader is null. A more complete way to fix this might be to iterate down the individual dependencies and verify that their classloaders are also null.

I have a quick patch that fixes the issue that I have seen.

The patch is finished and I mailed it to the maven dev list last night.

Thanks Jeff Prickett


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org