If I understand correctly, you want the last four (all samples) to be: log4j-samples log4j-samples-common log4j-samples-remote log4j-samples-embedded
And you also want them to have names as apposed to just IDs. I'll make some further observations: - Core and JMX GUI should start with "Apache Log4j" (lowercase J) like the other artifacts, not "Apache Log4J" (uppercase J). - It seems to me like ALL of the artifacts should start with "Apache Log4j 2" to eliminate any ambiguity. - Throughout the site and documentation "Log4j" and "Log4J" are intermixed. I think we should stick to "Log4j" and make it consistent everywhere. I can easily do a case-sensitive search and clean this up. I can take care of all of these if you'd like. Nick On May 16, 2013, at 12:31 PM, Gary Gregory wrote: > Right now we have, as seen in M3 output: > > [INFO] Apache Log4j 2 > [INFO] Apache Log4j API > [INFO] Apache Log4J Core > [INFO] Apache Log4j 1.x Compatibility API > [INFO] Apache Log4j SLF4J Binding > [INFO] Apache Log4j to SLF4J Adapter > [INFO] Apache Log4j Commons Logging Bridge > [INFO] Apache Log4j Flume NG Bridge > [INFO] Apache Log4j Web Adapters > [INFO] Apache Log4j Tag Library > [INFO] Apache Log4J JMX GUI > [INFO] log4j-samples > [INFO] flume-common > [INFO] flume-remote > [INFO] flume-embedded > > The last four should be renamed, which means changing the artifact IDs, to > match the log4j prefix. > > I ran into some odd problems when I tried to do that and gave up. > > Gary > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory
