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 "Ralph Goers (JIRA)" <ji...@apache.org> on 2016/09/30 16:50:20 UTC

[jira] [Created] (LOG4J2-1627) Move components from the Log4j 2 build into a separate build.

Ralph Goers created LOG4J2-1627:
-----------------------------------

             Summary: Move components from the Log4j 2 build into a separate build.
                 Key: LOG4J2-1627
                 URL: https://issues.apache.org/jira/browse/LOG4J2-1627
             Project: Log4j 2
          Issue Type: Improvement
    Affects Versions: 2.8
            Reporter: Ralph Goers


The Log4j build has grown to the point that performing releases is very time consuming. One way to help with this is to move some components, especially those that are not typically modified frequently, to another project.  Almost everything besides the API, Core, web and the various bridges could be moved.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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