commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (LOGGING-105) Implementation dependencies should be set to runtime scope
Date Thu, 01 Jun 2006 16:48:31 GMT
     [ http://issues.apache.org/jira/browse/LOGGING-105?page=all ]
     
Robert Burrell Donkin resolved LOGGING-105:
-------------------------------------------

    Resolution: Duplicate

JCL does not fit nicely into the Maven2 dependency management scheme so this creating a good
POM difficult. The Commons team does not maintain the Maven2 POMs for JCL.  Please add any
comments you have to http://jira.codehaus.org/browse/MEV-392.

> Implementation dependencies should be set to runtime scope
> ----------------------------------------------------------
>
>          Key: LOGGING-105
>          URL: http://issues.apache.org/jira/browse/LOGGING-105
>      Project: Commons Logging
>         Type: Bug

>     Versions: 1.1 Final
>     Reporter: Michael Hartman

>
> The logkit, log4j, and avalon-framework dependencies listed in the commons-logging-1.1.pom
Maven2 POM should have their scopes set to runtime  or otherwise be set to optional.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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


Mime
View raw message