Re: Module clean ups

2013-05-16 Thread Gary Gregory
On Thu, May 16, 2013 at 7:30 PM, Scott Deboy wrote: > http://www.jetbrains.com/idea/buy/buy.jsp#openSource > Thank you! Gary > > On 5/16/13, Gary Gregory wrote: > > On Thu, May 16, 2013 at 6:04 PM, Nick Williams < > > nicho...@nicholaswilliams.net> wrote: > > > >> I don't use Eclipse (can't

Re: Module clean ups

2013-05-16 Thread Scott Deboy
http://www.jetbrains.com/idea/buy/buy.jsp#openSource On 5/16/13, Gary Gregory wrote: > On Thu, May 16, 2013 at 6:04 PM, Nick Williams < > nicho...@nicholaswilliams.net> wrote: > >> I don't use Eclipse (can't stand the thing), so I hesitate to hazard a >> guess. My gut feeling is it sounds like a

Re: Module clean ups

2013-05-16 Thread Gary Gregory
On Thu, May 16, 2013 at 6:04 PM, Nick Williams < nicho...@nicholaswilliams.net> wrote: > I don't use Eclipse (can't stand the thing), so I hesitate to hazard a > guess. My gut feeling is it sounds like a bug in the Maven Eclipse Plugin. > The error message and URL definitely indicates that the err

Re: Module clean ups

2013-05-16 Thread Gary Gregory
On Thu, May 16, 2013 at 6:04 PM, Nick Williams < nicho...@nicholaswilliams.net> wrote: > I don't use Eclipse (can't stand the thing), so I hesitate to hazard a > guess. > Flame bait! :) > My gut feeling is it sounds like a bug in the Maven Eclipse Plugin. The > error message and URL definitely

Re: Module clean ups

2013-05-16 Thread Nick Williams
I don't use Eclipse (can't stand the thing), so I hesitate to hazard a guess. My gut feeling is it sounds like a bug in the Maven Eclipse Plugin. The error message and URL definitely indicates that the error originated in the plugin. I would try running with -e to see the full error stack trace.

Re: Module clean ups

2013-05-16 Thread Gary Gregory
Nice work Nick. The last wrinkle for Eclipse users is that running, which is not new, is running "mvn eclipse:eclipse" works until the last sample: [INFO] Apache Log4j 2 SUCCESS [1.101s] [INFO] Apache Log4j API .. SUCCESS [0.256

Re: Module clean ups

2013-05-16 Thread Nick Williams
- There were >400 use cases of "Log4j" in documentation, but around 100 use cases of "Log4J." All uses of "Log4J" have been changed to "Log4j." - There were dozens of classes with "Log4j" in their names, but a handful had "Log4J" in their name. All uses of "Log4J" have been changed to "Log4j."

Re: Module clean ups

2013-05-16 Thread Ralph Goers
Yes. That way both log4j 1.x and log4j 2.x configuration files can be present. Ralph On May 16, 2013, at 11:10 AM, Gary Gregory wrote: > On Thu, May 16, 2013 at 2:07 PM, Ralph Goers > wrote: > We decided a while ago not to include the "2" in the Log4j name. It is > enough that it is in the

Re: Module clean ups

2013-05-16 Thread Ralph Goers
Not someone :-) me. Notice that only beta5 is there. I didn't do it in beta6. I need to update the wiki to remind myself not to do it in the future (or whoever else does the release). Ralph On May 16, 2013, at 11:08 AM, Nick Williams wrote: > Then in appears someone broke that. The samples

Re: Module clean ups

2013-05-16 Thread Gary Gregory
On Thu, May 16, 2013 at 2:07 PM, Ralph Goers wrote: > We decided a while ago not to include the "2" in the Log4j name. It is > enough that it is in the version number. > But the "2" remains in the name of the default configuration files. Is that on purpose? Gary > Ralph > > On May 16, 2013, a

Re: Module clean ups

2013-05-16 Thread Nick Williams
Then in appears someone broke that. The samples are, indeed, in Maven Central: http://search.maven.org/#search%7Cga%7C1%7Corg.apache.logging.log4j.samples Nick On May 16, 2013, at 1:06 PM, Ralph Goers wrote: > The release wiki doesn't say it but the samples are excluded from releases to > Mave

Re: Module clean ups

2013-05-16 Thread Nick Williams
A valid point. I won't add 2. But what about the parent POM? It has 2 in the name. Should that be removed? On May 16, 2013, at 1:07 PM, Ralph Goers wrote: > We decided a while ago not to include the "2" in the Log4j name. It is > enough that it is in the version number. > > Ralph > > On May

Re: Module clean ups

2013-05-16 Thread Ralph Goers
We decided a while ago not to include the "2" in the Log4j name. It is enough that it is in the version number. Ralph On May 16, 2013, at 10:43 AM, Nick Williams wrote: > If I understand correctly, you want the last four (all samples) to be: > > log4j-samples > log4j-samples-common > log4j-sa

Re: Module clean ups

2013-05-16 Thread Ralph Goers
The release wiki doesn't say it but the samples are excluded from releases to Maven Central. I believe the sample jars are also not included in the binary distribution. Ralph On May 16, 2013, at 10:31 AM, Gary Gregory wrote: > Right now we have, as seen in M3 output: > > [INFO] Apache Log4j

Re: Module clean ups

2013-05-16 Thread Gary Gregory
On Thu, May 16, 2013 at 1:43 PM, Nick Williams < nicho...@nicholaswilliams.net> wrote: > 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 appos

Re: Module clean ups

2013-05-16 Thread Nick Williams
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 Lo

Module clean ups

2013-05-16 Thread Gary Gregory
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 B