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:57:20 UTC

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

     [ https://issues.apache.org/jira/browse/LOG4J2-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers updated LOG4J2-1627:
--------------------------------
    Description: 
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.

In addition, some core components could be considered for moving to another module such as the mom and db appenders. Perhaps even the JMX support could be moved.

We should also take into consideration making things line up with the Java profile system in Java 8 and the Java 9 module system.

  was: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.


> 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.
> In addition, some core components could be considered for moving to another module such as the mom and db appenders. Perhaps even the JMX support could be moved.
> We should also take into consideration making things line up with the Java profile system in Java 8 and the Java 9 module system.



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