[LOG4J2-333] Match artifact ids with Maven module names

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.0-beta8
• Fix Version/s: 2.0-beta9
• Component/s: API, Core, Flume Appender, JCL Bridge, JMX, Log4j 1.2 bridge, SLF4J Bridge, Taglib
• Assignee: Gary D. Gregory
• Reporter: Herve Boutemy
• Created: 02/Aug/13 10:13
• Updated: 04/Sep/13 05:40
• Resolved: 26/Aug/13 14:52

Description

actual directory names don't match artifact ids:

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

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)