[jboss-jira] [JBoss JIRA] Commented: (AS7-1389) Log API dependencies should be included automatically in deployments

jaikiran pai (JIRA) jira-events at lists.jboss.org
Fri Jul 22 11:02:23 EDT 2011


    [ https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615945#comment-12615945 ] 

jaikiran pai commented on AS7-1389:
-----------------------------------

Out of curiosity, why do we want to do that? Especially in cases where the users usually end up packaging these jars (either due to Maven or intentionally) within their .war/WEB-INF/lib or .ear/lib folders.

Adding these implicit dependencies will force them to have a jboss-deployment-structure.xml just to exclude these dependencies. On the other hand, I think if users want to rely on the version of these libraries shipped in AS, then I guess it would be better to just have them explicitly list it as a module dependency via jboss-deployment-structure.xml or MANIFEST.MF


> Log API dependencies should be included automatically in deployments
> --------------------------------------------------------------------
>
>                 Key: AS7-1389
>                 URL: https://issues.jboss.org/browse/AS7-1389
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 7.0.0.Final
>            Reporter: David Lloyd
>             Fix For: 7.0.1.Final
>
>
> The following log APIs should be included by deployments by default:
> * {{org.slf4j}}
> * {{org.apache.commons.logging}}
> * {{org.log4j}}
> These dependencies should override the deployment's versions of these libraries unless explicitly excluded by {{jboss-deployment-structure.xml}}.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list