logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-333) match artifact ids with Maven module names
Date Sun, 18 Aug 2013 14:34:48 GMT

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

Hervé Boutemy commented on LOG4J2-333:

that would be great, IMHO, but of course, this is a decision for your dev team, not myself

notice that if you choose not to rename directories (you still can), you should then manually
define scm section in every submodule since actual auto-calculated value is wrong (uses artifact-id:
try mvn help:effective-pom on a submodule and you'll see)
> match artifact ids with Maven module names
> ------------------------------------------
>                 Key: LOG4J2-333
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-333
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: API, Core, Flume Appender, JCL Bridge, JMX, log4j 1.2 emulation,
SLF4J Bridge, Taglib
>    Affects Versions: 2.0-beta8
>            Reporter: Hervé Boutemy
>            Priority: Blocker
> actual directory names don't match artifact ids:
> {noformat}$ grep "^  <artifact" */pom.xml
> api/pom.xml:  <artifactId>log4j-api</artifactId>
> core/pom.xml:  <artifactId>log4j-core</artifactId>
> dist/pom.xml:  <artifactId>log4j-distribution</artifactId>
> flume-ng/pom.xml:  <artifactId>log4j-flume-ng</artifactId>
> jcl-bridge/pom.xml:  <artifactId>log4j-jcl</artifactId>
> jmx-gui/pom.xml:  <artifactId>log4j-jmx-gui</artifactId>
> log4j12-api/pom.xml:  <artifactId>log4j-1.2-api</artifactId>
> log4j-to-slf4j/pom.xml:  <artifactId>log4j-to-slf4j</artifactId>
> osgi/pom.xml:  <artifactId>log4j-osgi</artifactId>
> samples/pom.xml:  <artifactId>log4j-samples</artifactId>
> slf4j-impl/pom.xml:  <artifactId>log4j-slf4j-impl</artifactId>
> taglib/pom.xml:  <artifactId>log4j-taglib</artifactId>{noformat}
> the only exception is log4j-to-slf4j
> doing so will cause you problems with automatic calculations done by Maven for site:
you're going to fight against Maven, which is good neither for you nor Maven (I already heard
a lot about "maven site plugin is broken"...) :)
> you should really rename directories in svn to match artifactIds (which will cause less
trouble than renaming artifact ids to match directory names IMHO)

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

View raw message