You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/04/15 08:32:22 UTC

[jira] Closed: (MNG-75) resolve issues with commons-logging

     [ http://jira.codehaus.org/browse/MNG-75?page=history ]
     
Brett Porter closed MNG-75:
---------------------------

    Fix Version:     (was: 2.0-alpha-2)
                 2.0-alpha-1
     Resolution: Fixed

this was already fixed

> resolve issues with commons-logging
> -----------------------------------
>
>          Key: MNG-75
>          URL: http://jira.codehaus.org/browse/MNG-75
>      Project: m2
>         Type: Improvement
>     Reporter: Brett Porter
>      Fix For: 2.0-alpha-1

>
>
> commons-logging may not play well with classloaders (eg, under current implementation, a POM with just hibernate 2.1.3 in it will get the infamous "Jdk14Logger does not implement Log" error).
> Devise a way to handle this. It may need to be something in classworlds, or maybe putting commons-logging into the root of the classloader with a Maven implementation (as long as this only affects Maven and its plugins, not projects built by Maven and run from Maven for tests).

-- 
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