from:"Christian Grobmeier"


Sorry, I thought I already wrote I could do it, but forgot!
Sure, let me do that for you.

Can you send me the key by private message?

On 14 Feb 2014, at 19:29, Nick Williams wrote:

Christian, since neither Greg, nor Ralph, nor Remko are able to help, 
can YOU help me get my KEYS and these artifacts committed? It's been 2 
days already. :-(


Nick

On Feb 13, 2014, at 3:30 PM, Remko Popma wrote:

Sorry Nick, I won't be able to help today. Maybe Saturday (but even 
that is a maybe...) :-(



On Fri, Feb 14, 2014 at 6:28 AM, Remko Popma remko.po...@gmail.com 
wrote:




On Fri, Feb 14, 2014 at 1:24 AM, Gary Gregory 
garydgreg...@gmail.com wrote:
On Thu, Feb 13, 2014 at 8:54 AM, Nicholas Williams 
nicho...@nicholaswilliams.net wrote:
Apparently I don't have karma to commit anything on dist, because I 
can't commit my keys OR the rc1 release artifacts. I'm told it's 
forbidden. Can y'all provide me (even temporary) karma to do that? Or 
does Infra have to get involved?


I think you'll need someone else to commit the for you. Today's not 
good for me here, sorry. Until then, the release will fail anyway 
because the scripts that do the mirroring check the signatures. Hence 
the recommendation to check signatures against the KEYS file by at 
least one person in our PMC. It'll be smoother next time :)


Gary

Nick

Sent from my iPhone, so please forgive brief replies and frequent 
typos


On Feb 13, 2014, at 3:39, Christian Grobmeier 
grobme...@gmail.com wrote:


On 12 Feb 2014, at 20:01, Nick Williams wrote:
What matters is what is in 
https://www.apache.org/dist/logging/KEYS


If someone will provide me instructions, I can put my keys there.

Instructions are at the top of the file:
https://www.apache.org/dist/logging/KEYS

also, following through the links I posted earlier, you get to 
https://www.apache.org/dev/release-signing.html


I've read those pages until I was blue in the face :-) but neither 
help me any at all. Exporting my keys is *easy*. I'm looking for 
instructions to edit the KEYS file. I don't know where it is or 
whether I should edit it via SVN or SSH or what.



oh haha :) Sorry for misunderstanding!

Please check the file out from:
https://dist.apache.org/repos/dist/release/logging/

Unfortunately you'll checkout the old releases as well.
You *should* have karma to commit your key to the file directly.

From there your KEY will be spread to the mirrors (which is 
including the link above)


Cheers



Nick


Gary

Cheers


Nick

If the RM's key is not there, the files cannot be verified.

I am guessing you added Nick's key to your keystore?

Gary


On 2/12/14, Gary Gregory garydgreg...@gmail.com wrote:
On Wed, Feb 12, 2014 at 11:44 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:


On Feb 12, 2014, at 10:29 AM, Nick Williams wrote:


On Feb 12, 2014, at 10:15 AM, Gary Gregory wrote:

Nick,

You've got to add your key to the project KEYS file, in the case 
the

Log4j
projects KEYS file as referenced from
https://logging.apache.org/log4j/2.x/download.html


Okay. The ASF tech folks never told me that. How do I edit that 
file?



Interesting: You don't have a key in that file. Additionally, all 
the

keys
in that file are expired.


Well, now's a good time to find all this out! ;)

Gary



Verifying sigs and hashes is a step in the voting process AFAIK.


Agreed. My question was, Does this vote need to be canceled? 
followed
by, Does that mean someone on the PMC needs to change their vote 
from +1

to -1? because we already have the necessary votes to release.

If you follow the links from my previous messages, you'll find all 
the

information you need about signing, keys, using PGP/GPG and so on.


Okay. My problem was I couldn't find any information anywhere 
(including
in the links you sent me) that tell me how to tell whether a PGP 
key is

RSA
or DSA and what its strength is. Through some deductive reasoning, 
I

THINK
when you see 1024R or 2048R it mess 1024-bit RSA or 2048-bit 
RSA,
respectively, and likewise 1024D and 2048D mean 1024-bit DSA 
and
2048-bit DSA, respectively. IF I'm correct about this, Christian 
is still

using a 1024-bit DSA key.

In the meantime, I'll generate a new key.

Nick


Gary


On Wed, Feb 12, 2014 at 10:57 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:

I'm guessing the public key wasn't found because you didn't import 
it.


I don't know why I would have generated a DSA key. That doesn't 
make any
sense. Unfortunately, I can't even figure out how to VIEW the 
contents

of
my own GPG public key to see what's in it. All I've been able to 
find is
how to list my keys and view their fingerprints, so I can't see 
whether

any
of them are RSA or DSA or what strength they are. Anyone have any
suggestions?

What I DO know is that, before I could become a committer, the ASF 
tech
people required me to generate a key and upload it to a public 
site. I
uploaded it to http://pgp.mit.edu/. They went and looked at the 
key and

told me that it looked

Re: [VOTE] Log4j 2.0-rc1 RC2


I added your KEY and also the release:
https://dist.apache.org/repos/dist/release/logging/log4j/2.0-rc1/

As we discussed I didn't upload the website yet but want to wait for the 
artifacts to be distributed by the mirrors.


Also I would like to suggest we remove the old artifacts after we 
updated the website.


Cheers
Christian

On 15 Feb 2014, at 16:53, Nick Williams wrote:


Done. Let me know if you didn't receive the email.

Nick

On Feb 15, 2014, at 9:38 AM, Christian Grobmeier wrote:


Sorry, I thought I already wrote I could do it, but forgot!
Sure, let me do that for you.

Can you send me the key by private message?

On 14 Feb 2014, at 19:29, Nick Williams wrote:

Christian, since neither Greg, nor Ralph, nor Remko are able to 
help, can YOU help me get my KEYS and these artifacts committed? 
It's been 2 days already. :-(


Nick

On Feb 13, 2014, at 3:30 PM, Remko Popma wrote:

Sorry Nick, I won't be able to help today. Maybe Saturday (but even 
that is a maybe...) :-(



On Fri, Feb 14, 2014 at 6:28 AM, Remko Popma 
remko.po...@gmail.com wrote:




On Fri, Feb 14, 2014 at 1:24 AM, Gary Gregory 
garydgreg...@gmail.com wrote:
On Thu, Feb 13, 2014 at 8:54 AM, Nicholas Williams 
nicho...@nicholaswilliams.net wrote:
Apparently I don't have karma to commit anything on dist, because I 
can't commit my keys OR the rc1 release artifacts. I'm told it's 
forbidden. Can y'all provide me (even temporary) karma to do that? 
Or does Infra have to get involved?


I think you'll need someone else to commit the for you. Today's not 
good for me here, sorry. Until then, the release will fail anyway 
because the scripts that do the mirroring check the signatures. 
Hence the recommendation to check signatures against the KEYS file 
by at least one person in our PMC. It'll be smoother next time :)


Gary

Nick

Sent from my iPhone, so please forgive brief replies and frequent 
typos


On Feb 13, 2014, at 3:39, Christian Grobmeier 
grobme...@gmail.com wrote:


On 12 Feb 2014, at 20:01, Nick Williams wrote:
What matters is what is in 
https://www.apache.org/dist/logging/KEYS


If someone will provide me instructions, I can put my keys 
there.


Instructions are at the top of the file:
https://www.apache.org/dist/logging/KEYS

also, following through the links I posted earlier, you get to 
https://www.apache.org/dev/release-signing.html


I've read those pages until I was blue in the face :-) but 
neither help me any at all. Exporting my keys is *easy*. I'm 
looking for instructions to edit the KEYS file. I don't know 
where it is or whether I should edit it via SVN or SSH or what.



oh haha :) Sorry for misunderstanding!

Please check the file out from:
https://dist.apache.org/repos/dist/release/logging/

Unfortunately you'll checkout the old releases as well.
You *should* have karma to commit your key to the file directly.

From there your KEY will be spread to the mirrors (which is 
including the link above)


Cheers



Nick


Gary

Cheers


Nick

If the RM's key is not there, the files cannot be verified.

I am guessing you added Nick's key to your keystore?

Gary


On 2/12/14, Gary Gregory garydgreg...@gmail.com wrote:
On Wed, Feb 12, 2014 at 11:44 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:


On Feb 12, 2014, at 10:29 AM, Nick Williams wrote:


On Feb 12, 2014, at 10:15 AM, Gary Gregory wrote:

Nick,

You've got to add your key to the project KEYS file, in the case 
the

Log4j
projects KEYS file as referenced from
https://logging.apache.org/log4j/2.x/download.html


Okay. The ASF tech folks never told me that. How do I edit that 
file?



Interesting: You don't have a key in that file. Additionally, 
all the

keys
in that file are expired.


Well, now's a good time to find all this out! ;)

Gary



Verifying sigs and hashes is a step in the voting process AFAIK.


Agreed. My question was, Does this vote need to be canceled? 
followed
by, Does that mean someone on the PMC needs to change their 
vote from +1

to -1? because we already have the necessary votes to release.

If you follow the links from my previous messages, you'll find 
all the
information you need about signing, keys, using PGP/GPG and so 
on.



Okay. My problem was I couldn't find any information anywhere 
(including
in the links you sent me) that tell me how to tell whether a PGP 
key is

RSA
or DSA and what its strength is. Through some deductive 
reasoning, I

THINK
when you see 1024R or 2048R it mess 1024-bit RSA or 2048-bit 
RSA,
respectively, and likewise 1024D and 2048D mean 1024-bit DSA 
and
2048-bit DSA, respectively. IF I'm correct about this, Christian 
is still

using a 1024-bit DSA key.

In the meantime, I'll generate a new key.

Nick


Gary


On Wed, Feb 12, 2014 at 10:57 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:

I'm guessing the public key wasn't found because you didn't 
import it.


I don't know why I would have generated a DSA key. That doesn't 
make any
sense. Unfortunately, I can't even figure out

Re: Logo contest: nominate your favorite logo

I would like to encourage everybody who didn't voice his opinion on the
logos to do it now. If somebody prefers to respond to the mailing list with
his/her thoughts I am happy to fill the wiki with.

My suggestion is to start a final vote on coming thursday.
Also I think we should only on the logos which are currently
supported by minimum 2 persons.



On 2 Feb 2014, at 11:21, Christian Grobmeier wrote:

 Hi all,

 please show your support for your favorite logo on this wiki page:
 http://wiki.apache.org/logging/Log4jLogoNominations

 I added a few nominations already, just stick with the format.

 Everybody reading this message is invited to nominate their favorite logo.

 Cheers,
 Christian


---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Logo contest: nominate your favorite logo


Uh? What did I change?

I mentioned we should vote on the 10 logos with most votes if we have 
enough logos.
At the moment we have to less expressed support for any logos to chose 
the ten.


Or which one would you let fall of the table?


On 15 Feb 2014, at 20:14, Gary Gregory wrote:


Let's not change the rules in the middle of the game here...

 Original message 
From: Christian Grobmeier grobme...@gmail.com
Date:02/15/2014  13:21  (GMT-05:00)
To: Log4J Developers List log4j-dev@logging.apache.org,Log4J Users 
List log4j-u...@logging.apache.org

Subject: Re: Logo contest: nominate your favorite logo

I would like to encourage everybody who didn't voice his opinion on 
the
logos to do it now. If somebody prefers to respond to the mailing list 
with

his/her thoughts I am happy to fill the wiki with.

My suggestion is to start a final vote on coming thursday.
Also I think we should only on the logos which are currently
supported by minimum 2 persons.



On 2 Feb 2014, at 11:21, Christian Grobmeier wrote:


Hi all,

please show your support for your favorite logo on this wiki page:
http://wiki.apache.org/logging/Log4jLogoNominations

I added a few nominations already, just stick with the format.

Everybody reading this message is invited to nominate their favorite 
logo.


Cheers,
Christian



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: [VOTE] Log4j 2.0-rc1 RC2

2014-02-13 Thread Christian Grobmeier


On 12 Feb 2014, at 20:01, Nick Williams wrote:

What matters is what is in https://www.apache.org/dist/logging/KEYS

If someone will provide me instructions, I can put my keys there.

Instructions are at the top of the file:
https://www.apache.org/dist/logging/KEYS

also, following through the links I posted earlier, you get to 
https://www.apache.org/dev/release-signing.html


I've read those pages until I was blue in the face :-) but neither 
help me any at all. Exporting my keys is *easy*. I'm looking for 
instructions to edit the KEYS file. I don't know where it is or 
whether I should edit it via SVN or SSH or what.



oh haha :) Sorry for misunderstanding!

Please check the file out from:
https://dist.apache.org/repos/dist/release/logging/

Unfortunately you'll checkout the old releases as well.
You *should* have karma to commit your key to the file directly.

From there your KEY will be spread to the mirrors (which is including 
the link above)


Cheers



Nick


Gary

Cheers


Nick

If the RM's key is not there, the files cannot be verified.

I am guessing you added Nick's key to your keystore?

Gary


On 2/12/14, Gary Gregory garydgreg...@gmail.com wrote:
On Wed, Feb 12, 2014 at 11:44 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:


On Feb 12, 2014, at 10:29 AM, Nick Williams wrote:


On Feb 12, 2014, at 10:15 AM, Gary Gregory wrote:

Nick,

You've got to add your key to the project KEYS file, in the case the
Log4j
projects KEYS file as referenced from
https://logging.apache.org/log4j/2.x/download.html


Okay. The ASF tech folks never told me that. How do I edit that file?


Interesting: You don't have a key in that file. Additionally, all the
keys
in that file are expired.


Well, now's a good time to find all this out! ;)

Gary



Verifying sigs and hashes is a step in the voting process AFAIK.


Agreed. My question was, Does this vote need to be canceled? 
followed
by, Does that mean someone on the PMC needs to change their vote 
from +1

to -1? because we already have the necessary votes to release.

If you follow the links from my previous messages, you'll find all 
the

information you need about signing, keys, using PGP/GPG and so on.


Okay. My problem was I couldn't find any information anywhere 
(including
in the links you sent me) that tell me how to tell whether a PGP key 
is

RSA
or DSA and what its strength is. Through some deductive reasoning, I
THINK
when you see 1024R or 2048R it mess 1024-bit RSA or 2048-bit RSA,
respectively, and likewise 1024D and 2048D mean 1024-bit DSA and
2048-bit DSA, respectively. IF I'm correct about this, Christian is 
still

using a 1024-bit DSA key.

In the meantime, I'll generate a new key.

Nick


Gary


On Wed, Feb 12, 2014 at 10:57 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:

I'm guessing the public key wasn't found because you didn't import 
it.


I don't know why I would have generated a DSA key. That doesn't make 
any
sense. Unfortunately, I can't even figure out how to VIEW the 
contents

of
my own GPG public key to see what's in it. All I've been able to find 
is
how to list my keys and view their fingerprints, so I can't see 
whether

any
of them are RSA or DSA or what strength they are. Anyone have any
suggestions?

What I DO know is that, before I could become a committer, the ASF 
tech
people required me to generate a key and upload it to a public site. 
I
uploaded it to http://pgp.mit.edu/. They went and looked at the key 
and

told me that it looked good and that I had been approved for
committership.
I assumed that meant the key was sufficient for ASF code signing
purposes.
I would think they would have told me that it was DSA and not strong
enough. :-[

On the other hand, it's possible these instructions have changed in 
the

last year and I just wasn't aware of it.

Does this vote need to be canceled? Technically speaking, we already
have
3 PMC votes, so I THINK that means a PMC member who has already voted 
+1

would HAVE to change their vote to -1, but I may misunderstand that
rule.

Nick

On Feb 12, 2014, at 9:01 AM, Gary Gregory wrote:

Has anyone verified the signatures of all the files?

I am guessing not, the first one I try fails:

gpg --verify log4j-1.2-api-2.0-rc1.jar.asc
gpg: Signature made 02/09/14 14:09:30 using DSA key ID ED446286
gpg: Can't check signature: public key not found

Also, we are NOT supposed to use DSA keys per
https://www.apache.org/dev/release-signing.html

Under Important: All new *RSA* keys generated should be at least
*4096* bits. *Do not* generate new *DSA* keys.

See What are the ASF requirements on approving a release? in
https://www.apache.org/dev/release.html and
https://www.apache.org/dev/release-publishing.html#signed

Built from src zip with:

Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 
2013-09-17

11:22:22-0400)
Maven home: C:\Java\apache-maven-3.1.1\bin\..
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: C:\Program

Re: [VOTE] Log4j 2.0-rc1 RC2

2014-02-12 Thread Christian Grobmeier


On 12 Feb 2014, at 19:31, Nick Williams wrote:


On Feb 12, 2014, at 12:14 PM, Gary Gregory wrote:

On Wed, Feb 12, 2014 at 12:56 PM, Scott Deboy scott.de...@gmail.com 
wrote:

Actually when I run gpg on the .asc files I get:

gpg: Signature made Sun Feb  9 11:08:17 2014 PST using DSA key ID 
ED446286

gpg: Good signature from Nicholas Scott Williams (For signing NWTS
Java Code) nicho...@nicholaswilliams.net
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to 
the owner.
Primary key fingerprint: 33B0 CF6B 3229 9166 905E  52C4 C140 F70B 
ED44 6286


What matters is what is in https://www.apache.org/dist/logging/KEYS


If someone will provide me instructions, I can put my keys there.


Instructions are at the top of the file:
https://www.apache.org/dist/logging/KEYS

Cheers


Nick


If the RM's key is not there, the files cannot be verified.

I am guessing you added Nick's key to your keystore?

Gary


On 2/12/14, Gary Gregory garydgreg...@gmail.com wrote:

On Wed, Feb 12, 2014 at 11:44 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:



On Feb 12, 2014, at 10:29 AM, Nick Williams wrote:


On Feb 12, 2014, at 10:15 AM, Gary Gregory wrote:

Nick,

You've got to add your key to the project KEYS file, in the case 
the

Log4j
projects KEYS file as referenced from
https://logging.apache.org/log4j/2.x/download.html


Okay. The ASF tech folks never told me that. How do I edit that 
file?



Interesting: You don't have a key in that file. Additionally, all 
the

keys
in that file are expired.



Well, now's a good time to find all this out! ;)

Gary




Verifying sigs and hashes is a step in the voting process AFAIK.


Agreed. My question was, Does this vote need to be canceled? 
followed
by, Does that mean someone on the PMC needs to change their vote 
from +1

to -1? because we already have the necessary votes to release.

If you follow the links from my previous messages, you'll find all 
the

information you need about signing, keys, using PGP/GPG and so on.


Okay. My problem was I couldn't find any information anywhere 
(including
in the links you sent me) that tell me how to tell whether a PGP 
key is

RSA
or DSA and what its strength is. Through some deductive reasoning, 
I

THINK
when you see 1024R or 2048R it mess 1024-bit RSA or 2048-bit 
RSA,
respectively, and likewise 1024D and 2048D mean 1024-bit DSA 
and
2048-bit DSA, respectively. IF I'm correct about this, Christian is 
still

using a 1024-bit DSA key.

In the meantime, I'll generate a new key.

Nick


Gary


On Wed, Feb 12, 2014 at 10:57 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:

I'm guessing the public key wasn't found because you didn't import 
it.


I don't know why I would have generated a DSA key. That doesn't 
make any
sense. Unfortunately, I can't even figure out how to VIEW the 
contents

of
my own GPG public key to see what's in it. All I've been able to 
find is
how to list my keys and view their fingerprints, so I can't see 
whether

any
of them are RSA or DSA or what strength they are. Anyone have any
suggestions?

What I DO know is that, before I could become a committer, the ASF 
tech
people required me to generate a key and upload it to a public 
site. I
uploaded it to http://pgp.mit.edu/. They went and looked at the 
key and

told me that it looked good and that I had been approved for
committership.
I assumed that meant the key was sufficient for ASF code signing
purposes.
I would think they would have told me that it was DSA and not 
strong

enough. :-[

On the other hand, it's possible these instructions have changed 
in the

last year and I just wasn't aware of it.

Does this vote need to be canceled? Technically speaking, we 
already

have
3 PMC votes, so I THINK that means a PMC member who has already 
voted +1
would HAVE to change their vote to -1, but I may misunderstand 
that

rule.

Nick

On Feb 12, 2014, at 9:01 AM, Gary Gregory wrote:

Has anyone verified the signatures of all the files?

I am guessing not, the first one I try fails:

gpg --verify log4j-1.2-api-2.0-rc1.jar.asc
gpg: Signature made 02/09/14 14:09:30 using DSA key ID ED446286
gpg: Can't check signature: public key not found

Also, we are NOT supposed to use DSA keys per
https://www.apache.org/dev/release-signing.html

Under Important: All new *RSA* keys generated should be at 
least

*4096* bits. *Do not* generate new *DSA* keys.

See What are the ASF requirements on approving a release? in
https://www.apache.org/dev/release.html and
https://www.apache.org/dev/release-publishing.html#signed

Built from src zip with:

Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 
2013-09-17

11:22:22-0400)
Maven home: C:\Java\apache-maven-3.1.1\bin\..
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_51\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family:

Re: [VOTE] Log4j 2.0-rc1 RC2

2014-02-11 Thread Christian Grobmeier


+1

On 9 Feb 2014, at 20:56, Nick Williams wrote:

This is a vote to release Log4j 2.0-rc1, the twelfth release of Log4j 
2.0.


This release contains several changes that break binary and backwards 
compatibility with previous versions. Please read the release notes 
correctly so that you can adjust your usage of Log4j 2, if necessary.


Changes in this version include:

New features:
o LOG4J2-530:  (JMX) JMX Client GUI should dynamically update when 
LoggerContext MBeans are registered/unregistered in MBean server.
o LOG4J2-479:  ThreadContext now uses plain ThreadLocal by default, 
unless system property isThreadContextMapInheritable has value true. 
Thanks to MK.

o LOG4J2-481:  Add Stream interface to Loggers. Thanks to Matt Sicker.
o LOG4J2-482:  Documentation fix: The attribute of Route to refer to 
an appender is ref not AppenderRef. Thanks to Hongdi Ren.
o LOG4J2-467:  Added option to toggle Thread name caching in 
AsyncLogger. Thanks to Anthony Baldocchi.
o LOG4J2-423:  Added MBeans for instrumenting AsyncAppenders and 
AsyncLogger RingBuffers, exposing queue size, remaining capacity and 
other attributes.

o LOG4J2-420:  Create a lookup for resource bundle substitution.
o LOG4J2-415:  Format log event time as UNIX time (seconds or 
milliseconds).

o LOG4J2-401:  Configure FileAppender buffer size.
o LOG4J2-402:  Configure RandomAccessFileAppender buffer size.

Fixed Bugs:
o LOG4J2-500:  (JMX - ObjectNames changed!) Unloading one web 
application unloads JMX MBeans for all web applications.
o LOG4J2-531:  Fixed bugs where rolled log files were overwritten by 
RollingFile appender with composite time and size based policies. 
Thanks to Geoff Ballinger.
o LOG4J2-475:  Changed the MongoDBConnection to add a MongoDB encoding 
hook instead of a decoding hook. Thanks to Matt Sicker.
o LOG4J2-489:  Fixed the JPAAppender's overuse of transactions by 
connecting (borrowing from pool) on new write internal or on flush.
o LOG4J2-457:  Fixed failure of JDBC and JPA appender to properly 
release database connections by connecting (borrowing from pool) on 
new write internal or on flush.
o LOG4J2-442:  Fixed problem with JDBC and JPA appender connectivity 
in WebSphere by connecting (borrowing from pool) on new write internal 
or on flush.
o LOG4J2-438:  Ensured the JDBCAppender commits transactions after a 
single write or a flush of multiple writes.
o LOG4J2-407:  Fixed inability to recover from lost database 
connection in database appenders by connecting (borrowing from pool) 
on new write internal or on flush.
o LOG4J2-511:  Stop AsyncLoggerConfig Disruptor thread(s), then 
AsyncAppender thread(s) first before stopping other appenders. Thanks 
to James Pretorius.
o LOG4J2-392:  Stop AsyncLoggerConfig Disruptor thread(s), then 
AsyncAppender thread(s) first before stopping other appenders. Thanks 
to ilynaf, Andre Bogus.
o LOG4J2-345:  (OSGi) logging.log4j-1.2-api doesn't export the log4j 
API 1.2. Dependent bundles can not be resolved. Thanks to Roland 
Weiglhofer, Matt Sicker.

o LOG4J2-523:  LocalizedMessage serialization is broken.
o LOG4J2-385:  Fixed issues with time-based file rollover (monthly, 
weekly, hourly and every minute). Thanks to Ace Funk, Porfirio 
Partida.
o LOG4J2-452:  Added a ServletContext attribute that, when set to 
true, disables Log4j's auto-initialization in Servlet 3.0+ web 
applications.
o LOG4J2-512:  Exposed Log4j web support interface and methods and the 
LoggerContext through ServletContext attributes so that threads not 
affected by filters (such as asynchronous threads) can utilize the 
LoggerContext. Also updated the Log4j filter so that it supports 
async. Thanks to Chandra Sekhar Kakarla, Matt Sicker.
o LOG4J2-409:  Created a utility to properly escape backslashes before 
creating URIs, and changed URI creation to use the utility instead of 
instantiating URI directly. Thanks to Frank Steinmann, Thomas 
Neidhart.
o LOG4J2-344:  Changed the Servlet 3.0 auto-initializer to add the 
filter by class to get around a WebLogic bug. Thanks to Keir Lawson, 
Tomasz Wladzinski.
o LOG4J2-359:  Changed the Servlet 3.0 auto-initializer so that it 
does nothing in a Servlet 2.5 or older application. This ensures 
behavioral consistency across containers. This includes additional 
fixes to abort initialization if a duplicate filter already exists and 
to check the actual Servlet EFFECTIVE version. Thanks to Abhinav Shah.
o LOG4J2-517:  Switch in log4j-1.2-api Category.getEffectiveLevel has 
no cases for FATAL, OFF.
o LOG4J2-406:  (JMX) Unregister all log4j JMX MBeans when the 
LoggerContext is stopped to allow web application classes to be GC-ed 
on undeploy. Thanks to Kerrigan Joseph.

o LOG4J2-405:  Configuration was being processed twice at startup.
o LOG4J2-398:  Configure properties and setup Interpolator before 
processing rest of configuration.
o LOG4J2-470:  hostName property was not being set until after the 
first configuration element.

o LOG4J2-464:  Support arrays as

Re: [VOTE] Log4j 2.0-rc1 RC2

2014-02-11 Thread Christian Grobmeier

Not sure if the site dependency needs to be considered part of our 
software.

I recall having that discussion once i am going to dig archives

On 11 Feb 2014, at 6:13, Nicholas Williams wrote:

I think it's very clearly a yes. The legal page says code with the MIT 
license can be included in ASF projects.


However, I have a suggestion for the next release that will make this 
whole discussion moot: let's use the CDN instead of including the 
JQuery source code in source control. That way we're not hosting the 
JQuery files, and we don't have to worry about RAT reports, NOTICE 
files, or license info in the POM.


As for RC1, I don't see any reason it can't proceed. This isn't a 
regression—the JQuery files have been in source control for 14 
months without incident or complaint.


Nick

Sent from my iPhone, so please forgive brief replies and frequent 
typos


On Feb 10, 2014, at 20:20, Gary Gregory garydgreg...@gmail.com 
wrote:


This should be documented clearly in our build (in this case, in the 
POM).


Is the JQuery license compatible with ours?

If you read https://www.apache.org/legal/resolved.html#category-a as 
a yes  then the files RAT complains about can be excluded from the 
report. If you read it as a no, then we cannot include JQuery.


It reads like a yes to me.

The next question is: Do we need to add JQuery to our NOTICE file?

Gary





On Mon, Feb 10, 2014 at 8:46 PM, Remko Popma remko.po...@gmail.com 
wrote:

I agree with Nick.
Didn't we discuss this before, for the beta-9 release (and came to 
the same conclusion)?



On Tuesday, February 11, 2014, Nick Williams 
nicho...@nicholaswilliams.net wrote:
I'm not sure what our policy is, either, but there's nothing we can 
do about it. We can't modify the license header of those 
files—that would be in violation of the license under which 
JQuery is made available. And ceasing to use JQuery would make the 
site not very good anymore.


Either way, since this is JS for the site and not source code for 
Log4j, and since those files have been there for a very long time, 
I certainly don't think it should hold up this release.


Nick


On Feb 10, 2014, at 4:12 PM, Gary Gregory wrote:

RAT complains:

***

Unapproved licenses:

src/site/resources/js/jquery.js
src/site/resources/js/jquery.min.js

***
I'm not sure what our policy is for this kind of issue.

Gary



On Mon, Feb 10, 2014 at 2:56 PM, Nick Williams 
nicho...@nicholaswilliams.net wrote:



On Feb 9, 2014, at 1:56 PM, Nick Williams wrote:

This is a vote to release Log4j 2.0-rc1, the twelfth release of 
Log4j 2.0.


snip /

Please test and cast your votes.
[x] +1, release the artifacts

[ ] -1, don't release because...


Nick




--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
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




--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
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



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: [VOTE] Log4j 2.0-rc1 RC2

2014-02-11 Thread Christian Grobmeier


I think Rat is wrong on the jquery license.

They have included a header, but its not identified by rat.
MIT is a clear yes for me. We have several other portions of MIT code 
inside AL code (i.e. commons compress if i recall correctly).


If we want to put it into the NOTICE file we need to make sure to add 
bootstrap.min.js

and prettify.min.js as well (both AL 2.0)

I would not use a CDN because people might download it for a reason - 
maybe they

have no real connection where they want to work with it.



On 11 Feb 2014, at 3:20, Gary Gregory wrote:

This should be documented clearly in our build (in this case, in the 
POM).


Is the JQuery license compatible with ours?

If you read https://www.apache.org/legal/resolved.html#category-a as a
yes  then the files RAT complains about can be excluded from the 
report.

If you read it as a no, then we cannot include JQuery.

It reads like a yes to me.

The next question is: Do we need to add JQuery to our NOTICE file?

Gary





On Mon, Feb 10, 2014 at 8:46 PM, Remko Popma remko.po...@gmail.com 
wrote:



I agree with Nick.
Didn't we discuss this before, for the beta-9 release (and came to 
the

same conclusion)?


On Tuesday, February 11, 2014, Nick Williams 
nicho...@nicholaswilliams.net wrote:

I'm not sure what our policy is, either, but there's nothing we can 
do
about it. We can't modify the license header of those files—that 
would be
in violation of the license under which JQuery is made available. 
And

ceasing to use JQuery would make the site not very good anymore.

Either way, since this is JS for the site and not source code for 
Log4j,
and since those files have been there for a very long time, I 
certainly

don't think it should hold up this release.

Nick

On Feb 10, 2014, at 4:12 PM, Gary Gregory wrote:

RAT complains:

***

Unapproved licenses:

src/site/resources/js/jquery.js
src/site/resources/js/jquery.min.js

***

I'm not sure what our policy is for this kind of issue.

Gary



On Mon, Feb 10, 2014 at 2:56 PM, Nick Williams 
nicho...@nicholaswilliams.net wrote:



On Feb 9, 2014, at 1:56 PM, Nick Williams wrote:

*This is a vote to release Log4j 2.0-rc1, the twelfth release of 
Log4j

2.0.*

snip /

*Please test and cast your votes.*
[x] +1, release the artifacts

[ ] -1, don't release because...


Nick





--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second 
Editionhttp://www.manning.com/bauer3/

JUnit in Action, Second Edition http://www.manning.com/tahchiev/
Spring Batch in Action http://www.manning.com/templier/
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory






--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second 
Editionhttp://www.manning.com/bauer3/

JUnit in Action, Second Edition http://www.manning.com/tahchiev/
Spring Batch in Action http://www.manning.com/templier/
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Log4j 2.0-rc1 Lives to Release Another Day

2014-02-09 Thread Christian Grobmeier


hm, its there:
http://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk/src/site/site.vm

Does it exist on your system? If not maybe you should work on on a fresh 
checkout.


On 9 Feb 2014, at 7:56, Nick Williams wrote:


By the way, this is the error I'm getting when building site now:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on 
project log4j-distribution: Template file 
'/Users/Nicholas/Documents/Apache/Projects/log4j/log4j2/trunk/log4j-distribution/src/site/site.vm' 
does not exist - [Help 1]


As far as I can tell, nothing has changed with the log4j-distribution 
project since it worked this morning. I'm at a loss to explain this 
sudden failure. Help?


N

On Feb 9, 2014, at 12:43 AM, Nick Williams wrote:

I'm giving up for today. First pass: Resulted in a canceled vote. 
Second pass: Sonatype crashed halfway through and stopped accepting 
uploads to the staging repository. Third pass: Now `mvn site` fails 
with strange error about a missing file that it shouldn't be looking 
for to begin with. I give up trying to make this happen today.


I guess I'll try again tomorrow...

This process is a pain in the @$$...

Nick



-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Log4j 2.0-rc1 Lives to Release Another Day

2014-02-09 Thread Christian Grobmeier


I am not even coming that far.

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on 
project log4j: Execution default-site of goal 
org.apache.maven.plugins:maven-site-plugin:3.0:site failed: A required 
class was missing while executing 
org.apache.maven.plugins:maven-site-plugin:3.0:site: 
org/sonatype/aether/graph/DependencyFilter


i am going too look around, maybe when i understand whats causing this i 
will understand whats your problem too



On 9 Feb 2014, at 18:42, Nick Williams wrote:

I checked out a fresh trunk anyway and built site again. Same error, 
so it's not something wrong with my local copy. I don't 
understand...and we can't release until this is fixed. :-(


N

On Feb 9, 2014, at 11:14 AM, Nick Williams wrote:

No, that's not it. It's looking for the file 
/log4j-distribution/src/site/site.vm, not /src/site/site.vm. There's 
not even a /log4j-distribution/src/site directory in source control, 
much less a site.vm file in it.


Other than POM version changes for the attempted releases, there have 
been no changes to any files in /log4j-distribution in months.


svn diff -r HEAD shows that my local copy is identical to that on 
svn.apache.org.


Nick

On Feb 9, 2014, at 2:46 AM, Christian Grobmeier wrote:


hm, its there:
http://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk/src/site/site.vm

Does it exist on your system? If not maybe you should work on on a 
fresh checkout.


On 9 Feb 2014, at 7:56, Nick Williams wrote:


By the way, this is the error I'm getting when building site now:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) 
on project log4j-distribution: Template file 
'/Users/Nicholas/Documents/Apache/Projects/log4j/log4j2/trunk/log4j-distribution/src/site/site.vm' 
does not exist - [Help 1]


As far as I can tell, nothing has changed with the 
log4j-distribution project since it worked this morning. I'm at a 
loss to explain this sudden failure. Help?


N

On Feb 9, 2014, at 12:43 AM, Nick Williams wrote:

I'm giving up for today. First pass: Resulted in a canceled vote. 
Second pass: Sonatype crashed halfway through and stopped 
accepting uploads to the staging repository. Third pass: Now `mvn 
site` fails with strange error about a missing file that it 
shouldn't be looking for to begin with. I give up trying to make 
this happen today.


I guess I'll try again tomorrow...

This process is a pain in the @$$...

Nick



-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org






-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Log4j 2.0-rc1 Lives to Release Another Day

2014-02-09 Thread Christian Grobmeier


I get this error:
https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound

looks like i would need to downgrade maven to 3.0.

Weird, i never saw this before

On 9 Feb 2014, at 19:28, Nick Williams wrote:

I disabled the site plugin on the distribution module and that fixed 
my problem. I don't see why we would be running the site plugin on the 
distribution module, anyway. It has no site.


I've found info that says your error is a bug in Maven Site Plugin 
3.1. We can't use anything newer than 3.0 because of MSITE-695, but 
the parent samples module was referring to 3.1 just to disable the 
site plugin for all of the sample modules. That still doesn't explain 
why you're getting that error and I'm not, but I've changed this to 
3.0 just to be on the safe side.


Nick

On Feb 9, 2014, at 12:15 PM, Christian Grobmeier wrote:


I am not even coming that far.

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on 
project log4j: Execution default-site of goal 
org.apache.maven.plugins:maven-site-plugin:3.0:site failed: A 
required class was missing while executing 
org.apache.maven.plugins:maven-site-plugin:3.0:site: 
org/sonatype/aether/graph/DependencyFilter


i am going too look around, maybe when i understand whats causing 
this i will understand whats your problem too



On 9 Feb 2014, at 18:42, Nick Williams wrote:

I checked out a fresh trunk anyway and built site again. Same error, 
so it's not something wrong with my local copy. I don't 
understand...and we can't release until this is fixed. :-(


N

On Feb 9, 2014, at 11:14 AM, Nick Williams wrote:

No, that's not it. It's looking for the file 
/log4j-distribution/src/site/site.vm, not /src/site/site.vm. 
There's not even a /log4j-distribution/src/site directory in source 
control, much less a site.vm file in it.


Other than POM version changes for the attempted releases, there 
have been no changes to any files in /log4j-distribution in months.


svn diff -r HEAD shows that my local copy is identical to that on 
svn.apache.org.


Nick

On Feb 9, 2014, at 2:46 AM, Christian Grobmeier wrote:


hm, its there:
http://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk/src/site/site.vm

Does it exist on your system? If not maybe you should work on on a 
fresh checkout.


On 9 Feb 2014, at 7:56, Nick Williams wrote:


By the way, this is the error I'm getting when building site now:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.0:site 
(default-site) on project log4j-distribution: Template file 
'/Users/Nicholas/Documents/Apache/Projects/log4j/log4j2/trunk/log4j-distribution/src/site/site.vm' 
does not exist - [Help 1]


As far as I can tell, nothing has changed with the 
log4j-distribution project since it worked this morning. I'm at a 
loss to explain this sudden failure. Help?


N

On Feb 9, 2014, at 12:43 AM, Nick Williams wrote:

I'm giving up for today. First pass: Resulted in a canceled 
vote. Second pass: Sonatype crashed halfway through and stopped 
accepting uploads to the staging repository. Third pass: Now 
`mvn site` fails with strange error about a missing file that it 
shouldn't be looking for to begin with. I give up trying to make 
this happen today.


I guess I'll try again tomorrow...

This process is a pain in the @$$...

Nick



-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org






-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org




-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: CouchDb vs CouchDB


On 8 Feb 2014, at 5:51, Gary Gregory wrote:


On Fri, Feb 7, 2014 at 10:25 PM, Nick Williams 
nicho...@nicholaswilliams.net wrote:

Yes, they might as well follow the same pattern. I was already 
working on
the MongoDB provider, so I went ahead and renamed the package. I also 
added
items to changes.xml for both renames. I think this closes this 
discussion.


Thanks mate!





Agreed, ! :)

Gary




Nick

On Feb 7, 2014, at 3:51 PM, Christian Grobmeier wrote:


I am sorry that I didn't express myself better. For some reason I

thought everybody would know about the couchdb/couchbase issue.


I have committed the change to svn.

Sorry that I don't know if I should have opened an issue for this or 
add

an entry to changes.xml, maybe one can remind me...


And Nick: would you accept to rename mongo to mongodb for the same
reasons? The products name is mongodb actually. At the moment there 
is

nobody having some kind of mongobase to my knowledge but maybe we are
better being prepared... to many database vendors these days. What do 
you

think?


Thanks!


On 7 Feb 2014, at 17:55, Nick Williams wrote:


Ohhh okay. I misunderstood. H. Well I suppose in that case we

really must rename it, although I'm not super happy about it. But I'm
convinced it's necessary.


I guess we rename the couch package to couchdb.

Nick

On Feb 7, 2014, at 10:23 AM, Christian Grobmeier wrote:


folks thats what i meant.

Couchbase is a different database than CouchDB. They share the 
same

roots,

but meanwhile have some differences.

My guess is one needs a second appender.

The one we have seems to work with couchdb, so the package should 
be

named couchdb.

If we want to support couchbase, we need a new implementation

Its more precise. Nobody would just say log4 because its clear 
that

we mean java.


If I could convince you now, I would like to rename mongo to 
mongodb

too.


As Scott mentioned I would like to convince you (Nick) first, 
before I

do any change.


Hope this happened now :)






On 7 Feb 2014, at 17:16, Scott Deboy wrote:



I would appreciate if there wasn't even a threat of veto.

I would like to see folks ask questions and talk about concerns, 
and

then

only mention a veto when there is no other recourse.
On Feb 7, 2014 8:14 AM, Nick Williams 

nicho...@nicholaswilliams.net

wrote:

Yep. I would've accompanied any veto with technical 
justification.

Since I

can't come up with a technical justification for renaming it to

couchbase,

I won't veto it. :-)

N

On Feb 7, 2014, at 10:09 AM, Scott Deboy wrote:

I do want to remind everyone that vetoes are only valid if they 
are

backed

by a technical justification.

Scott
On Feb 7, 2014 8:07 AM, Nick Williams 

nicho...@nicholaswilliams.net

wrote:

I'm not convinced it really makes a difference, but it's better 
than
couchdb, so if the majority wants couchbase it I won't veto it. 
Be

sure to

change the test package name, too.

Nick

On Feb 7, 2014, at 10:03 AM, Scott Deboy wrote:

+1 to couchbase
On Feb 7, 2014 7:54 AM, Christian Grobmeier 
grobme...@gmail.com

wrote:


On 7 Feb 2014, at 16:19, Nick Williams wrote:

It doesn't so much matter because the XML element names are 
case

insensitive, but if we change the plugin name for CouchDB we

should
probably also change it for MongoDB. There's a reason I did 
that,

I just

can't remember what it was...

I don't see any compelling reason to rename the package. The

package

name for MongoDB is mongo. I don't like combining multiple

words into a

single package name segment, because we can't camel case them

(bad practice

to have cap letters in package names). Show me another NoSQL

database with

the word couch in it and I'll reconsider. :-)



couchbase maybe?




N

On Feb 7, 2014, at 9:12 AM, Christian Grobmeier wrote:

also the packagename is just couch, but it should better be

couchdb.
The name couch is misleading imho

On 7 Feb 2014, at 16:11, Christian Grobmeier wrote:

Hi


one minor thing in ClouchDBProvider:

* The Apache CouchDB implementation of {@link 
NoSQLProvider}.

*/
@Plugin(name = CouchDb, category = Core, printObject = 
true)

public final class CouchDBProvider

The name of this plugin is CouchDb while the correct name 
of

the

product
is CouchDB: couchdb.apache.org
Also our class and the comments do use the correct name. 
Just

the

plugin
name is lower case.

Any objections if I would change the plugin name to CouchDB

instead

of CouchDb?

Cheers




---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB



-
To unsubscribe, e-mail: 
log4j-dev-unsubscr...@logging.apache.org

For additional commands, e-mail:

log4j-dev-h...@logging.apache.org







-
To unsubscribe, e-mail: 
log4j-dev-unsubscr...@logging.apache.org

For additional commands, e-mail:

log4j-dev-h...@logging.apache.org

Author tags in xdocs

Hello,

we have a lot of 

author email=../author

tags in our docs. Thinking about the board recommendation to remove
author tags from the source code, I would like to bring up the 
discussion of removing author tags from the docs too.

I am not very oppinionated on this change, just want to bring it
up as I have looked in the docs today

Cheers
Christian

---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Can we roll RC1 tonight?


It looks weird that it says:
log4j-core-osgi-nosql-couch

shouldn't it be couchdb instead meanwhile?
Same for mongodb.

At least in the artifact ids its:
artifactIdlog4j-core-osgi-nosql-mongodb/artifactId

So maybe its some dependency which is still using the old artifact

Just a guess

On 8 Feb 2014, at 18:02, Nick Williams wrote:


The wiki does NOT have enough info on this...

I got the following error that prevent release from proceeding (and 
forced me to have to revert a bunch of staged changes):


[INFO] [ERROR] Failed to execute goal on project log4j-distribution: 
Could not resolve dependencies for project 
org.apache.logging.log4j:log4j-distribution:pom:2.0-rc1: The following 
artifacts could not be resolved: 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch:jar:2.0-rc1, 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongo:jar:2.0-rc1: 
Could not find artifact 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch:jar:2.0-rc1 
in oracleReleases (http://download.oracle.com/maven) - [Help 1]


This was after having received a bunch of prompts I wasn't expecting. 
I'm not sure I responded to them all correctly. Can anyone tell me 
what I should do next?


[INFO] Checking dependencies and plugins for snapshots ...
There are still some remaining snapshot dependencies.
: Do you want to resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All 
1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 
1: : 1
Dependency 'org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongo' 
is a snapshot (2.0-rc1-SNAPSHOT)

: Which release version should it be set to? 2.0-rc1: :
What version should the dependency be reset to for development? 
2.0-rc1: :
Dependency 'org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch' 
is a snapshot (2.0-rc1-SNAPSHOT)

: Which release version should it be set to? 2.0-rc1: :
What version should the dependency be reset to for development? 
2.0-rc1: :
What is the release version for Apache Log4j 2? 
(org.apache.logging.log4j:log4j) 2.0-rc1: :
What is the release version for Apache Log4j API? 
(org.apache.logging.log4j:log4j-api) 2.0-rc1: :
What is the release version for Apache Log4j Core? 
(org.apache.logging.log4j:log4j-core) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi Async? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-async) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi JPA? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-jpa) 2.0-rc1: :
What is the release version for Apache Log4j 1.x Compatibility API? 
(org.apache.logging.log4j:log4j-1.2-api) 2.0-rc1: :
What is the release version for Apache Log4J 1.x Compatibility 
Bundle? (org.apache.logging.log4j.osgi:log4j-1.2-osgi-api) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi Net? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-net) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi CouchDB? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couchdb) 2.0-rc1: 
:
What is the release version for Apache Log4J Core OSGi MongoDB? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongodb) 2.0-rc1: 
:
What is the release version for Apache Log4J Core OSGi? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-reduced) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi Bundles? 
(org.apache.logging.log4j.osgi:log4j-osgi) 2.0-rc1: :
What is the release version for Apache Log4j SLF4J Binding? 
(org.apache.logging.log4j:log4j-slf4j-impl) 2.0-rc1: :
What is the release version for Apache Log4j to SLF4J Adapter? 
(org.apache.logging.log4j:log4j-to-slf4j) 2.0-rc1: :
What is the release version for Apache Log4j Commons Logging Bridge? 
(org.apache.logging.log4j:log4j-jcl) 2.0-rc1: :
What is the release version for Apache Log4j Flume NG Bridge? 
(org.apache.logging.log4j:log4j-flume-ng) 2.0-rc1: :
What is the release version for Apache Log4j Tag Library? 
(org.apache.logging.log4j:log4j-taglib) 2.0-rc1: :
What is the release version for Apache Log4j JMX GUI? 
(org.apache.logging.log4j:log4j-jmx-gui) 2.0-rc1: :
What is the release version for Apache Log4j Samples? 
(org.apache.logging.log4j.samples:log4j-samples) 2.0-rc1: :
What is the release version for Apache Log4j Samples: Flume - 
Common? (org.apache.logging.log4j.samples:log4j-samples-flume-common) 
2.0-rc1: :
What is the release version for Apache Log4j Samples: Flume - 
Remote? (org.apache.logging.log4j.samples:log4j-samples-flume-remote) 
2.0-rc1: :
What is the release version for Apache Log4j Samples: Flume - 
Embedded? 
(org.apache.logging.log4j.samples:log4j-samples-flume-embedded) 
2.0-rc1: :
What is the release version for Log4j Distribution? 
(org.apache.logging.log4j:log4j-distribution) 2.0-rc1: :
What is SCM release tag or label for Apache Log4j 2? 
(org.apache.logging.log4j:log4j) log4j-2.0-rc1: :
What is the new development version for Apache Log4j 2? 
(org.apache.logging.log4j:log4j) 2.0-rc2-SNAPSHOT: :

Re: Can we roll RC1 tonight?


Nick,

i totally feel your pain. Releasing is always evil, i never experienced 
it otherwise in what ever project.


On 8 Feb 2014, at 19:56, Nick Williams wrote:
Well, after wasting a couple hours, it turns out I do NOT have the 
power to roll a release. I got a 401 Unauthorized error when it 
tried to deploy to the staging repository. I can log in to that 
repository in my browser, but I must not have deploy permissions. 
Fail.


I am not sure if you need extra permissions honestly.


I have reverted the automatic changes to trunk. It seems I can't 
delete a tag: DAV request failed: 411 Content length required. The 
server or an intermediate proxy does not accept chunked encoding. Try 
setting 'http-chunked-requests' to 'auto' or 'no' in your client 
configuration.


I need someone to:

- Delete the rc1 tag, please.


OK, so just confirming you want me to do:

svn delete 
https://svn.apache.org/repos/asf/logging/log4j/log4j2/tags/log4j-2.0-rc1/


Right?

- Either give me permissions to roll a release, or just do it for me. 
I've already run steps 1-5. The release notes have been committed.


I would prefer to give you the permissions, if there are any to give.
I will look around, maybe i find a hint.


Cheers
Christian




Nick

On Feb 8, 2014, at 12:13 PM, Nick Williams wrote:

Christian was right. The distribution POM was still referring to 
log4j-core-osgi-nosql-mongo and log4j-core-osgi-nosql-couch. I've 
fixed that. Continuing the release...


N

On Feb 8, 2014, at 12:11 PM, Ralph Goers wrote:

When you run the build you should have just had to hit enter a bunch 
of times to set they version.  I have never gotten messages like 
below when releasing.


Sent from my iPad

On Feb 8, 2014, at 9:02 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:



The wiki does NOT have enough info on this...

I got the following error that prevent release from proceeding (and 
forced me to have to revert a bunch of staged changes):


[INFO] [ERROR] Failed to execute goal on project 
log4j-distribution: Could not resolve dependencies for project 
org.apache.logging.log4j:log4j-distribution:pom:2.0-rc1: The 
following artifacts could not be resolved: 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch:jar:2.0-rc1, 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongo:jar:2.0-rc1: 
Could not find artifact 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch:jar:2.0-rc1 
in oracleReleases (http://download.oracle.com/maven) - [Help 1]


This was after having received a bunch of prompts I wasn't 
expecting. I'm not sure I responded to them all correctly. Can 
anyone tell me what I should do next?


[INFO] Checking dependencies and plugins for snapshots ...
There are still some remaining snapshot dependencies.
: Do you want to resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All 
1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): 
(0/1/2/3) 1: : 1
Dependency 
'org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongo' is a 
snapshot (2.0-rc1-SNAPSHOT)

: Which release version should it be set to? 2.0-rc1: :
What version should the dependency be reset to for development? 
2.0-rc1: :
Dependency 
'org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch' is a 
snapshot (2.0-rc1-SNAPSHOT)

: Which release version should it be set to? 2.0-rc1: :
What version should the dependency be reset to for development? 
2.0-rc1: :
What is the release version for Apache Log4j 2? 
(org.apache.logging.log4j:log4j) 2.0-rc1: :
What is the release version for Apache Log4j API? 
(org.apache.logging.log4j:log4j-api) 2.0-rc1: :
What is the release version for Apache Log4j Core? 
(org.apache.logging.log4j:log4j-core) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi Async? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-async) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi JPA? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-jpa) 2.0-rc1: :
What is the release version for Apache Log4j 1.x Compatibility 
API? (org.apache.logging.log4j:log4j-1.2-api) 2.0-rc1: :
What is the release version for Apache Log4J 1.x Compatibility 
Bundle? (org.apache.logging.log4j.osgi:log4j-1.2-osgi-api) 
2.0-rc1: :
What is the release version for Apache Log4J Core OSGi Net? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-net) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi CouchDB? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couchdb) 
2.0-rc1: :
What is the release version for Apache Log4J Core OSGi MongoDB? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongodb) 
2.0-rc1: :
What is the release version for Apache Log4J Core OSGi? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-reduced) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi Bundles? 
(org.apache.logging.log4j.osgi:log4j-osgi) 2.0-rc1: :
What is the release version for Apache Log4j SLF4J Binding? 
(org.apache.logging.log4j:log4j-slf4j-impl)

Re: Can we roll RC1 tonight?

I just remembered something which confuses me for a while. Maybe it 
helps, but maybe somebody else here on this list can show me/us a better 
way.


When I made a release in the past days, I had to add some commandline 
parameters, like:


mvn -P apache-release release:prepare release:perform 
-Dusername=apacheid -Dpassword=apachepass -Dgpg.username=usernam 
-Dgpg.password=pass


You might already be sceptic that you have to use the password by cli 
which is then visible by every other user on your machine running ps.


For me this was the only thing which worked out. I had the passwords etc 
encrypted in some profile, but they just weren't used.
Like: 
https://docs.sonatype.org/display/Repository/Deploy+Snapshots+and+Stage+Releases+with+Ant


So maybe it is the same case for you. I asked around for quite a while 
but never got a proper response how to handle this.
Many people never run into that issue and so I think its somehow related 
to my setup. Recently I found out another apache guy has the same 
problem, solving it the same way.


maybe worth a shot.



On 8 Feb 2014, at 20:06, Christian Grobmeier wrote:


Nick,

i totally feel your pain. Releasing is always evil, i never 
experienced it otherwise in what ever project.


On 8 Feb 2014, at 19:56, Nick Williams wrote:
Well, after wasting a couple hours, it turns out I do NOT have the 
power to roll a release. I got a 401 Unauthorized error when it 
tried to deploy to the staging repository. I can log in to that 
repository in my browser, but I must not have deploy permissions. 
Fail.


I am not sure if you need extra permissions honestly.


I have reverted the automatic changes to trunk. It seems I can't 
delete a tag: DAV request failed: 411 Content length required. The 
server or an intermediate proxy does not accept chunked encoding. Try 
setting 'http-chunked-requests' to 'auto' or 'no' in your client 
configuration.


I need someone to:

- Delete the rc1 tag, please.


OK, so just confirming you want me to do:

svn delete 
https://svn.apache.org/repos/asf/logging/log4j/log4j2/tags/log4j-2.0-rc1/


Right?

- Either give me permissions to roll a release, or just do it for me. 
I've already run steps 1-5. The release notes have been committed.


I would prefer to give you the permissions, if there are any to give.
I will look around, maybe i find a hint.


Cheers
Christian




Nick

On Feb 8, 2014, at 12:13 PM, Nick Williams wrote:

Christian was right. The distribution POM was still referring to 
log4j-core-osgi-nosql-mongo and log4j-core-osgi-nosql-couch. I've 
fixed that. Continuing the release...


N

On Feb 8, 2014, at 12:11 PM, Ralph Goers wrote:

When you run the build you should have just had to hit enter a 
bunch of times to set they version.  I have never gotten messages 
like below when releasing.


Sent from my iPad

On Feb 8, 2014, at 9:02 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:



The wiki does NOT have enough info on this...

I got the following error that prevent release from proceeding 
(and forced me to have to revert a bunch of staged changes):


[INFO] [ERROR] Failed to execute goal on project 
log4j-distribution: Could not resolve dependencies for project 
org.apache.logging.log4j:log4j-distribution:pom:2.0-rc1: The 
following artifacts could not be resolved: 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch:jar:2.0-rc1, 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongo:jar:2.0-rc1: 
Could not find artifact 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch:jar:2.0-rc1 
in oracleReleases (http://download.oracle.com/maven) - [Help 1]


This was after having received a bunch of prompts I wasn't 
expecting. I'm not sure I responded to them all correctly. Can 
anyone tell me what I should do next?


[INFO] Checking dependencies and plugins for snapshots ...
There are still some remaining snapshot dependencies.
: Do you want to resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All 
1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): 
(0/1/2/3) 1: : 1
Dependency 
'org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongo' is a 
snapshot (2.0-rc1-SNAPSHOT)

: Which release version should it be set to? 2.0-rc1: :
What version should the dependency be reset to for development? 
2.0-rc1: :
Dependency 
'org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch' is a 
snapshot (2.0-rc1-SNAPSHOT)

: Which release version should it be set to? 2.0-rc1: :
What version should the dependency be reset to for development? 
2.0-rc1: :
What is the release version for Apache Log4j 2? 
(org.apache.logging.log4j:log4j) 2.0-rc1: :
What is the release version for Apache Log4j API? 
(org.apache.logging.log4j:log4j-api) 2.0-rc1: :
What is the release version for Apache Log4j Core? 
(org.apache.logging.log4j:log4j-core) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi Async? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-async) 2.0-rc1

Re: Can we roll RC1 tonight?


On 8 Feb 2014, at 20:11, Nick Williams wrote:

On Feb 8, 2014, at 1:06 PM, Christian Grobmeier wrote:

OK, so just confirming you want me to do:
svn delete 
https://svn.apache.org/repos/asf/logging/log4j/log4j2/tags/log4j-2.0-rc1/


Correct. Please delete that.


OK, its done.


I would prefer to give you the permissions, if there are any to give.
I will look around, maybe i find a hint.


Some Googling reveals that I need to edit ~/.m2/settings.xml and add 
my repository username and password to it. Why it can't just PROMPT me 
for my username and password is beyond me. I'll update the wiki with 
more info after all of this. Just delete that tag and I'll make 
another attempt.


Please also note my other mail - you may need additional -D params 
duplicating password info.


And yes, updating the wiki is always welcome.



Nick




Cheers
Christian




Nick

On Feb 8, 2014, at 12:13 PM, Nick Williams wrote:

Christian was right. The distribution POM was still referring to 
log4j-core-osgi-nosql-mongo and log4j-core-osgi-nosql-couch. I've 
fixed that. Continuing the release...


N

On Feb 8, 2014, at 12:11 PM, Ralph Goers wrote:

When you run the build you should have just had to hit enter a 
bunch of times to set they version.  I have never gotten messages 
like below when releasing.


Sent from my iPad

On Feb 8, 2014, at 9:02 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:



The wiki does NOT have enough info on this...

I got the following error that prevent release from proceeding 
(and forced me to have to revert a bunch of staged changes):


[INFO] [ERROR] Failed to execute goal on project 
log4j-distribution: Could not resolve dependencies for project 
org.apache.logging.log4j:log4j-distribution:pom:2.0-rc1: The 
following artifacts could not be resolved: 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch:jar:2.0-rc1, 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongo:jar:2.0-rc1: 
Could not find artifact 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch:jar:2.0-rc1 
in oracleReleases (http://download.oracle.com/maven) - [Help 1]


This was after having received a bunch of prompts I wasn't 
expecting. I'm not sure I responded to them all correctly. Can 
anyone tell me what I should do next?


[INFO] Checking dependencies and plugins for snapshots ...
There are still some remaining snapshot dependencies.
: Do you want to resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All 
1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): 
(0/1/2/3) 1: : 1
Dependency 
'org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongo' is a 
snapshot (2.0-rc1-SNAPSHOT)

: Which release version should it be set to? 2.0-rc1: :
What version should the dependency be reset to for development? 
2.0-rc1: :
Dependency 
'org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch' is a 
snapshot (2.0-rc1-SNAPSHOT)

: Which release version should it be set to? 2.0-rc1: :
What version should the dependency be reset to for development? 
2.0-rc1: :
What is the release version for Apache Log4j 2? 
(org.apache.logging.log4j:log4j) 2.0-rc1: :
What is the release version for Apache Log4j API? 
(org.apache.logging.log4j:log4j-api) 2.0-rc1: :
What is the release version for Apache Log4j Core? 
(org.apache.logging.log4j:log4j-core) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi Async? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-async) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi JPA? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-jpa) 2.0-rc1: :
What is the release version for Apache Log4j 1.x Compatibility 
API? (org.apache.logging.log4j:log4j-1.2-api) 2.0-rc1: :
What is the release version for Apache Log4J 1.x Compatibility 
Bundle? (org.apache.logging.log4j.osgi:log4j-1.2-osgi-api) 
2.0-rc1: :
What is the release version for Apache Log4J Core OSGi Net? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-net) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi CouchDB? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couchdb) 
2.0-rc1: :
What is the release version for Apache Log4J Core OSGi MongoDB? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongodb) 
2.0-rc1: :
What is the release version for Apache Log4J Core OSGi? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-reduced) 2.0-rc1: 
:
What is the release version for Apache Log4J Core OSGi Bundles? 
(org.apache.logging.log4j.osgi:log4j-osgi) 2.0-rc1: :
What is the release version for Apache Log4j SLF4J Binding? 
(org.apache.logging.log4j:log4j-slf4j-impl) 2.0-rc1: :
What is the release version for Apache Log4j to SLF4J Adapter? 
(org.apache.logging.log4j:log4j-to-slf4j) 2.0-rc1: :
What is the release version for Apache Log4j Commons Logging 
Bridge? (org.apache.logging.log4j:log4j-jcl) 2.0-rc1: :
What is the release version for Apache Log4j Flume NG Bridge? 
(org.apache.logging.log4j:log4j-flume-ng) 2.0-rc1: :
What is the release

Re: Can we roll RC1 tonight?


On 8 Feb 2014, at 21:12, Nick Williams wrote:

Almost done. In the vote email, I'm supposed to, Provide a list of 
the artifacts by copying from the email sent from the Nexus 
Repository. I didn't get an email from the Nexus Repository. Perhaps 
that only went to the PMC? Can someone forward that email to me 
privately?


I haven't seen an email to the PMC. If it would be sent to private it 
would need to go to public anyway as this is not confidential.


Great you have made it, thanks! I am going to vote tomorrow.





Nick

On Feb 8, 2014, at 1:17 PM, Christian Grobmeier wrote:


On 8 Feb 2014, at 20:11, Nick Williams wrote:

On Feb 8, 2014, at 1:06 PM, Christian Grobmeier wrote:

OK, so just confirming you want me to do:
svn delete 
https://svn.apache.org/repos/asf/logging/log4j/log4j2/tags/log4j-2.0-rc1/


Correct. Please delete that.


OK, its done.

I would prefer to give you the permissions, if there are any to 
give.

I will look around, maybe i find a hint.


Some Googling reveals that I need to edit ~/.m2/settings.xml and add 
my repository username and password to it. Why it can't just PROMPT 
me for my username and password is beyond me. I'll update the wiki 
with more info after all of this. Just delete that tag and I'll make 
another attempt.


Please also note my other mail - you may need additional -D params 
duplicating password info.


And yes, updating the wiki is always welcome.



Nick




Cheers
Christian




Nick

On Feb 8, 2014, at 12:13 PM, Nick Williams wrote:

Christian was right. The distribution POM was still referring to 
log4j-core-osgi-nosql-mongo and log4j-core-osgi-nosql-couch. I've 
fixed that. Continuing the release...


N

On Feb 8, 2014, at 12:11 PM, Ralph Goers wrote:

When you run the build you should have just had to hit enter a 
bunch of times to set they version.  I have never gotten 
messages like below when releasing.


Sent from my iPad

On Feb 8, 2014, at 9:02 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:



The wiki does NOT have enough info on this...

I got the following error that prevent release from proceeding 
(and forced me to have to revert a bunch of staged changes):


[INFO] [ERROR] Failed to execute goal on project 
log4j-distribution: Could not resolve dependencies for project 
org.apache.logging.log4j:log4j-distribution:pom:2.0-rc1: The 
following artifacts could not be resolved: 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch:jar:2.0-rc1, 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongo:jar:2.0-rc1: 
Could not find artifact 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch:jar:2.0-rc1 
in oracleReleases (http://download.oracle.com/maven) - [Help 
1]


This was after having received a bunch of prompts I wasn't 
expecting. I'm not sure I responded to them all correctly. Can 
anyone tell me what I should do next?


[INFO] Checking dependencies and plugins for snapshots ...
There are still some remaining snapshot dependencies.
: Do you want to resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 
0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions 
): (0/1/2/3) 1: : 1
Dependency 
'org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongo' is 
a snapshot (2.0-rc1-SNAPSHOT)

: Which release version should it be set to? 2.0-rc1: :
What version should the dependency be reset to for development? 
2.0-rc1: :
Dependency 
'org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch' is 
a snapshot (2.0-rc1-SNAPSHOT)

: Which release version should it be set to? 2.0-rc1: :
What version should the dependency be reset to for development? 
2.0-rc1: :
What is the release version for Apache Log4j 2? 
(org.apache.logging.log4j:log4j) 2.0-rc1: :
What is the release version for Apache Log4j API? 
(org.apache.logging.log4j:log4j-api) 2.0-rc1: :
What is the release version for Apache Log4j Core? 
(org.apache.logging.log4j:log4j-core) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi Async? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-async) 2.0-rc1: 
:
What is the release version for Apache Log4J Core OSGi JPA? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-jpa) 2.0-rc1: :
What is the release version for Apache Log4j 1.x Compatibility 
API? (org.apache.logging.log4j:log4j-1.2-api) 2.0-rc1: :
What is the release version for Apache Log4J 1.x Compatibility 
Bundle? (org.apache.logging.log4j.osgi:log4j-1.2-osgi-api) 
2.0-rc1: :
What is the release version for Apache Log4J Core OSGi Net? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-net) 2.0-rc1: :
What is the release version for Apache Log4J Core OSGi 
CouchDB? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couchdb) 
2.0-rc1: :
What is the release version for Apache Log4J Core OSGi 
MongoDB? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongodb) 
2.0-rc1: :
What is the release version for Apache Log4J Core OSGi? 
(org.apache.logging.log4j.osgi:log4j-core-osgi-reduced) 
2.0-rc1: :
What

CouchDb vs CouchDB


Hi

one minor thing in ClouchDBProvider:

* The Apache CouchDB implementation of {@link NoSQLProvider}.
 */
@Plugin(name = CouchDb, category = Core, printObject = true)
public final class CouchDBProvider

The name of this plugin is CouchDb while the correct name of the 
product

is CouchDB: couchdb.apache.org
Also our class and the comments do use the correct name. Just the plugin
name is lower case.

Any objections if I would change the plugin name to CouchDB instead of 
CouchDb?


Cheers

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: CouchDb vs CouchDB


also the packagename is just couch, but it should better be couchdb.
The name couch is misleading imho

On 7 Feb 2014, at 16:11, Christian Grobmeier wrote:


Hi

one minor thing in ClouchDBProvider:

* The Apache CouchDB implementation of {@link NoSQLProvider}.
*/
@Plugin(name = CouchDb, category = Core, printObject = true)
public final class CouchDBProvider

The name of this plugin is CouchDb while the correct name of the 
product

is CouchDB: couchdb.apache.org
Also our class and the comments do use the correct name. Just the 
plugin

name is lower case.

Any objections if I would change the plugin name to CouchDB instead of 
CouchDb?


Cheers



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: CouchDb vs CouchDB


On 7 Feb 2014, at 16:19, Nick Williams wrote:

It doesn't so much matter because the XML element names are case 
insensitive, but if we change the plugin name for CouchDB we should 
probably also change it for MongoDB. There's a reason I did that, I 
just can't remember what it was...


I don't see any compelling reason to rename the package. The package 
name for MongoDB is mongo. I don't like combining multiple words 
into a single package name segment, because we can't camel case them 
(bad practice to have cap letters in package names). Show me another 
NoSQL database with the word couch in it and I'll reconsider. :-)


couchbase maybe?




N

On Feb 7, 2014, at 9:12 AM, Christian Grobmeier wrote:

also the packagename is just couch, but it should better be 
couchdb.

The name couch is misleading imho

On 7 Feb 2014, at 16:11, Christian Grobmeier wrote:


Hi

one minor thing in ClouchDBProvider:

* The Apache CouchDB implementation of {@link NoSQLProvider}.
*/
@Plugin(name = CouchDb, category = Core, printObject = true)
public final class CouchDBProvider

The name of this plugin is CouchDb while the correct name of the 
product

is CouchDB: couchdb.apache.org
Also our class and the comments do use the correct name. Just the 
plugin

name is lower case.

Any objections if I would change the plugin name to CouchDB instead 
of CouchDb?


Cheers



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org




-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: CouchDb vs CouchDB


folks thats what i meant.

Couchbase is a different database than CouchDB. They share the same 
roots,

but meanwhile have some differences.

My guess is one needs a second appender.

The one we have seems to work with couchdb, so the package should be 
named couchdb.

If we want to support couchbase, we need a new implementation

Its more precise. Nobody would just say log4 because its clear that we 
mean java.


If I could convince you now, I would like to rename mongo to mongodb 
too.


As Scott mentioned I would like to convince you (Nick) first, before I 
do any change.


Hope this happened now :)






On 7 Feb 2014, at 17:16, Scott Deboy wrote:



I would appreciate if there wasn't even a threat of veto.

I would like to see folks ask questions and talk about concerns, and 
then

only mention a veto when there is no other recourse.
On Feb 7, 2014 8:14 AM, Nick Williams 
nicho...@nicholaswilliams.net

wrote:

Yep. I would've accompanied any veto with technical justification. 
Since I
can't come up with a technical justification for renaming it to 
couchbase,

I won't veto it. :-)

N

On Feb 7, 2014, at 10:09 AM, Scott Deboy wrote:

I do want to remind everyone that vetoes are only valid if they are 
backed

by a technical justification.

Scott
On Feb 7, 2014 8:07 AM, Nick Williams 
nicho...@nicholaswilliams.net

wrote:


I'm not convinced it really makes a difference, but it's better than
couchdb, so if the majority wants couchbase it I won't veto it. Be 
sure to

change the test package name, too.

Nick

On Feb 7, 2014, at 10:03 AM, Scott Deboy wrote:

+1 to couchbase
On Feb 7, 2014 7:54 AM, Christian Grobmeier grobme...@gmail.com
wrote:


On 7 Feb 2014, at 16:19, Nick Williams wrote:

It doesn't so much matter because the XML element names are case
insensitive, but if we change the plugin name for CouchDB we 
should
probably also change it for MongoDB. There's a reason I did that, 
I just

can't remember what it was...

I don't see any compelling reason to rename the package. The 
package
name for MongoDB is mongo. I don't like combining multiple words 
into a
single package name segment, because we can't camel case them (bad 
practice
to have cap letters in package names). Show me another NoSQL 
database with

the word couch in it and I'll reconsider. :-)



couchbase maybe?




N

On Feb 7, 2014, at 9:12 AM, Christian Grobmeier wrote:

also the packagename is just couch, but it should better be

couchdb.
The name couch is misleading imho

On 7 Feb 2014, at 16:11, Christian Grobmeier wrote:

Hi


one minor thing in ClouchDBProvider:

* The Apache CouchDB implementation of {@link NoSQLProvider}.
*/
@Plugin(name = CouchDb, category = Core, printObject = true)
public final class CouchDBProvider

The name of this plugin is CouchDb while the correct name of 
the

product
is CouchDB: couchdb.apache.org
Also our class and the comments do use the correct name. Just 
the

plugin
name is lower case.

Any objections if I would change the plugin name to CouchDB 
instead

of CouchDb?

Cheers




---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org





-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org




---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org









---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: GA?


Let me do the package rename from couch to couchdb.
I am just after it

On 7 Feb 2014, at 19:29, Remko Popma wrote:


Any showstoppers left for anyone?

https://issues.apache.org/jira/browse/LOG4J2-529 is not great, but not 
sure

if it qualifies as a showstopper...

I'll see if I can find time to work on
https://issues.apache.org/jira/browse/LOG4J2-520 this weekend, but 
this is
not a showstopper IMHO. So I'd be fine with doing a release with what 
we

have now.

Cheers, -Remko


On Wed, Jan 29, 2014 at 1:17 AM, Christian Grobmeier 
grobme...@gmail.comwrote:



On 28 Jan 2014, at 1:45, Ralph Goers wrote:

I agree with that, but that doesn't mean we can't add new stuff to 
the

API.



I would like to highlight that!

Anyway happy with the proposed time plan :-)

Cheers





Ralph

On Jan 27, 2014, at 2:08 PM, Gary Gregory garydgreg...@gmail.com 
wrote:


IMO: We cannot/should not break binary compatibility without a major
release change (and accompanying package and Maven coordinate 
changes).


Gary


On Mon, Jan 27, 2014 at 4:59 PM, Remko Popma 
remko.po...@gmail.com

wrote:
How about an RC now (after showstoppers are fixed),
then the GA release say one month later?

Keep in mind we can still have bugix releases in 2.0.1, etc, and 
even

API changes in 2.1 etc...


On Tuesday, January 28, 2014, Matt Sicker boa...@gmail.com wrote:
I agree on putting out an RC release. I think it might help spur 
some

3rd party development to integrate with the new version.


On 27 January 2014 12:37, Gary Gregory garydgreg...@gmail.com 
wrote:
So, yes, the new level API needs to go through a non-GA release. 
Aside
from that, I am behind in my Log4j2 homework to see how much work 
it will
be to convert our Log4j1 code and extensions to v2. But that's just 
an

issue on my end that should not hold up everyone else.

I've been out of 100% commission for almost a week so I need to try 
and

use the new level system...

Gary


On Mon, Jan 27, 2014 at 11:18 AM, Ralph Goers 
ralph.go...@dslextreme.com wrote:
Due to the API change I can agree with having another beta or an RC 
but
the reason I asked about GA is that I am not aware of very many 
showstopper
issues that need to be addressed.  I am sensing that you have a 
real
reluctance to have Log4j 2 released as GA and I am trying to 
understand

what the reason is.

Ralph

On Jan 27, 2014, at 6:15 AM, Gary Gregory garydgreg...@gmail.com
wrote:

I agree with Nick. Changing levels to be extensible warrants 
another

Beta. I'd like to see a stable API before we get into RC mode.

What about:

- Now: Another Beta
- +1 month, If the API is stable: RC1
- RCs until shows stoppers are fixed, pick a rhythm: once a week 
may be
too much, once a month too long. Every two weeks seems pretty 
frequent for

our bunch for a ramp down.

Thoughts on that?

I am not so much concerned about OSGi now since I look at this as 
more
of a packaging issue and how much gets dragged in the container 
with
dependencies. For OSGi, are we really considering delivering one 
bundle

(jar) per appender?

I am more concerned about all the issues people seem to have in 
servlet

environments.


Gary


On Mon, Jan 27, 2014 at 7:22 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:
I wouldn't necessarily vote against a GA, but given that we just
MAJORLY overhauled Level, I think a brief RC is in order. It would 
be a
shame if someone found a problem with Level a week after GA that 
caused us

to need to change the API to fix it.
Nick


On Jan 27, 2014, at 12:51 AM, Remko Popma wrote:

I'd like to fix LOG4J-412 and 448, but neither of them are

showstoppers IMHO.

Remko

On Monday, January 27, 2014, Ralph Goers 
ralph.go...@dslextreme.com

wrote:
Since we are having good discussions I would also like to find 
out

what are blockers to a GA release.  My list includes:
1. The fix Nick is working on to allow Servlet initialization to 
be

disabled from automatically happening in a 3.0 container.
2. Support for programmatic configuration of Loggers. I planned 
on
working on that this weekend but worked on the custom levels 
instead.


While I believe better support for OSGi is necessary I don't 
believe

we will be able to do that for GA.

Are there any other Jira issues or features that anybody else 
feels is

required?

Ralph
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org






--

Matt Sicker boa...@gmail.com



--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
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





---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

Re: GA?


It's ok for me to make an RC.

I would like to avoid the beta from a community perspective.
I also don't don't think that we are beta anymore and it would
be misleading for the community. In fact, having a RC would
show we are close before.

You are more the beta guy where I am usually more into GA, so can we
find a compromise on RC?

Cheers
Christian

On 7 Feb 2014, at 22:07, Gary Gregory wrote:

I think the next release should be an RC (or beta), not the GA. There 
are

just too many changes since beta-9 IMO.

Ideally, there should only be minor fixes from RC to GA.

Gary


On Fri, Feb 7, 2014 at 4:03 PM, Christian Grobmeier 
grobme...@gmail.comwrote:



Let me do the package rename from couch to couchdb.
I am just after it


On 7 Feb 2014, at 19:29, Remko Popma wrote:

Any showstoppers left for anyone?


https://issues.apache.org/jira/browse/LOG4J2-529 is not great, but 
not

sure
if it qualifies as a showstopper...

I'll see if I can find time to work on
https://issues.apache.org/jira/browse/LOG4J2-520 this weekend, but 
this

is
not a showstopper IMHO. So I'd be fine with doing a release with 
what we

have now.

Cheers, -Remko


On Wed, Jan 29, 2014 at 1:17 AM, Christian Grobmeier 
grobme...@gmail.com

wrote:


On 28 Jan 2014, at 1:45, Ralph Goers wrote:


I agree with that, but that doesn't mean we can't add new stuff to 
the



API.



I would like to highlight that!

Anyway happy with the proposed time plan :-)

Cheers




Ralph


On Jan 27, 2014, at 2:08 PM, Gary Gregory garydgreg...@gmail.com
wrote:

IMO: We cannot/should not break binary compatibility without a 
major


release change (and accompanying package and Maven coordinate 
changes).


Gary


On Mon, Jan 27, 2014 at 4:59 PM, Remko Popma 
remko.po...@gmail.com

wrote:
How about an RC now (after showstoppers are fixed),
then the GA release say one month later?

Keep in mind we can still have bugix releases in 2.0.1, etc, and 
even

API changes in 2.1 etc...


On Tuesday, January 28, 2014, Matt Sicker boa...@gmail.com 
wrote:
I agree on putting out an RC release. I think it might help spur 
some

3rd party development to integrate with the new version.


On 27 January 2014 12:37, Gary Gregory garydgreg...@gmail.com 
wrote:
So, yes, the new level API needs to go through a non-GA release. 
Aside
from that, I am behind in my Log4j2 homework to see how much work 
it

will
be to convert our Log4j1 code and extensions to v2. But that's 
just an

issue on my end that should not hold up everyone else.

I've been out of 100% commission for almost a week so I need to 
try and

use the new level system...

Gary


On Mon, Jan 27, 2014 at 11:18 AM, Ralph Goers 
ralph.go...@dslextreme.com wrote:
Due to the API change I can agree with having another beta or an 
RC but

the reason I asked about GA is that I am not aware of very many
showstopper
issues that need to be addressed.  I am sensing that you have a 
real
reluctance to have Log4j 2 released as GA and I am trying to 
understand

what the reason is.

Ralph

On Jan 27, 2014, at 6:15 AM, Gary Gregory 
garydgreg...@gmail.com

wrote:

I agree with Nick. Changing levels to be extensible warrants 
another



Beta. I'd like to see a stable API before we get into RC mode.

What about:

- Now: Another Beta
- +1 month, If the API is stable: RC1
- RCs until shows stoppers are fixed, pick a rhythm: once a week 
may

be
too much, once a month too long. Every two weeks seems pretty
frequent for
our bunch for a ramp down.

Thoughts on that?

I am not so much concerned about OSGi now since I look at this 
as more
of a packaging issue and how much gets dragged in the container 
with

dependencies. For OSGi, are we really considering delivering one
bundle
(jar) per appender?

I am more concerned about all the issues people seem to have in
servlet
environments.


Gary


On Mon, Jan 27, 2014 at 7:22 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:
I wouldn't necessarily vote against a GA, but given that we just
MAJORLY overhauled Level, I think a brief RC is in order. It 
would be

a
shame if someone found a problem with Level a week after GA that
caused us
to need to change the API to fix it.
Nick


On Jan 27, 2014, at 12:51 AM, Remko Popma wrote:

I'd like to fix LOG4J-412 and 448, but neither of them are


showstoppers IMHO.

Remko

On Monday, January 27, 2014, Ralph Goers 
ralph.go...@dslextreme.com



wrote:
Since we are having good discussions I would also like to find 
out

what are blockers to a GA release.  My list includes:
1. The fix Nick is working on to allow Servlet initialization 
to be

disabled from automatically happening in a 3.0 container.
2. Support for programmatic configuration of Loggers. I planned 
on
working on that this weekend but worked on the custom levels 
instead.


While I believe better support for OSGi is necessary I don't 
believe

we will be able to do that for GA.

Are there any other Jira issues or features that anybody else 
feels

is
required?

Ralph

Re: GA?


On 7 Feb 2014, at 22:25, Gary Gregory wrote:

On Fri, Feb 7, 2014 at 4:15 PM, Christian Grobmeier 
grobme...@gmail.comwrote:



It's ok for me to make an RC.

I would like to avoid the beta from a community perspective.
I also don't don't think that we are beta anymore and it would
be misleading for the community. In fact, having a RC would
show we are close before.

You are more the beta guy where I am usually more into GA, so can we
find a compromise on RC?



Sure, you can put whatever label it, but I think there should be as 
many

releases as needed until we have an RC-n to GA with very few changes.

For example:

RC-1: the giant set of changes since beta-9
RC-2: fixes
...
GA: API frozen until 3.0


I get your point.

My feeling says there will not be too many big changes in future.
If others feel different i am fine with beta.
If others think like me I am happy about RC and trying to keep 
modifications low.




Gary

Gary



Cheers
Christian

On 7 Feb 2014, at 22:07, Gary Gregory wrote:

I think the next release should be an RC (or beta), not the GA. There 
are

just too many changes since beta-9 IMO.

Ideally, there should only be minor fixes from RC to GA.

Gary


On Fri, Feb 7, 2014 at 4:03 PM, Christian Grobmeier 
grobme...@gmail.com

wrote:


Let me do the package rename from couch to couchdb.

I am just after it


On 7 Feb 2014, at 19:29, Remko Popma wrote:

Any showstoppers left for anyone?



https://issues.apache.org/jira/browse/LOG4J2-529 is not great, but 
not

sure
if it qualifies as a showstopper...

I'll see if I can find time to work on
https://issues.apache.org/jira/browse/LOG4J2-520 this weekend, but 
this

is
not a showstopper IMHO. So I'd be fine with doing a release with 
what we

have now.

Cheers, -Remko


On Wed, Jan 29, 2014 at 1:17 AM, Christian Grobmeier 
grobme...@gmail.com


wrote:



On 28 Jan 2014, at 1:45, Ralph Goers wrote:



I agree with that, but that doesn't mean we can't add new stuff 
to the


API.



I would like to highlight that!


Anyway happy with the proposed time plan :-)

Cheers




Ralph



On Jan 27, 2014, at 2:08 PM, Gary Gregory 
garydgreg...@gmail.com

wrote:

IMO: We cannot/should not break binary compatibility without a 
major


release change (and accompanying package and Maven coordinate

changes).

Gary


On Mon, Jan 27, 2014 at 4:59 PM, Remko Popma 
remko.po...@gmail.com

wrote:
How about an RC now (after showstoppers are fixed),
then the GA release say one month later?

Keep in mind we can still have bugix releases in 2.0.1, etc, 
and even

API changes in 2.1 etc...


On Tuesday, January 28, 2014, Matt Sicker boa...@gmail.com 
wrote:
I agree on putting out an RC release. I think it might help 
spur some

3rd party development to integrate with the new version.


On 27 January 2014 12:37, Gary Gregory garydgreg...@gmail.com
wrote:
So, yes, the new level API needs to go through a non-GA 
release.

Aside
from that, I am behind in my Log4j2 homework to see how much 
work it

will
be to convert our Log4j1 code and extensions to v2. But that's 
just

an
issue on my end that should not hold up everyone else.

I've been out of 100% commission for almost a week so I need to 
try

and
use the new level system...

Gary


On Mon, Jan 27, 2014 at 11:18 AM, Ralph Goers 
ralph.go...@dslextreme.com wrote:
Due to the API change I can agree with having another beta or 
an RC

but
the reason I asked about GA is that I am not aware of very many
showstopper
issues that need to be addressed.  I am sensing that you have a 
real

reluctance to have Log4j 2 released as GA and I am trying to
understand
what the reason is.

Ralph

On Jan 27, 2014, at 6:15 AM, Gary Gregory 
garydgreg...@gmail.com

wrote:

I agree with Nick. Changing levels to be extensible warrants 
another


Beta. I'd like to see a stable API before we get into RC mode.


What about:

- Now: Another Beta
- +1 month, If the API is stable: RC1
- RCs until shows stoppers are fixed, pick a rhythm: once a 
week may

be
too much, once a month too long. Every two weeks seems pretty
frequent for
our bunch for a ramp down.

Thoughts on that?

I am not so much concerned about OSGi now since I look at this 
as

more
of a packaging issue and how much gets dragged in the 
container with
dependencies. For OSGi, are we really considering delivering 
one

bundle
(jar) per appender?

I am more concerned about all the issues people seem to have 
in

servlet
environments.


Gary


On Mon, Jan 27, 2014 at 7:22 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:
I wouldn't necessarily vote against a GA, but given that we 
just
MAJORLY overhauled Level, I think a brief RC is in order. It 
would

be
a
shame if someone found a problem with Level a week after GA 
that

caused us
to need to change the API to fix it.
Nick


On Jan 27, 2014, at 12:51 AM, Remko Popma wrote:

I'd like to fix LOG4J-412 and 448, but neither of them are

showstoppers IMHO.


Remko

On Monday, January 27, 2014, Ralph Goers 
ralph.go

Re: CouchDb vs CouchDB

I am sorry that I didn't express myself better. For some reason I 
thought everybody would know about the couchdb/couchbase issue.


I have committed the change to svn.

Sorry that I don't know if I should have opened an issue for this or add 
an entry to changes.xml, maybe one can remind me...


And Nick: would you accept to rename mongo to mongodb for the same 
reasons? The products name is mongodb actually. At the moment there is 
nobody having some kind of mongobase to my knowledge but maybe we are 
better being prepared... to many database vendors these days. What do 
you think?


Thanks!


On 7 Feb 2014, at 17:55, Nick Williams wrote:

Ohhh okay. I misunderstood. H. Well I suppose in that case we 
really must rename it, although I'm not super happy about it. But I'm 
convinced it's necessary.


I guess we rename the couch package to couchdb.

Nick

On Feb 7, 2014, at 10:23 AM, Christian Grobmeier wrote:


folks thats what i meant.

Couchbase is a different database than CouchDB. They share the same 
roots,

but meanwhile have some differences.

My guess is one needs a second appender.

The one we have seems to work with couchdb, so the package should be 
named couchdb.

If we want to support couchbase, we need a new implementation

Its more precise. Nobody would just say log4 because its clear that 
we mean java.


If I could convince you now, I would like to rename mongo to mongodb 
too.


As Scott mentioned I would like to convince you (Nick) first, before 
I do any change.


Hope this happened now :)






On 7 Feb 2014, at 17:16, Scott Deboy wrote:



I would appreciate if there wasn't even a threat of veto.

I would like to see folks ask questions and talk about concerns, and 
then

only mention a veto when there is no other recourse.
On Feb 7, 2014 8:14 AM, Nick Williams 
nicho...@nicholaswilliams.net

wrote:

Yep. I would've accompanied any veto with technical justification. 
Since I
can't come up with a technical justification for renaming it to 
couchbase,

I won't veto it. :-)

N

On Feb 7, 2014, at 10:09 AM, Scott Deboy wrote:

I do want to remind everyone that vetoes are only valid if they are 
backed

by a technical justification.

Scott
On Feb 7, 2014 8:07 AM, Nick Williams 
nicho...@nicholaswilliams.net

wrote:

I'm not convinced it really makes a difference, but it's better 
than
couchdb, so if the majority wants couchbase it I won't veto it. Be 
sure to

change the test package name, too.

Nick

On Feb 7, 2014, at 10:03 AM, Scott Deboy wrote:

+1 to couchbase
On Feb 7, 2014 7:54 AM, Christian Grobmeier 
grobme...@gmail.com

wrote:


On 7 Feb 2014, at 16:19, Nick Williams wrote:

It doesn't so much matter because the XML element names are case
insensitive, but if we change the plugin name for CouchDB we 
should
probably also change it for MongoDB. There's a reason I did 
that, I just

can't remember what it was...

I don't see any compelling reason to rename the package. The 
package
name for MongoDB is mongo. I don't like combining multiple 
words into a
single package name segment, because we can't camel case them 
(bad practice
to have cap letters in package names). Show me another NoSQL 
database with

the word couch in it and I'll reconsider. :-)



couchbase maybe?




N

On Feb 7, 2014, at 9:12 AM, Christian Grobmeier wrote:

also the packagename is just couch, but it should better be

couchdb.
The name couch is misleading imho

On 7 Feb 2014, at 16:11, Christian Grobmeier wrote:

Hi


one minor thing in ClouchDBProvider:

* The Apache CouchDB implementation of {@link NoSQLProvider}.
*/
@Plugin(name = CouchDb, category = Core, printObject = 
true)

public final class CouchDBProvider

The name of this plugin is CouchDb while the correct name of 
the

product
is CouchDB: couchdb.apache.org
Also our class and the comments do use the correct name. Just 
the

plugin
name is lower case.

Any objections if I would change the plugin name to CouchDB 
instead

of CouchDb?

Cheers




---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: 
log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org





-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org





---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org










---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail

Re: Logo contest: nominate your favorite logo

2014-02-04 Thread Christian Grobmeier


Hey folks,

with the wiki i just wanted to check which logos should enter the actual 
vote.
Not sure how we would do that, but we have soem tool at the ASF which we 
might
be able to utilize. I am just not sure if non-committers can vote with 
that tool


Cheers

On 4 Feb 2014, at 3:51, Matt Sicker wrote:


Too many good choices for logos!


On 3 February 2014 20:06, Gary Gregory garydgreg...@gmail.com wrote:


On Mon, Feb 3, 2014 at 9:02 PM, Nick Williams 
nicho...@nicholaswilliams.net wrote:

I thought about that, but there's no way to prevent people from 
voting
multiple times. The mailing list isn't fool-proof but it's a lot 
harder to

vote multiple times on it.



With the Wiki, I had to be careful not to mess up everyone else's 
'votes'


Gary



N


On Feb 3, 2014, at 6:40 PM, Paul Benedict wrote:

Why not setup a Survey Monkey?


On Mon, Feb 3, 2014 at 6:36 PM, Nick Williams 
nicho...@nicholaswilliams.net wrote:


Wow. This is going to be hard...

I have submitted my nominations. What's the next step? I read the 
JIRA,
but I saw nothing talking about this nomination stage on the 
Wiki. IMO,
doing the *actual* voting on the mailing list is preferable. Voting 
on the

wiki will be hard and discourage participation.

Nick

On Feb 3, 2014, at 4:58 PM, Remko Popma wrote:

Christian, it worked!
What was Immutable Page in gray before is now an Edit (text) 
link.

Thanks!
-Remko


On Tue, Feb 4, 2014 at 6:40 AM, Christian Grobmeier 
grobme...@gmail.com

wrote:



On 3 Feb 2014, at 22:28, Gary Gregory wrote:

On Mon, Feb 3, 2014 at 1:11 PM, Christian Grobmeier 

grobme...@gmail.comwrote:

On 3 Feb 2014, at 14:40, Gary Gregory wrote:


Wow, our wiki is lame.



Does each wiki need new user account, or is my account an 
all-apache

wiki
account that needs to be added to each wiki I want to play 
with?


Please add GaryGregory



I added you, let me know if it doesnt work



It does not work.



You have an account on this wiki?

I am not sure about the specifics here... just want to collect
some information before I head on to Infra. I added you to 
contributors

list
and if the account is on this wiki it is expected to work.
SO if you have an account for this wiki let me know. I don't 
expect

other moinmoin
wiki accounts work here (in example, Commons).

And yes, I don't like these wikis either! I just feel Confluence 
is not

much better.




Gary




Gary



On Sun, Feb 2, 2014 at 5:21 AM, Christian Grobmeier 
grobme...@gmail.com


wrote:



Hi all,



please show your support for your favorite logo on this wiki 
page:

http://wiki.apache.org/logging/Log4jLogoNominations

I added a few nominations already, just stick with the format.

Everybody reading this message is invited to nominate their 
favorite

logo.

Cheers,
Christian


-
To unsubscribe, e-mail: 
log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org






--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second 
Editionhttp://www.manning.

com/bauer3/
JUnit in Action, Second Edition 
http://www.manning.com/tahchiev/

Spring Batch in Action http://www.manning.com/templier/

Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory




---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org






--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second 
Editionhttp://www.manning.

com/bauer3/
JUnit in Action, Second Edition 
http://www.manning.com/tahchiev/

Spring Batch in Action http://www.manning.com/templier/
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory




---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org








--
Cheers,
Paul






--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second 
Editionhttp://www.manning.com/bauer3/

JUnit in Action, Second Edition http://www.manning.com/tahchiev/
Spring Batch in Action http://www.manning.com/templier/

Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory





--
Matt Sicker boa...@gmail.com



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr

Re: Logo contest: nominate your favorite logo


Hello,

yes, there is a reason! Please give me your wiki name.

You need to be added to the contributors group.

I will add a note to the wiki page as well

Cheers
Christian

On 3 Feb 2014, at 9:25, Remko Popma wrote:


Ralph, can you edit?
I am logged in, but don't see an Edit link...

Available actions are Info, Subscribe, Remove Link, Attachments, More
Actions.
On the left of those it says Immutable Page in gray.

Remko

On Monday, February 3, 2014, Ralph Goers rgo...@apache.org wrote:


You have to log in to the wiki

Sent from my iPad

On Feb 2, 2014, at 8:49 PM, Matt Sicker 
boa...@gmail.comjavascript:_e(%7B%7D,'cvml','boa...@gmail.com');

wrote:

Same, can't edit the page.


On 2 February 2014 19:18, Remko Popma 
remko.po...@gmail.comjavascript:_e(%7B%7D,'cvml','remko.po...@gmail.com');

wrote:



Christian,

Maybe I'm missing something, but I don't see a link to edit this 
page...

In the Actions bar (left of Info, Attachments, More Actions) I see
Immutable Page in gray (not a link)...

Can you check?

Remko


On Sunday, February 2, 2014, Christian Grobmeier 
grobme...@gmail.comjavascript:_e(%7B%7D,'cvml','grobme...@gmail.com');

wrote:


Hi all,

please show your support for your favorite logo on this wiki page:
http://wiki.apache.org/logging/Log4jLogoNominations

I added a few nominations already, just stick with the format.

Everybody reading this message is invited to nominate their 
favorite

logo.

Cheers,
Christian

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org





--
Matt Sicker 
boa...@gmail.comjavascript:_e(%7B%7D,'cvml','boa...@gmail.com');







---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: What will the GA version number be?


Also 2.0 or 2.0.0 for me

On 3 Feb 2014, at 7:41, Ralph Goers wrote:


I had thought it would be 2.0.

Sent from my iPad

On Feb 2, 2014, at 8:59 PM, Nick Williams 
nicho...@nicholaswilliams.net wrote:


I'm finalizing the logging chapter of my book to send to the printers 
Wednesday (I'm so glad I got to correct it to say Level was 
extendable!), and I need to know what the Maven artifact GA version 
number will be. I print the new Maven artifacts used in each chapter 
on the first page of the chapter as a guide to the user. Log4j is the 
only library I'm using that isn't yet GA. I want to be sure the 
version numbers I'm printing are correct.


Here are the options that I can think of for the GA release:

2.0
2.0-GA
2.0.GA
2.0.Final
2.0.RELEASE
2.0.0
2.0.0-GA
2.0.0.GA
2.0.0.Final
2.0.0.RELEASE

So, which is it going to be? I assume that eventually we're going to 
have a 2.0.1, 2.0.2, etc., so it would seem to me that, whatever GA 
is, it should start with 2.0.0. Doesn't seem to make a lot of sense 
to go from 2.0 to 2.0.1. However, all of our beta releases have been 
2.0-Betan.


Thoughts?

Nick
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org



-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Logo contest: nominate your favorite logo

I was out for a while, but the change is now done.
You should see the edit link, let me know if its not the case

On 3 Feb 2014, at 15:17, Remko Popma wrote:

 Christian,

 Did you make a change (add rpopma)? If so, it is not working: I still
 cannot see an Edit link...

 Best regards,
 -Remko



 On Mon, Feb 3, 2014 at 7:14 PM, Remko Popma remko.po...@gmail.com wrote:

 Aha!
 rpopma

 Sent from my iPhone

 On 2014/02/03, at 19:10, Christian Grobmeier grobme...@gmail.com
 wrote:

 Hello,

 yes, there is a reason! Please give me your wiki name.

 You need to be added to the contributors group.

 I will add a note to the wiki page as well

 Cheers
 Christian

 On 3 Feb 2014, at 9:25, Remko Popma wrote:

 Ralph, can you edit?
 I am logged in, but don't see an Edit link...

 Available actions are Info, Subscribe, Remove Link, Attachments, More
 Actions.
 On the left of those it says Immutable Page in gray.

 Remko

 On Monday, February 3, 2014, Ralph Goers rgo...@apache.org wrote:

 You have to log in to the wiki

 Sent from my iPad

 On Feb 2, 2014, at 8:49 PM, Matt Sicker boa...@gmail.com
 javascript:_e(%7B%7D,'cvml','boa...@gmail.com');
 wrote:

 Same, can't edit the page.


 On 2 February 2014 19:18, Remko Popma remko.po...@gmail.com
 javascript:_e(%7B%7D,'cvml','remko.po...@gmail.com');
 wrote:

 Christian,

 Maybe I'm missing something, but I don't see a link to edit this
 page...
 In the Actions bar (left of Info, Attachments, More Actions) I see
 Immutable Page in gray (not a link)...

 Can you check?

 Remko


 On Sunday, February 2, 2014, Christian Grobmeier grobme...@gmail.com
 javascript:_e(%7B%7D,'cvml','grobme...@gmail.com');
 wrote:

 Hi all,

 please show your support for your favorite logo on this wiki page:
 http://wiki.apache.org/logging/Log4jLogoNominations

 I added a few nominations already, just stick with the format.

 Everybody reading this message is invited to nominate their favorite
 logo.

 Cheers,
 Christian

 -
 To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
 For additional commands, e-mail: log4j-dev-h...@logging.apache.org


 --
 Matt Sicker boa...@gmail.comjavascript:_e(%7B%7D,'cvml','
 boa...@gmail.com');


 ---
 http://www.grobmeier.de
 The Zen Programmer: http://bit.ly/12lC6DL
 @grobmeier
 GPG: 0xA5CC90DB

 -
 To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
 For additional commands, e-mail: log4j-dev-h...@logging.apache.org




---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Logo contest: nominate your favorite logo


On 3 Feb 2014, at 14:40, Gary Gregory wrote:


Wow, our wiki is lame.

Does each wiki need new user account, or is my account an all-apache 
wiki

account that needs to be added to each wiki I want to play with?

Please add GaryGregory


I added you, let me know if it doesnt work


Gary


On Sun, Feb 2, 2014 at 5:21 AM, Christian Grobmeier 
grobme...@gmail.comwrote:



Hi all,

please show your support for your favorite logo on this wiki page:
http://wiki.apache.org/logging/Log4jLogoNominations

I added a few nominations already, just stick with the format.

Everybody reading this message is invited to nominate their favorite 
logo.


Cheers,
Christian

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org





--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second 
Editionhttp://www.manning.com/bauer3/

JUnit in Action, Second Edition http://www.manning.com/tahchiev/
Spring Batch in Action http://www.manning.com/templier/
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Logo contest: nominate your favorite logo


On 3 Feb 2014, at 22:28, Gary Gregory wrote:

On Mon, Feb 3, 2014 at 1:11 PM, Christian Grobmeier 
grobme...@gmail.comwrote:



On 3 Feb 2014, at 14:40, Gary Gregory wrote:

Wow, our wiki is lame.


Does each wiki need new user account, or is my account an all-apache 
wiki

account that needs to be added to each wiki I want to play with?

Please add GaryGregory



I added you, let me know if it doesnt work



It does not work.


You have an account on this wiki?

I am not sure about the specifics here... just want to collect
some information before I head on to Infra. I added you to contributors 
list

and if the account is on this wiki it is expected to work.
SO if you have an account for this wiki let me know. I don't expect 
other moinmoin

wiki accounts work here (in example, Commons).

And yes, I don't like these wikis either! I just feel Confluence is not 
much better.




Gary





Gary


On Sun, Feb 2, 2014 at 5:21 AM, Christian Grobmeier 
grobme...@gmail.com

wrote:


Hi all,


please show your support for your favorite logo on this wiki page:
http://wiki.apache.org/logging/Log4jLogoNominations

I added a few nominations already, just stick with the format.

Everybody reading this message is invited to nominate their 
favorite

logo.

Cheers,
Christian

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org





--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Editionhttp://www.manning.
com/bauer3/
JUnit in Action, Second Edition http://www.manning.com/tahchiev/
Spring Batch in Action http://www.manning.com/templier/

Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory




---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org





--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second 
Editionhttp://www.manning.com/bauer3/

JUnit in Action, Second Edition http://www.manning.com/tahchiev/
Spring Batch in Action http://www.manning.com/templier/
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: What will the GA version number be?

On 3 Feb 2014, at 22:14, Matt Sicker wrote:

 I like 2.0.0 because semver.org etc., although as long as it's not a dumb
 version number like GA or RELEASE or Final, I'm happy with it.

Sticking with semver might be a good idea. Its a language many understand
and we should try to stick with that lanugage as well.



 On 3 February 2014 07:07, Gary Gregory garydgreg...@gmail.com wrote:

 Keep it simple: 2.0.

 Gary


  Original message 
 From: Christian Grobmeier
 Date:02/03/2014 05:12 (GMT-05:00)
 To: Log4J Developers List
 Subject: Re: What will the GA version number be?

 Also 2.0 or 2.0.0 for me

 On 3 Feb 2014, at 7:41, Ralph Goers wrote:

 I had thought it would be 2.0.

 Sent from my iPad

 On Feb 2, 2014, at 8:59 PM, Nick Williams
 nicho...@nicholaswilliams.net wrote:

 I'm finalizing the logging chapter of my book to send to the printers
 Wednesday (I'm so glad I got to correct it to say Level was
 extendable!), and I need to know what the Maven artifact GA version
 number will be. I print the new Maven artifacts used in each chapter
 on the first page of the chapter as a guide to the user. Log4j is the
 only library I'm using that isn't yet GA. I want to be sure the
 version numbers I'm printing are correct.

 Here are the options that I can think of for the GA release:

 2.0
 2.0-GA
 2.0.GA
 2.0.Final
 2.0.RELEASE
 2.0.0
 2.0.0-GA
 2.0.0.GA
 2.0.0.Final
 2.0.0.RELEASE

 So, which is it going to be? I assume that eventually we're going to
 have a 2.0.1, 2.0.2, etc., so it would seem to me that, whatever GA
 is, it should start with 2.0.0. Doesn't seem to make a lot of sense
 to go from 2.0 to 2.0.1. However, all of our beta releases have been
 2.0-Betan.

 Thoughts?

 Nick
 -
 To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
 For additional commands, e-mail: log4j-dev-h...@logging.apache.org


 -
 To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
 For additional commands, e-mail: log4j-dev-h...@logging.apache.org


 ---
 http://www.grobmeier.de
 The Zen Programmer: http://bit.ly/12lC6DL
 @grobmeier
 GPG: 0xA5CC90DB

 -
 To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
 For additional commands, e-mail: log4j-dev-h...@logging.apache.org




 --
 Matt Sicker boa...@gmail.com


---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Updated] (LOG4J2-316) Logo Contest Submissions

2014-02-02 Thread Christian Grobmeier (JIRA)

[
https://issues.apache.org/jira/browse/LOG4J2-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christian Grobmeier updated LOG4J2-316:
---

Description:
h4. Log4J logo contest

THANK YOU FOR PARTICIPATING - we are going to choose a new logo in the coming
days.

Log4j 2.0 is looking for a new logo!

After 12 years, the Log4j project is getting ready for a brand new major
release: version 2.0. This new major version is a reboot of this project in
many ways: it is not only time to change the version number to 2.0 but also
time to refresh the Log4j logo.

Log4j 2 is very different from Log4j 1. Log4j 2 is more reliable and faster
than its predecessor and comparable frameworks.

The team has grown after years of stagnation and there is now a lot of activity
on our lists. We are now approaching the 2.0 release after eight beta releases.

With our new logo, we want to show the Java community that Log4j is back.

We would like to open participation to the community to create this new logo.

h4. HOW TO PARTICIPATE

Attach your entries to the Jira:
https://issues.apache.org/jira/browse/LOG4J2-316

You can submit as many entries as you like.

You must license your Logo under the Apache License 2.0.

-The contest will last one month from the date of the announcement.-

*UPDATE: The contest ends on 31.01.2014.*

If your Logo is accepted, you must sign an ICLA:
http://www.apache.org/licenses/icla.txt

While we will accept PNG image formats for the contest, we prefer vector based
formats (SVG).

You can convert pixel-based formats produced with Gimp or Photoshop to SVG with
free tools like Inkscape (http://inkscape.org)

Please note that a logo should not contain too many details.

h4. HOW THE WINNING LOGO IS CHOSEN

We invite everyone to vote on the mailing lists. The votes of Apache Logging
Committers are binding.

If the community submits more than 10 Logos, voting will proceed in two rounds.

In the first round, the 10 logos with the most +1 votes graduate to round two.

In the second round, the logo with the most +1 will win the contest.

The majority of the Apache Logging PMC can veto a logo.

We will accept the logo when all votes are successful and the ICLA of the logo
contributor is on file.

Please ask questions on the dev mailing list.

The Log4j team

was:
h4. Log4J logo contest

Log4j 2.0 is looking for a new logo!

Log4j 2 is very different from Log4j 1. Log4j 2 is more reliable and faster
than its predecessor and comparable frameworks.

The team has grown after years of stagnation and there is now a lot of activity
on our lists. We are now approaching the 2.0 release after eight beta releases.

With our new logo, we want to show the Java community that Log4j is back.

We would like to open participation to the community to create this new logo.

h4. HOW TO PARTICIPATE

Attach your entries to the Jira:
https://issues.apache.org/jira/browse/LOG4J2-316

You can submit as many entries as you like.

You must license your Logo under the Apache License 2.0.

-The contest will last one month from the date of the announcement.-

*UPDATE: The contest ends on 31.01.2014.*

If your Logo is accepted, you must sign an ICLA:
http://www.apache.org/licenses/icla.txt

While we will accept PNG image formats for the contest, we prefer vector based
formats (SVG).

You can convert pixel-based formats produced with Gimp or Photoshop to SVG with
free tools like Inkscape (http://inkscape.org)

Please note that a logo should not contain too many details.

h4. HOW THE WINNING LOGO IS CHOSEN

We invite everyone to vote on the mailing lists. The votes of Apache Logging
Committers are binding.

If the community submits more than 10 Logos, voting will proceed in two rounds.

In the first round, the 10 logos with the most +1 votes graduate to round two.

In the second round, the logo with the most +1 will win the contest.

The majority of the Apache Logging PMC can veto a logo.

We will accept the logo when all votes are successful and the ICLA of the logo
contributor is on file.

Please ask questions on the dev mailing list.

The Log4j team

Logo Contest Submissions

[jira] [Commented] (LOG4J2-316) Logo Contest Submissions

2014-02-02 Thread Christian Grobmeier (JIRA)

[
https://issues.apache.org/jira/browse/LOG4J2-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1386#comment-1386
]

Christian Grobmeier commented on LOG4J2-316:

THANK YOU FOR PARTICIPATING - we are going to choose a new logo in the coming
days. Please stay patient :)

Logo Contest Submissions

Key: LOG4J2-316
URL: https://issues.apache.org/jira/browse/LOG4J2-316
Project: Log4j 2
Issue Type: Task
Reporter: Christian Grobmeier
Assignee: Christian Grobmeier
Attachments: CarloMatti-Concept.jpg, Log4J2-Attitude.png,
Log4J2-Selected.png, Log4j-circular-more.png, Log4j-circular-more.svg,
Log4j-circular.png, Log4j-circular.svg, Log4j-combined.png,
Log4j-galactica.png, Log4j-rectangular.png, Log4j-rectangular.svg,
Log4j-textured.png, Log4j_logo.png, Micah_log4j_icon.png,
a_new_log4j2-logo.png, apache-log4j-2.png, apache_log4j2_logo.png, l4j.png,
l4j.svg, log4-SE.png, log4.png, log4J2-logo-B.png, log4J2-logo.png,
log4J2_Lila.png, log4J2_Orange_Grün.png, log4J2_Schwartz.png, log4J_bunt.png,
log4j-2-rnm.png, log4j-2.png, log4j-apache.png, log4j-asap.png,
log4j-designmantic.com-1.PNG, log4j-designmantic.com-2.PNG,
log4j-designmantic.com-3.PNG, log4j-designmantic.com-4.PNG,
log4j-designmantic.com-5.PNG, log4j-designmantic.com-6.PNG,
log4j-designmantic.com-7.PNG, log4j-designmantic.com-8.PNG, log4j-stepuk.png,
log4j.png, log4j.png, log4j.svg, log4j2(Pasha_G).png, log4j2(logo).png,
log4j2(logo)_1.png, log4j2-b.svg, log4j2_e-id.nl.jpg, log4j2_e-id.nl.svg,
log4j_2.svg, log4j_idea.jpg, log4j_logo.png, log4j_murdy_1.png,
log4j_murdy_10.png, log4j_murdy_11.png, log4j_murdy_11_types.png,
log4j_murdy_2.png, log4j_murdy_3.png, log4j_murdy_4.png, log4j_murdy_6.png,
log4j_murdy_7.png, log4j_murdy_8.png, log4j_murdy_9.png,
logo-log4j-circle.png, logo-log4j-eruption.png,
logo-m-nostrokes-condensed.png, logo-m-nostrokes-condensed.svg,
logo-m-nostrokes.png, logo-m-nostrokes.svg, logo-m.png, logo-m.svg,
logoprop_coffeesteam_131022NS.png, logoprop_monogram_131022NS.png,
logoprop_stacked-lj_131022NS.png, tmp_140123_0205221834269922.png

h4. Log4J logo contest
THANK YOU FOR PARTICIPATING - we are going to choose a new logo in the coming
days.
Log4j 2.0 is looking for a new logo!
After 12 years, the Log4j project is getting ready for a brand new major
release: version 2.0. This new major version is a reboot of this project in
many ways: it is not only time to change the version number to 2.0 but also
time to refresh the Log4j logo.
Log4j 2 is very different from Log4j 1. Log4j 2 is more reliable and faster
than its predecessor and comparable frameworks.
The team has grown after years of stagnation and there is now a lot of
activity on our lists. We are now approaching the 2.0 release after eight
beta releases.
With our new logo, we want to show the Java community that Log4j is back.
We would like to open participation to the community to create this new logo.
h4. HOW TO PARTICIPATE
Attach your entries to the Jira:
https://issues.apache.org/jira/browse/LOG4J2-316
You can submit as many entries as you like.
You must license your Logo under the Apache License 2.0.
-The contest will last one month from the date of the announcement.-
*UPDATE: The contest ends on 31.01.2014.*
If your Logo is accepted, you must sign an ICLA:
http://www.apache.org/licenses/icla.txt
While we will accept PNG image formats for the contest, we prefer vector
based formats (SVG).
You can convert pixel-based formats produced with Gimp or Photoshop to SVG
with free tools like Inkscape (http://inkscape.org)
Please note that a logo should not contain too many details.
h4. HOW THE WINNING LOGO IS CHOSEN
We invite everyone to vote on the mailing lists. The votes of Apache Logging
Committers are binding.
If the community submits more than 10 Logos, voting will proceed in two
rounds.
In the first round, the 10 logos with the most +1 votes graduate to round two.
In the second round, the logo with the most +1 will win the contest.
The majority of the Apache Logging PMC can veto a logo.
We will accept the logo when all votes are successful and the ICLA of the
logo contributor is on file.
Please ask questions on the dev mailing list.
The Log4j team

--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Logo contest: nominate your favorite logo

2014-02-02 Thread Christian Grobmeier

Hi all,

please show your support for your favorite logo on this wiki page:
http://wiki.apache.org/logging/Log4jLogoNominations

I added a few nominations already, just stick with the format.

Everybody reading this message is invited to nominate their favorite logo.

Cheers,
Christian

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: ApacheCon CFP

2014-02-01 Thread Christian Grobmeier

! If we can get two PMC members to come, we 
can even have a summit, which would be great exposure! We need to 
coordinate so that we're covering different topics and not 
stepping on each other.


I NEED A ROOMMATE AND YOU DO, TOO! Hotel is the biggest expense 
for this--more than flights and committer registration combined. 
I'm looking for someone who wants to go and is willing to share a 
hotel room and split the cost. If we can get 4 Logging guys 
there, we can use just 2 hotel rooms and save a bunch of money. I 
plan on flying in Sunday night and checking out of the hotel 
Friday morning--that's five nights. If someone can only share the 
hotel for 3 nights, we can split the price accordingly.


Inline below I have included the answers I got to some questions 
I asked Rich.


I hope some of you will come to ApacheCon with me! It'll be a 
great opportunity to publicize Log4j 2.0 GA!


Nick


On Jan 27, 2014, at 6:21 AM, Nick Williams wrote:

- What exactly is a project summit?


Rich: Some projects are taking the opportunity to have a summit 
of one kind or another, to do sprints on features, or to discuss 
the direction of the project, or to do bug triage, or whatever. A 
project summit is whatever you want to make it, if two or more 
members of the PMC are together in a room to make it happen.


- What exactly is a tutorial and how is it different from a talk 
on the normal days?


Rich: A talk is 50 minutes. A tutorial is 3 hours. That's the 
main difference. A tutorial is usually more indepth, with 
hands-on elements - more of a training class than an overview.


I noticed the fee is normally $799 (until Friday, then $1099), 
but it's $275 for committers. That means that anyone who's a 
committer on any Apache project whatsoever /only/ pays $275 to 
attend the entire conference, right?


Rich: That's correct.



The registration page says there is an additional fee for 
tutorials on April 10th: $399 for ½ day tutorials ($299 for 
students) and $749 for full day tutorials (students and 
attendees). What it doesn't say is:
1) Is there an additional fee for tutorials on April 10th for 
/committers/?


Rich: Yes, tutorials have a fee for everyone.

2) Is there an additional fee for tutorials on April 11th for 
anyone (it only mentions April 10th, but the schedule shows 
tutorials on April 11th as well)?


Rich: We'll get that fixed.

3) Is there an additional fee for project summits on April 10th 
or 11th?


Rich: Project summits are usually open to anyone interested in 
the project, and no extra fee is charged.


It says they will have 5-9 tracks going on this year. I assume 
that means 5-9 conference rooms (based on the # of CFPs 
submitted), which means 5-9 simultaneous talks can occur.


Rich: That is correct.

It sounds like there is potentially time to have multiple talks 
on Apache Logging. Though I am new-ish, I'd love to present on 
behalf of Apache Logging. Do we want to have multiple talks?


Nick


On Jan 26, 2014, at 9:29 PM, Ralph Goers wrote:

I would like to attend but I’m not sure I can.

Ralph

On Jan 25, 2014, at 11:11 AM, Christian Grobmeier 
grobme...@gmail.com wrote:


Hi folks,

I would like to remind you ApacheCon is happening in April 
2014.

If you would like to submit your talk, now is the chance.

I think it would be great to have somebody presenting our 
Logging frameworks.

I will not be there unfortunately.

Regards,
Christian

---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: 
log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org



-
To unsubscribe, e-mail: 
log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org



-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org




-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org




-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org




--
Matt Sicker boa...@gmail.com





-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev

Re: ApacheCon CFP

2014-01-31 Thread Christian Grobmeier

--that's five nights. If someone can only share the 
hotel for 3 nights, we can split the price accordingly.


Inline below I have included the answers I got to some questions 
I asked Rich.


I hope some of you will come to ApacheCon with me! It'll be a 
great opportunity to publicize Log4j 2.0 GA!


Nick


On Jan 27, 2014, at 6:21 AM, Nick Williams wrote:

- What exactly is a project summit?


Rich: Some projects are taking the opportunity to have a summit 
of one kind or another, to do sprints on features, or to discuss 
the direction of the project, or to do bug triage, or whatever. A 
project summit is whatever you want to make it, if two or more 
members of the PMC are together in a room to make it happen.


- What exactly is a tutorial and how is it different from a talk 
on the normal days?


Rich: A talk is 50 minutes. A tutorial is 3 hours. That's the 
main difference. A tutorial is usually more indepth, with 
hands-on elements - more of a training class than an overview.


I noticed the fee is normally $799 (until Friday, then $1099), 
but it's $275 for committers. That means that anyone who's a 
committer on any Apache project whatsoever /only/ pays $275 to 
attend the entire conference, right?


Rich: That's correct.



The registration page says there is an additional fee for 
tutorials on April 10th: $399 for ½ day tutorials ($299 for 
students) and $749 for full day tutorials (students and 
attendees). What it doesn't say is:
1) Is there an additional fee for tutorials on April 10th for 
/committers/?


Rich: Yes, tutorials have a fee for everyone.

2) Is there an additional fee for tutorials on April 11th for 
anyone (it only mentions April 10th, but the schedule shows 
tutorials on April 11th as well)?


Rich: We'll get that fixed.

3) Is there an additional fee for project summits on April 10th 
or 11th?


Rich: Project summits are usually open to anyone interested in 
the project, and no extra fee is charged.


It says they will have 5-9 tracks going on this year. I assume 
that means 5-9 conference rooms (based on the # of CFPs 
submitted), which means 5-9 simultaneous talks can occur.


Rich: That is correct.

It sounds like there is potentially time to have multiple talks 
on Apache Logging. Though I am new-ish, I'd love to present on 
behalf of Apache Logging. Do we want to have multiple talks?


Nick


On Jan 26, 2014, at 9:29 PM, Ralph Goers wrote:

I would like to attend but I’m not sure I can.

Ralph

On Jan 25, 2014, at 11:11 AM, Christian Grobmeier 
grobme...@gmail.com wrote:


Hi folks,

I would like to remind you ApacheCon is happening in April 
2014.

If you would like to submit your talk, now is the chance.

I think it would be great to have somebody presenting our 
Logging frameworks.

I will not be there unfortunately.

Regards,
Christian

---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: 
log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org



-
To unsubscribe, e-mail: 
log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org



-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: 
log4j-dev-h...@logging.apache.org




-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org




-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org




--
Matt Sicker boa...@gmail.com





---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: ApacheCon CFP

2014-01-30 Thread Christian Grobmeier


Please don't wait any longer Matt.

http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
Submission must arrive before (!) 1.02. and they will not extend this 
deadline.


However you talk sounds good. Just from experience, people are sometimes 
setup
when they hear they should move their facade from slf4j to log4j2 again. 
Be prepared

to have good arguments

Any great if you could submit a proposal!

On 30 Jan 2014, at 15:42, Matt Sicker wrote:

I know I'm not a committer (yet), but I would be interested in doing a 
talk on logging. I'll see if I can get employer support as well. Is 
anyone else interested in putting together a CFP or two? I'd like to 
cover the neat new features in log4j, why we're more awesome than 
SLF4J, how to use logging effectively (e.g., using aspects to inject 
trace logging, using informative log messages, effective usage of the 
API, when to use different levels, using markers, complex logging 
configurations, etc), how to help make log4j compatible with other 
logging APIs not already implemented, creating additional components 
(I.e., appenders, filters, layouts, etc.), and many other ideas. 
Obviously that's too much to cover in one talk, but it's a good place 
to start examining what topics to cover and at what levels of 
expertise.


Matt Sicker

On Jan 28, 2014, at 11:29, Nick Williams 
nicho...@nicholaswilliams.net wrote:


Guys, let's show up for Apache Logging! They're hurting for CFP's 
right now. Rich Bowen at ApacheCon assures me that if money is an 
issue getting committers to come and lead talks, the Travel 
Assistance Committee will do everything it can to help you get there. 
Email them at t...@apache.org.


I'm definitely going and I'll submit a CFP as well. I'm open to 
suggestions. Let's try to get 3-5 good Apache Logging talks in from 
different people! If we can get two PMC members to come, we can even 
have a summit, which would be great exposure! We need to coordinate 
so that we're covering different topics and not stepping on each 
other.


I NEED A ROOMMATE AND YOU DO, TOO! Hotel is the biggest expense for 
this--more than flights and committer registration combined. I'm 
looking for someone who wants to go and is willing to share a hotel 
room and split the cost. If we can get 4 Logging guys there, we can 
use just 2 hotel rooms and save a bunch of money. I plan on flying in 
Sunday night and checking out of the hotel Friday morning--that's 
five nights. If someone can only share the hotel for 3 nights, we can 
split the price accordingly.


Inline below I have included the answers I got to some questions I 
asked Rich.


I hope some of you will come to ApacheCon with me! It'll be a great 
opportunity to publicize Log4j 2.0 GA!


Nick


On Jan 27, 2014, at 6:21 AM, Nick Williams wrote:

- What exactly is a project summit?


Rich: Some projects are taking the opportunity to have a summit of 
one kind or another, to do sprints on features, or to discuss the 
direction of the project, or to do bug triage, or whatever. A project 
summit is whatever you want to make it, if two or more members of the 
PMC are together in a room to make it happen.


- What exactly is a tutorial and how is it different from a talk on 
the normal days?


Rich: A talk is 50 minutes. A tutorial is 3 hours. That's the main 
difference. A tutorial is usually more indepth, with hands-on 
elements - more of a training class than an overview.


I noticed the fee is normally $799 (until Friday, then $1099), but 
it's $275 for committers. That means that anyone who's a committer 
on any Apache project whatsoever /only/ pays $275 to attend the 
entire conference, right?


Rich: That's correct.



The registration page says there is an additional fee for tutorials 
on April 10th: $399 for ½ day tutorials ($299 for students) and 
$749 for full day tutorials (students and attendees). What it 
doesn't say is:
1) Is there an additional fee for tutorials on April 10th for 
/committers/?


Rich: Yes, tutorials have a fee for everyone.

2) Is there an additional fee for tutorials on April 11th for anyone 
(it only mentions April 10th, but the schedule shows tutorials on 
April 11th as well)?


Rich: We'll get that fixed.

3) Is there an additional fee for project summits on April 10th or 
11th?


Rich: Project summits are usually open to anyone interested in the 
project, and no extra fee is charged.


It says they will have 5-9 tracks going on this year. I assume that 
means 5-9 conference rooms (based on the # of CFPs submitted), which 
means 5-9 simultaneous talks can occur.


Rich: That is correct.

It sounds like there is potentially time to have multiple talks on 
Apache Logging. Though I am new-ish, I'd love to present on behalf 
of Apache Logging. Do we want to have multiple talks?


Nick


On Jan 26, 2014, at 9:29 PM, Ralph Goers wrote:

I would like to attend but I’m not sure I can.

Ralph

On Jan 25, 2014, at 11:11 AM, Christian Grobmeier 
grobme

Re: ApacheCon CFP

2014-01-29 Thread Christian Grobmeier


On 29 Jan 2014, at 0:22, Remko Popma wrote:


... I'm still learning proper ML etiquette...


Just for the record: i didn't mean you or anyone hear at Logging ;-)



Very nice slides, btw.

On Wednesday, January 29, 2014, Christian Grobmeier 
grobme...@gmail.com

wrote:

I would love to go, but i have to deal with a view personal issues 
(which

are not meant to be discussed in public)
That makes it impossible for me to travel.

However I was presenting Apache Logging at ACEU 2012 and it was an 
amazing

experience.
I can only recommend it to everybody new at this project or not.
The things you learn and the people you'll meet definitely make a
difference.
In example I met a few ASF fellow of whom I thought I didn't like 
them. I

was so wrong!
mails are useful for us, but in reality people are *so* different to 
mails.


What I also enjoyed were the feedback after the talks(s).

Here are my old slides:
http://www.slideshare.net/christiangrobmeier/world-of-logging

I also think Logging is an important topic and a focus on logging 
would

surely help us
to promote log4j in the US.



On 28 Jan 2014, at 18:59, Remko Popma wrote:

I'm interested but not sure if I can go (we are expecting our second 
child

early May...)
-Remko


On Wed, Jan 29, 2014 at 2:29 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:

Guys, let's show up for Apache Logging! They're hurting for CFP's 
right
now. Rich Bowen at ApacheCon assures me that if money is an issue 
getting
committers to come and lead talks, the Travel Assistance Committee 
will

do
everything it can to help you get there. Email them at 
t...@apache.org.


I'm definitely going and I'll submit a CFP as well. I'm open to
suggestions. Let's try to get 3-5 good Apache Logging talks in from
different people! If we can get two PMC members to come, we can 
even

have a
summit, which would be great exposure! We need to coordinate so 
that

we're
covering different topics and not stepping on each other.

I NEED A ROOMMATE AND YOU DO, TOO! Hotel is the biggest expense for
this--more than flights and committer registration combined. I'm 
looking
for someone who wants to go and is willing to share a hotel room 
and

split
the cost. If we can get 4 Logging guys there, we can use just 2 
hotel

rooms
and save a bunch of money. I plan on flying in Sunday night and 
checking
out of the hotel Friday morning--that's five nights. If someone can 
only

share the hotel for 3 nights, we can split the price accordingly.

Inline below I have included the answers I got to some questions I 
asked

Rich.

I hope some of you will come to ApacheCon with me! It'll be a great
opportunity to publicize Log4j 2.0 GA!

Nick

On Jan 27, 2014, at 6:21 AM, Nick Williams wrote:

- What exactly is a project summit?




Rich: Some projects are taking the opportunity to have a summit 
of one
kind or another, to do sprints on features, or to discuss the 
direction

of
the project, or to do bug triage, or whatever. A project summit is
whatever
you want to make it, if two or more members of the PMC are together 
in a

room to make it happen.

- What exactly is a tutorial and how is it different from a talk on 
the



normal days?

Rich: A talk is 50 minutes. A tutorial is 3 hours. That's the main
difference. A tutorial is usually more indepth, with hands-on 
elements -

more of a training class than an overview.

I noticed the fee is normally $799 (until Friday, then $1099), but 
it's


$275 for committers. That means that anyone who's a committer on 
any

Apache project whatsoever /only/ pays $275 to attend the entire
conference,
right?

Rich: That's correct.


The registration page says there is an additional fee for 
tutorials on


April 10th: $399 for 1/2 day tutorials ($299 for students) and 
$749 for

full
day tutorials (students and attendees). What it doesn't say is:


1) Is there an additional fee for tutorials on April 10th for


/committers/?

Rich: Yes, tutorials have a fee for everyone.

2) Is there an additional fee for tutorials on April 11th for 
anyone (it


only mentions April 10th, but the schedule shows tutorials on April 
11th

as
well)?

Rich: We'll get that fixed.

3) Is there an additional fee for project summits on April 10th or 
11th?




Rich: Project summits are usually open to anyone interested in the
project, and no extra fee is charged.

It says they will have 5-9 tracks going on this year. I assume that


means 5-9 conference rooms (based on the # of CFPs submitted), 
which

means
5-9 simultaneous talks can occur.

Rich: That is correct.

It sounds like there is potentially time to have multiple talks on


Apache Logging. Though I am new-ish, I'd love to present on behalf 
of

Apache Logging. Do we want to have multiple talks?



Nick

On Jan 26, 2014, at 9:29 PM, Ralph Goers wrote:

I would like to attend but I'm not sure I can.


Ralph

On Jan 25, 2014, at 11:11 AM, Christian Grobmeier 
grobme...@gmail.com





wrote:





Hi folks,


I would like to remind you

Re: GA?

2014-01-28 Thread Christian Grobmeier


On 28 Jan 2014, at 1:45, Ralph Goers wrote:

I agree with that, but that doesn’t mean we can’t add new stuff to 
the API.


I would like to highlight that!

Anyway happy with the proposed time plan :-)

Cheers




Ralph

On Jan 27, 2014, at 2:08 PM, Gary Gregory garydgreg...@gmail.com 
wrote:


IMO: We cannot/should not break binary compatibility without a major 
release change (and accompanying package and Maven coordinate 
changes).


Gary


On Mon, Jan 27, 2014 at 4:59 PM, Remko Popma remko.po...@gmail.com 
wrote:

How about an RC now (after showstoppers are fixed),
then the GA release say one month later?

Keep in mind we can still have bugix releases in 2.0.1, etc, and even 
API changes in 2.1 etc...



On Tuesday, January 28, 2014, Matt Sicker boa...@gmail.com wrote:
I agree on putting out an RC release. I think it might help spur some 
3rd party development to integrate with the new version.



On 27 January 2014 12:37, Gary Gregory garydgreg...@gmail.com 
wrote:
So, yes, the new level API needs to go through a non-GA release. 
Aside from that, I am behind in my Log4j2 homework to see how much 
work it will be to convert our Log4j1 code and extensions to v2. But 
that's just an issue on my end that should not hold up everyone else.


I've been out of 100% commission for almost a week so I need to try 
and use the new level system...


Gary


On Mon, Jan 27, 2014 at 11:18 AM, Ralph Goers 
ralph.go...@dslextreme.com wrote:
Due to the API change I can agree with having another beta or an RC 
but the reason I asked about GA is that I am not aware of very many 
showstopper issues that need to be addressed.  I am sensing that you 
have a real reluctance to have Log4j 2 released as GA and I am trying 
to understand what the reason is.


Ralph

On Jan 27, 2014, at 6:15 AM, Gary Gregory garydgreg...@gmail.com 
wrote:


I agree with Nick. Changing levels to be extensible warrants another 
Beta. I'd like to see a stable API before we get into RC mode.


What about:

- Now: Another Beta
- +1 month, If the API is stable: RC1
- RCs until shows stoppers are fixed, pick a rhythm: once a week may 
be too much, once a month too long. Every two weeks seems pretty 
frequent for our bunch for a ramp down.


Thoughts on that?

I am not so much concerned about OSGi now since I look at this as 
more of a packaging issue and how much gets dragged in the container 
with dependencies. For OSGi, are we really considering delivering 
one bundle (jar) per appender?


I am more concerned about all the issues people seem to have in 
servlet environments.



Gary


On Mon, Jan 27, 2014 at 7:22 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:
I wouldn't necessarily vote against a GA, but given that we just 
MAJORLY overhauled Level, I think a brief RC is in order. It would 
be a shame if someone found a problem with Level a week after GA 
that caused us to need to change the API to fix it.

Nick


On Jan 27, 2014, at 12:51 AM, Remko Popma wrote:

I'd like to fix LOG4J-412 and 448, but neither of them are 
showstoppers IMHO.


Remko

On Monday, January 27, 2014, Ralph Goers 
ralph.go...@dslextreme.com wrote:
Since we are having good discussions I would also like to find out 
what are blockers to a GA release.  My list includes:
1. The fix Nick is working on to allow Servlet initialization to be 
disabled from automatically happening in a 3.0 container.
2. Support for programmatic configuration of Loggers. I planned on 
working on that this weekend but worked on the custom levels 
instead.


While I believe better support for OSGi is necessary I don’t 
believe we will be able to do that for GA.


Are there any other Jira issues or features that anybody else feels 
is required?


Ralph
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org






--
Matt Sicker boa...@gmail.com



--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
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



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: ApacheCon CFP

2014-01-28 Thread Christian Grobmeier

I would love to go, but i have to deal with a view personal issues 
(which  are not meant to be discussed in public)

That makes it impossible for me to travel.

However I was presenting Apache Logging at ACEU 2012 and it was an 
amazing experience.

I can only recommend it to everybody new at this project or not.
The things you learn and the people you'll meet definitely make a 
difference.
In example I met a few ASF fellow of whom I thought I didn't like them. 
I was so wrong!
mails are useful for us, but in reality people are *so* different to 
mails.


What I also enjoyed were the feedback after the talks(s).

Here are my old slides:
http://www.slideshare.net/christiangrobmeier/world-of-logging

I also think Logging is an important topic and a focus on logging would 
surely help us

to promote log4j in the US.



On 28 Jan 2014, at 18:59, Remko Popma wrote:

I'm interested but not sure if I can go (we are expecting our second 
child

early May...)
-Remko


On Wed, Jan 29, 2014 at 2:29 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:

Guys, let's show up for Apache Logging! They're hurting for CFP's 
right
now. Rich Bowen at ApacheCon assures me that if money is an issue 
getting
committers to come and lead talks, the Travel Assistance Committee 
will do
everything it can to help you get there. Email them at 
t...@apache.org.


I'm definitely going and I'll submit a CFP as well. I'm open to
suggestions. Let's try to get 3-5 good Apache Logging talks in from
different people! If we can get two PMC members to come, we can even 
have a
summit, which would be great exposure! We need to coordinate so that 
we're

covering different topics and not stepping on each other.

I NEED A ROOMMATE AND YOU DO, TOO! Hotel is the biggest expense for
this--more than flights and committer registration combined. I'm 
looking
for someone who wants to go and is willing to share a hotel room and 
split
the cost. If we can get 4 Logging guys there, we can use just 2 hotel 
rooms
and save a bunch of money. I plan on flying in Sunday night and 
checking
out of the hotel Friday morning--that's five nights. If someone can 
only

share the hotel for 3 nights, we can split the price accordingly.

Inline below I have included the answers I got to some questions I 
asked

Rich.

I hope some of you will come to ApacheCon with me! It'll be a great
opportunity to publicize Log4j 2.0 GA!

Nick

On Jan 27, 2014, at 6:21 AM, Nick Williams wrote:


- What exactly is a project summit?


Rich: Some projects are taking the opportunity to have a summit of 
one
kind or another, to do sprints on features, or to discuss the 
direction of
the project, or to do bug triage, or whatever. A project summit is 
whatever
you want to make it, if two or more members of the PMC are together 
in a

room to make it happen.

- What exactly is a tutorial and how is it different from a talk on 
the

normal days?

Rich: A talk is 50 minutes. A tutorial is 3 hours. That's the main
difference. A tutorial is usually more indepth, with hands-on 
elements -

more of a training class than an overview.

I noticed the fee is normally $799 (until Friday, then $1099), but 
it's
$275 for committers. That means that anyone who's a committer on 
any
Apache project whatsoever /only/ pays $275 to attend the entire 
conference,

right?

Rich: That's correct.



The registration page says there is an additional fee for tutorials 
on
April 10th: $399 for 1/2 day tutorials ($299 for students) and $749 
for full

day tutorials (students and attendees). What it doesn't say is:

1) Is there an additional fee for tutorials on April 10th for

/committers/?

Rich: Yes, tutorials have a fee for everyone.

2) Is there an additional fee for tutorials on April 11th for anyone 
(it
only mentions April 10th, but the schedule shows tutorials on April 
11th as

well)?

Rich: We'll get that fixed.

3) Is there an additional fee for project summits on April 10th or 
11th?


Rich: Project summits are usually open to anyone interested in the
project, and no extra fee is charged.


It says they will have 5-9 tracks going on this year. I assume that
means 5-9 conference rooms (based on the # of CFPs submitted), which 
means

5-9 simultaneous talks can occur.

Rich: That is correct.


It sounds like there is potentially time to have multiple talks on

Apache Logging. Though I am new-ish, I'd love to present on behalf of
Apache Logging. Do we want to have multiple talks?


Nick

On Jan 26, 2014, at 9:29 PM, Ralph Goers wrote:


I would like to attend but I'm not sure I can.

Ralph

On Jan 25, 2014, at 11:11 AM, Christian Grobmeier 
grobme...@gmail.com

wrote:



Hi folks,

I would like to remind you ApacheCon is happening in April 2014.
If you would like to submit your talk, now is the chance.

I think it would be great to have somebody presenting our Logging

frameworks.

I will not be there unfortunately.

Regards,
Christian

---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL

Re: GA?

2014-01-27 Thread Christian Grobmeier

If people really thing that another non-GA release is necessary, please 
label it RC.


Beta sounds as log4j2 is absolutely not ready but this isn't the case.
At least with a RC we show some confidence in what we do.

As additions are easier to make then removals, I would even sacrifice 
something from the LogLevels enhancement

if it can be added later without breaking BC.

Personally I think it is necessary to make a GA as soon as possible. 
People ask me a lot
about when we do become GA. Looks like folks don't like to use *beta 
software

or even take it serious.


On 27 Jan 2014, at 17:18, Ralph Goers wrote:

Due to the API change I can agree with having another beta or an RC 
but the reason I asked about GA is that I am not aware of very many 
showstopper issues that need to be addressed.  I am sensing that you 
have a real reluctance to have Log4j 2 released as GA and I am trying 
to understand what the reason is.


Ralph

On Jan 27, 2014, at 6:15 AM, Gary Gregory garydgreg...@gmail.com 
wrote:


I agree with Nick. Changing levels to be extensible warrants another 
Beta. I'd like to see a stable API before we get into RC mode.


What about:

- Now: Another Beta
- +1 month, If the API is stable: RC1
- RCs until shows stoppers are fixed, pick a rhythm: once a week may 
be too much, once a month too long. Every two weeks seems pretty 
frequent for our bunch for a ramp down.


Thoughts on that?

I am not so much concerned about OSGi now since I look at this as 
more of a packaging issue and how much gets dragged in the container 
with dependencies. For OSGi, are we really considering delivering one 
bundle (jar) per appender?


I am more concerned about all the issues people seem to have in 
servlet environments.



Gary


On Mon, Jan 27, 2014 at 7:22 AM, Nick Williams 
nicho...@nicholaswilliams.net wrote:
I wouldn't necessarily vote against a GA, but given that we just 
MAJORLY overhauled Level, I think a brief RC is in order. It would be 
a shame if someone found a problem with Level a week after GA that 
caused us to need to change the API to fix it.

Nick


On Jan 27, 2014, at 12:51 AM, Remko Popma wrote:

I'd like to fix LOG4J-412 and 448, but neither of them are 
showstoppers IMHO.


Remko

On Monday, January 27, 2014, Ralph Goers 
ralph.go...@dslextreme.com wrote:
Since we are having good discussions I would also like to find out 
what are blockers to a GA release.  My list includes:
1. The fix Nick is working on to allow Servlet initialization to be 
disabled from automatically happening in a 3.0 container.
2. Support for programmatic configuration of Loggers. I planned on 
working on that this weekend but worked on the custom levels 
instead.


While I believe better support for OSGi is necessary I don’t 
believe we will be able to do that for GA.


Are there any other Jira issues or features that anybody else feels 
is required?


Ralph
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org






--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
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



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

ApacheCon CFP

2014-01-25 Thread Christian Grobmeier

Hi folks,

I would like to remind you ApacheCon is happening in April 2014.
If you would like to submit your talk, now is the chance.

I think it would be great to have somebody presenting our Logging frameworks.
I will not be there unfortunately.

Regards,
Christian

---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Logo contest closes by 31.01.2014

Dear all,

as previously discussed, the Log4j logo contest will be closed
on 31.01.2014. No more submissions will be accepted until then.

If you have another suggestion to make, please make sure
you enter it before that date.

Thanks!

Christian

---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Levels added in revision 1560602


What I miss in this discussion are actually good examples of what the
(new) log levels are intended for.

In example, Gary mentioned he is on a wireshark level with  trace.
That's fine, because it would give some idea when to use verbose (maybe 
entering method).


Maybe I missed it when what I ask for was already written,
but I believe if we can give concrete example how log levels should be
used then we are a step further.

I was asked quite a log what should be logged with which level.

I think making the difference between trace and debug is already 
difficult for a lot of users.

In the past two years i asked a lot of people how they log.

The answer was: exceptions on error, the rest on debug.

What we lack is a good recommendation how log levels should be used.
Something which is on our front page and which lets the average Java 
programmer fully

understand when he uses what, and maybe even why.

If we have something like that it is much easier to argue pro/contra
the new log levels.





On 24 Jan 2014, at 18:36, Scott Deboy wrote:


To be fair, I think we represent a reasonable fraction of the
users..some won't touch new predefined levels, some will use it -
that's the reason for adding it - we hit a significant portion of use
cases with small additional number of built-in levels.

The two solutions don't provide the same thing, do they?  If they do,
I wouldn't be pressing the issue.

If there is a way for us, via annotations or whatever mechanism we
define for 'custom levels', to add support easily for the newly
pre-defined levels, then we should do it.

Specifically, I'm ok with any mechanism (even using the new custom
level mechanism, but provide by log4j itself), where log4j users are
able to call:

logger.notice(something);

Anything else and it won't meet my expectations for usability.

By the way, while we're at it, let's remove fatal.

Scott


On 1/24/14, Remko Popma remko.po...@gmail.com wrote:
I'm not questioning your experience, and I believe you when you say 
that

the proposed levels would be a perfect match for your current work
environment.

However, out of the eight people that participated in the discussion 
on
adding levels, four expressed strong reservations about adding 
pre-defined
levels. We are all programmers on this list. So I think we can 
reasonable
assume that a large fraction of users would also not like this 
change.


On top of that, we have a more powerful and elegant alternative 
solution

that makes adding pre-defined levels unnecessary.
Sorry, but I veto the commit.




On Sat, Jan 25, 2014 at 1:49 AM, Gary Gregory
garydgreg...@gmail.comwrote:


On Thu, Jan 23, 2014 at 10:18 PM, Ralph Goers
ralph.go...@dslextreme.comwrote:

Gary, although Remko hasn’t said it I think he is implying that 
he is
vetoing the code commit. Unfortunately, unless you can convince 
Remko

otherwise you are going to have to revert the commit.

Remko, if that isn’t your intention then please say so as it will 
save

Gary a bunch of work.



Hello, hello,

Wow, what a pickle of religious debate this has turned into!

Before I do indeed do more work:








Ralph

On Jan 23, 2014, at 6:34 PM, Remko Popma remko.po...@gmail.com 
wrote:





I wish you had a story of some kind to show why you are so strongly
opposed to the new levels. I just wonder then why you are not 
arguing for
fewer levels? Is 6 levels just the perfect number in your mind? If 
you
designed a new logging system right now in a clean room approach, 
what

would you devise?

FWIW, I do consider Log4j2 a brand new system, granting us the 
freedom to
break APIs with version 1, which we've obviously done, but not in a 
way

that will make it too difficult to port client code. For custom
appenders,
I've not tried to port my version 1 appenders yet...


To clarify my position on the proposed DIAG, VERBOSE, NOTICE log 
levels:

I don't think these levels should be added to the Log4J API.
Here is my thinking:

1. The current five levels are a de facto. standard. (For example, 
they

match the SLF4J levels.)

But they do not match JUL, which is more of a standard since it is 
in

the

JRE; albeit a _brain-dead_ standard; no DEBUG level JUL? Really?
So clearly we care about certain kinds of standard but not others.
Since the Slf4j author created Log4j1, I would not expect otherwise 
and

it
should not make it the best solution moving forward by default.


They are sufficient for the vast majority of log4j users. We should 
be
hesitant to change this. My position would be to not change this 
unless

we
all think this is a really good idea. (The bar should be high for 
this

change.)

What are you afraid of? Confusing developers and users with 3 new
levels?

Let's give them more credit than that! ;)


2. From a practical point of view, making. levels an Extensible 
Enum

provides a more powerful alternative solution, making the proposed
levels
unnecessary.
3. From an engineering/aestical POV, I feel the proposed levels are
arbitrary

Re: Levels added in revision 1560602


On 24 Jan 2014, at 21:47, Paul Benedict wrote:


We should ensure that both the Javadocs and the user guide explain
recommended usages for these. Mailing lists are for the most die-hard
development fans. :-)


+1

Recommendations and documentation are/is absolutely necessary.

I will happily go through the mailing list to look how you use the 
various log levels.
But you also should know that I have read a ton of mails on this topic 
the past
two days and I am still unsure how *you* use the log levels. I am still 
stuck with my own usage,
and that is in my opinion the point why we can't reach an agreement 
easily.






On Fri, Jan 24, 2014 at 2:38 PM, Gary Gregory 
garydgreg...@gmail.comwrote:


There have been descriptions of what the levels are for... see Ralph 
'

message, many of mine and others. I know it can be tedious to go back
through various threads but the info is there. If you want more info, 
feel

free to ask ;)

Gary


 Original message 
From: Christian Grobmeier
Date:01/24/2014 14:20 (GMT-05:00)
To: Log4J Developers List
Subject: Re: Levels added in revision 1560602

What I miss in this discussion are actually good examples of what the
(new) log levels are intended for.

In example, Gary mentioned he is on a wireshark level with  trace.
That's fine, because it would give some idea when to use verbose 
(maybe

entering method).

Maybe I missed it when what I ask for was already written,
but I believe if we can give concrete example how log levels should 
be

used then we are a step further.

I was asked quite a log what should be logged with which level.

I think making the difference between trace and debug is already
difficult for a lot of users.
In the past two years i asked a lot of people how they log.

The answer was: exceptions on error, the rest on debug.

What we lack is a good recommendation how log levels should be used.
Something which is on our front page and which lets the average 
Java

programmer fully
understand when he uses what, and maybe even why.

If we have something like that it is much easier to argue pro/contra
the new log levels.





On 24 Jan 2014, at 18:36, Scott Deboy wrote:


To be fair, I think we represent a reasonable fraction of the
users..some won't touch new predefined levels, some will use it -
that's the reason for adding it - we hit a significant portion of 
use

cases with small additional number of built-in levels.

The two solutions don't provide the same thing, do they?  If they 
do,

I wouldn't be pressing the issue.

If there is a way for us, via annotations or whatever mechanism we
define for 'custom levels', to add support easily for the newly
pre-defined levels, then we should do it.

Specifically, I'm ok with any mechanism (even using the new custom
level mechanism, but provide by log4j itself), where log4j users are
able to call:

logger.notice(something);

Anything else and it won't meet my expectations for usability.

By the way, while we're at it, let's remove fatal.

Scott


On 1/24/14, Remko Popma remko.po...@gmail.com wrote:

I'm not questioning your experience, and I believe you when you say
that
the proposed levels would be a perfect match for your current work
environment.

However, out of the eight people that participated in the 
discussion

on
adding levels, four expressed strong reservations about adding
pre-defined
levels. We are all programmers on this list. So I think we can
reasonable
assume that a large fraction of users would also not like this
change.

On top of that, we have a more powerful and elegant alternative
solution
that makes adding pre-defined levels unnecessary.
Sorry, but I veto the commit.




On Sat, Jan 25, 2014 at 1:49 AM, Gary Gregory
garydgreg...@gmail.comwrote:


On Thu, Jan 23, 2014 at 10:18 PM, Ralph Goers
ralph.go...@dslextreme.comwrote:


Gary, although Remko hasn’t said it I think he is implying that
he is
vetoing the code commit. Unfortunately, unless you can convince
Remko
otherwise you are going to have to revert the commit.

Remko, if that isn’t your intention then please say so as it 
will

save
Gary a bunch of work.



Hello, hello,

Wow, what a pickle of religious debate this has turned into!

Before I do indeed do more work:








Ralph

On Jan 23, 2014, at 6:34 PM, Remko Popma remko.po...@gmail.com
wrote:




I wish you had a story of some kind to show why you are so 
strongly

opposed to the new levels. I just wonder then why you are not
arguing for
fewer levels? Is 6 levels just the perfect number in your mind? If
you
designed a new logging system right now in a clean room approach,
what
would you devise?

FWIW, I do consider Log4j2 a brand new system, granting us the
freedom to
break APIs with version 1, which we've obviously done, but not in 
a

way
that will make it too difficult to port client code. For custom
appenders,
I've not tried to port my version 1 appenders yet...



To clarify my position on the proposed DIAG, VERBOSE, NOTICE log
levels:
I don't think

Re: Levels added in revision 1560602