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 2016/12/04 03:02:58 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=15719190#comment-15719190 ]
Gary Gregory edited comment on LOG4J2-1627 at 12/4/16 3:02 AM:
---------------------------------------------------------------
Why separate project? If it is about releasing separate versions, then we can keep it all in this project. Apache Commons already does this. As long as a version is released out of a repo, then its simple. Maybe we should rename your 'project' to 'repo/component'.
I've read concerns about the size of log4j-core, not so much how we organize modules. We already have a repo for things like Scala, so we are good there. I do not think we need more 'projects', each with their own PMCs, that would just spread things around, more MLs, more JIRA IDs and so on. We are all the same people here. It's not like we are growing in size like crazy and we want our own communities for this and that. Look at the Scala modules, that's all ONE person.
was (Author: garydgregory):
Why a separate project. If it is about releasing separate versions, then we can keep it all in this project. Apache Commons already does this. As long as a version is released out of a repo, then its simple. Maybe we should rename your 'project' to 'repo/component'.
I've read concerns about the size of log4j-core, not so much how we organize modules. We already have a repo for things like Scala, so we are good there. I do not think we need more 'projects', each with their own PMCs, that would just spread things around, more MLs, more JIRA IDs and so on. We are all the same people here. It's not like we are growing in size like crazy and we want our own communities for this and that. Look at the Scala modules, that's all ONE person.
> 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