You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2013/09/04 18:02:52 UTC

[jira] [Commented] (LOG4J2-389) make maven dependencies "optional"

    [ https://issues.apache.org/jira/browse/LOG4J2-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757903#comment-13757903 ] 

Gary Gregory commented on LOG4J2-389:
-------------------------------------

Your POM can exclude runtime dependencies you do not use.

Also, when you package your app, you can decide what to ship.
                
> make maven dependencies "optional" 
> -----------------------------------
>
>                 Key: LOG4J2-389
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-389
>             Project: Log4j 2
>          Issue Type: Dependency upgrade
>          Components: API, Core
>    Affects Versions: 2.0-beta9
>         Environment: Maven
>            Reporter: Roland Weiglhofer
>              Labels: Maven, dependencies, optional
>
> Is it possible to make the maven dependencies optional, so I do not need to install libraries, which I do not need? Or make a lightweight brunch of log4j2. E.g. I do not need Jackson- SQL- or http-stuff! All the (transitiv) log4j2-dependencies together are much bigger than my own application. This is a realy big drawback of log4j2!
> Thanks & Regards
> Roland 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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