ry a full build to make sure all the unit tests pass? 'mvn clean
install'
Thank you,
Gary
> Log4j 2.0 with JBoss EAP 6.2
> -
>
> Key: LOG4J2-548
> URL: https://issues.apache.org/jira/browse/LOG4J2-548
&
(community edition) with the
attached patch. I don't have the time or knowledge necessary to fold this in,
but anyone is welcome to take whatever might be useful from this
> Log4j 2.0 with JBoss EAP 6.2
> -
>
> Key: LOG4J2-548
>
[
https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers reassigned LOG4J2-548:
--
Assignee: Ralph Goers
> Log4j 2.0 with JBoss EAP
"vfs" protocol?
> Log4j 2.0 with JBoss EAP 6.2
> -
>
> Key: LOG4J2-548
> URL: https://issues.apache.org/jira/browse/LOG4J2-548
> Project: Log4j 2
> Issue Type: Bug
> Component
ople experiencing problems with it as everything
requires custom code to support them.
I added support for VFSZip because I was working with webapps in JBoss at the
time. I've never used EARs so didn't run across this.
> Log4j 2.0 with JBoss EAP 6.2
> -
>
this is using Java 7 VFS?
> Log4j 2.0 with JBoss EAP 6.2
> -
>
> Key: LOG4J2-548
> URL: https://issues.apache.org/jira/browse/LOG4J2-548
> Project: Log4j 2
> Issue Type: Bug
> C
rvice Thread Pool -- 53 DEBUG Took 29.296404 seconds to
load 0 plugins from package com.logging.appender.log4j2
> Log4j 2.0 with JBoss EAP 6.2
> -
>
> Key: LOG4J2-548
> URL: https://issues.apache.org/jira/browse/LOG4J2-548
>
296404 seconds to
load 0 plugins from package com.logging.appender.log4j2
> Log4j 2.0 with JBoss EAP 6.2
> -
>
> Key: LOG4J2-548
> URL: https://issues.apache.org/jira/browse/LOG4J2-548
> Project: Log4j
a:122)
15:41:38,720 INFO [stdout] (ServerService Thread Pool -- 53)
15:41:50,981 INFO [stdout] (ServerService Thread Pool -- 53) 2016-02-05
15:41:50,980 ServerService Thread Pool -- 53 DEBUG Took 29.296404 seconds to
load 0 plugins from package com.logging.appender.log4j2
[
https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-548:
---
Affects Version/s: 2.1
> Log4j 2.0 with JBoss EAP
[
https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-548:
---
Fix Version/s: (was: 2.1)
> Log4j 2.0 with JBoss EAP
On Mon, Aug 4, 2014 at 9:15 AM, Mikael Ståldal <
mikael.stal...@appearnetworks.com> wrote:
> As far as I can see from testing and inspecting the code, the JSONLayout
> does never output any comma (,) between the events.
>
> Shouldn't it do so when complete="true" in order to generate a well-formed
:52 PM, Mikael Ståldal <
> mikael.stal...@appearnetworks.com> wrote:
>
>> The JSONLayout in Log4j 2.0 requires Jackson dependency, but this is not
>> mentioned in the documentation:
>>
>> http://logging.apache.org/log4j/2.x/manual/layouts.html
>>
>
As far as I can see from testing and inspecting the code, the JSONLayout
does never output any comma (,) between the events.
Shouldn't it do so when complete="true" in order to generate a well-formed
JSON document?
--
Mikael Ståldal
Chief Software Architect
*Appear*
Phone: +46 8 545 91 572
Email
4, 2014 at 2:52 PM, Mikael Ståldal <
mikael.stal...@appearnetworks.com> wrote:
> The JSONLayout in Log4j 2.0 requires Jackson dependency, but this is not
> mentioned in the documentation:
>
> http://logging.apache.org/log4j/2.x/manual/layouts.html
>
> --
> Mikael Ståldal
> Chie
Fixed in SVN.
Gary
On Mon, Aug 4, 2014 at 8:52 AM, Mikael Ståldal <
mikael.stal...@appearnetworks.com> wrote:
> The JSONLayout in Log4j 2.0 requires Jackson dependency, but this is not
> mentioned in the documentation:
>
> http://logging.apache.org/log4j/2.x/manual/layouts.ht
The JSONLayout in Log4j 2.0 requires Jackson dependency, but this is not
mentioned in the documentation:
http://logging.apache.org/log4j/2.x/manual/layouts.html
--
Mikael Ståldal
Chief Software Architect
*Appear*
Phone: +46 8 545 91 572
Email: mikael.stal...@appearnetworks.com
7 gives "java.lang.ClassNotFoundException:
> org.apache.logging.log4j.spi.AbstractLoggerWrapper" with log4j-2.0-rc2
> -
>
> Key: LOG4J2-700
[
https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-548:
---
Fix Version/s: (was: 2.0)
2.1
> Log4j 2.0 with JBoss EAP
Congratulations on the release! I've been looking forward to this for over
a year! :)
On 17 July 2014 00:26, Ralph Goers wrote:
> The Apache Log4j 2 team is pleased to announce the Log4j 2.0 release!
>
> Apache log4j is a well known framework for logging application behavior.
&
The Apache Log4j 2 team is pleased to announce the Log4j 2.0 release!
Apache log4j is a well known framework for logging application behavior. Log4j
2 is an upgrade to
Log4j that provides significant improvements over its predecessor, Log4j 1.x,
and provides
many of the improvements available
The vote is now closed and passes with binding +1 votes from: Remko Popma,
Christian Grobmeier, Ralph Goers and Gary Gregory, although Gary expressed a
desire to have it re-spun as rc3. Additional non-binding +1 votes came from:
Bruno Mahe and Matt Sticker. Bruce Brouwer cast a non-binding +0.
>>> Perhaps we should delay voting on 2.0 until we know how 703 and 713
>>>>> play out. Especially since splitting classes in two might be the only
>>>>> solution.
>>>>>
>>>>> Gary
>>>>>
>>>>>
>
oo.
>>>>>>
>>>>>> Perhaps we should delay voting on 2.0 until we know how 703 and 713 play
>>>>>> out. Especially since splitting classes in two might be the only
>>>>>> solution.
>>>>>>
>>>>>>
gt;>
>>>> Gary
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Jul 14, 2014 at 11:20 PM, Gary Gregory
>>>> wrote:
>>>>
>>>>> I have a simple fix for
>>>>> https://issues.apache.org/ji
://issues.apache.org/jira/browse/LOG4J2-703 "Could not find class
>>>> 'javax.naming.InitialContext', referenced from method
>>>> org.apache.logging.log4j.core.lookup.JndiLookup.lookup".
>>>>
>>>> This breaks BC in org.apache.logging.log4j.core.ut
t;>>> solution.
>>>>>>
>>>>>> Gary
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Mon, Jul 14, 2014 at 11:20 PM, Gary Gregory
>>>>>>> wrote:
&
a simple fix for
>>>> https://issues.apache.org/jira/browse/LOG4J2-703 "Could not find class
>>>> 'javax.naming.InitialContext', referenced from method
>>>> org.apache.logging.log4j.core.lookup.JndiLookup.lookup".
>>>>
>>>> T
javax.naming.InitialContext', referenced from
>>>> method org.apache.logging.log4j.core.lookup.JndiLookup.lookup".
>>>>
>>>> This breaks BC in org.apache.logging.log4j.core.util.Closer.
>>>>
>>>> So the question is: Are we, and if yes, w
uot;.
>>>
>>> This breaks BC in org.apache.logging.log4j.core.util.Closer.
>>>
>>> So the question is: Are we, and if yes, what modules, allowing ourselves
>>> to break BC in a non-major release.
>>>
>>> Gary
>>>
>>>
Here is my +1 vote on the release. I will close the vote in about 8 hours if
anyone else wants to weigh in.
Ralph
On Jul 12, 2014, at 5:25 PM, Ralph Goers wrote:
> This is a vote to release Log4j 2.0, the first GA release of Log4j 2.
>
> Please test and cast your votes.
> [] +1,
r to have the one and
perfect version. That said, we have already wait too long to make Log4j
2.0 GA. There was the argument of the first impression - the first
impression more and more becomes that we simply don't have the balls to
make a GA release.
Regards,
Christian
On 15 Jul 2014, at 15:
ight be the only solution.
>>>
>>> Gary
>>>
>>>
>>>
>>>
>>> On Mon, Jul 14, 2014 at 11:20 PM, Gary Gregory
>>> wrote:
>>> I have a simple fix for https://issues.apache.org/jira/browse/LOG4J2-703
>>> &quo
Fine with me.
Gary
Original message From: Bruce Brouwer
Date:07/15/2014 10:03 (GMT-05:00)
To: Log4J Developers List
Subject: Re: [VOTE] Log4j 2.0 candidate 1
My changes are ready to put in now. Is it equally acceptable to put them
in right now since in your view they
At this point we can keep it all in trunk afaiac...
Gary
Original message From: Bruce Brouwer
Date:07/15/2014 08:53 (GMT-05:00)
To: Log4J Developers List
Cc: Logging PMC Subject: Re:
[VOTE] Log4j 2.0 candidate 1
I can see that, Ralph. I too want to get 2.0 out the door
reated
>>>>> https://issues.apache.org/jira/browse/LOG4J2-713 and committed a fix
>>>>> to trunk.
>>>>>
>>>>> I wonder what else will pop up on Android. It looks like one of our
>>>>> JDBC classes also depends on JNDI s
t;>>> Perhaps we should delay voting on 2.0 until we know how 703 and 713
>>>> play out. Especially since splitting classes in two might be the only
>>>> solution.
>>>>
>>>> Gary
>>>>
>>>>
>>>>
>>>
modules, allowing ourselves
>> to break BC in a non-major release.
>>
>> Gary
>>
>>
>> On Sat, Jul 12, 2014 at 8:25 PM, Ralph Goers > > wrote:
>>
>>> This is a vote to release Log4j 2.0, the first GA release of Log4j 2.
>>>
>>> Please t
have a simple fix for
>>>> https://issues.apache.org/jira/browse/LOG4J2-703 "Could not find class
>>>> 'javax.naming.InitialContext', referenced from method
>>>> org.apache.logging.log4j.core.lookup.JndiLookup.lookup".
>>>>
>>>&
11:20 PM, Gary Gregory
>>>>> wrote:
>>>>> I have a simple fix for https://issues.apache.org/jira/browse/LOG4J2-703
>>>>> "Could not find class 'javax.naming.InitialContext', referenced from
>>>>> method org.apache.loggin
;>> I have a simple fix for https://issues.apache.org/jira/browse/LOG4J2-703
>>> "Could not find class 'javax.naming.InitialContext', referenced from method
>>> org.apache.logging.log4j.core.lookup.JndiLookup.lookup".
>>>
>>> This breaks BC in org.apache
ookup.JndiLookup.lookup".
>>>
>>> This breaks BC in org.apache.logging.log4j.core.util.Closer.
>>>
>>> So the question is: Are we, and if yes, what modules, allowing ourselves to
>>> break BC in a non-major release.
>>>
>&
.util.Closer.
>>
>> So the question is: Are we, and if yes, what modules, allowing ourselves
>> to break BC in a non-major release.
>>
>> Gary
>>
>>
>> On Sat, Jul 12, 2014 at 8:25 PM, Ralph Goers
>> wrote:
>>
>>> This is a vote t
14 05:25 PM, Ralph Goers a écrit :
> This is a vote to release Log4j 2.0, the first GA release of Log4j 2.
>
> Please test and cast your votes.
> [] +1, release the artifacts
> [] -1, don't release because…
>
> The vote will remain open for 72 hours (or more if required).
&
t;
> Gary
>
>
> On Sat, Jul 12, 2014 at 8:25 PM, Ralph Goers
> wrote:
>
>> This is a vote to release Log4j 2.0, the first GA release of Log4j 2.
>>
>> Please test and cast your votes.
>> [] +1, release the artifacts
>> [] -1, don't release because…
>
question is: Are we, and if yes, what modules, allowing ourselves to
break BC in a non-major release.
Gary
On Sat, Jul 12, 2014 at 8:25 PM, Ralph Goers
wrote:
> This is a vote to release Log4j 2.0, the first GA release of Log4j 2.
>
> Please test and cast your votes.
> [] +1, rele
org.bson
Minor issues with components side-nav: updated LOG4J2-678 with details.
Project Reports > Surefire Report
Page Not Found error
Sent from my iPhone
On 2014/07/13, at 9:25, Ralph Goers > wrote:
This is a vote to release Log4j 2.0, the first GA release of Log4j 2.
Please test an
at, Jul 12, 2014 at 8:25 PM, Ralph Goers
>>> wrote:
>>
>>> This is a vote to release Log4j 2.0, the first GA release of Log4j 2.
>>>
>>> Please test and cast your votes.
>>> [] +1, release the artifacts
>>> [] -1, don't release becaus
avadoc 8 doclint errors.
>
> Gary
>
>
> On Sat, Jul 12, 2014 at 8:25 PM, Ralph Goers
> wrote:
>
>> This is a vote to release Log4j 2.0, the first GA release of Log4j 2.
>>
>> Please test and cast your votes.
>> [] +1, release the artifacts
>> [] -1,
Just a note for the record and as we know, we fail building with Java 8 due
to Javadoc 8 doclint errors.
Gary
On Sat, Jul 12, 2014 at 8:25 PM, Ralph Goers
wrote:
> This is a vote to release Log4j 2.0, the first GA release of Log4j 2.
>
> Please test and cast your votes.
> [] +1,
the story with the "Disallowed import" checkstyle warnings?
>
> Gary
>
>
> On Sat, Jul 12, 2014 at 8:25 PM, Ralph Goers
> wrote:
> This is a vote to release Log4j 2.0, the first GA release of Log4j 2.
>
> Please test and cast your votes.
> [] +1, r
What is the story with the "Disallowed import" checkstyle warnings?
Gary
On Sat, Jul 12, 2014 at 8:25 PM, Ralph Goers
wrote:
> This is a vote to release Log4j 2.0, the first GA release of Log4j 2.
>
> Please test and cast your votes.
> [] +1, release the artifacts
This is a vote to release Log4j 2.0, the first GA release of Log4j 2.
Please test and cast your votes.
[] +1, release the artifacts
[] -1, don't release because…
The vote will remain open for 72 hours (or more if required).
New features:
o LOG4J2-519: Added support for generating custom l
xception:
> org.apache.logging.log4j.spi.AbstractLoggerWrapper" with log4j-2.0-rc2
> -
>
> Key: LOG4J2-700
> URL: https://issues.apache.org/jira/browse/LOG4J2-700
&g
.lang.ClassNotFoundException:
> org.apache.logging.log4j.spi.AbstractLoggerWrapper" with log4j-2.0-rc2
> -
>
> Key: LOG4J2-700
> URL: https://issues.apache.org/jira/
xception:
> org.apache.logging.log4j.spi.AbstractLoggerWrapper" with log4j-2.0-rc2
> -
>
> Key: LOG4J2-700
> URL: https://issues.apach
s 3.2.7 gives "java.lang.ClassNotFoundException:
> org.apache.logging.log4j.spi.AbstractLoggerWrapper" with log4j-2.0-rc2
> -
>
> Key: LOG
MyBatis 3.2.7 gives "java.lang.ClassNotFoundException:
> org.apache.logging.log4j.spi.AbstractLoggerWrapper" with log4j-2.0-rc2
> -
>
>
7 gives "java.lang.ClassNotFoundException:
> org.apache.logging.log4j.spi.AbstractLoggerWrapper" with log4j-2.0-rc2
> -
>
> Key: LOG4J2-700
ption:
org.apache.logging.log4j.spi.AbstractLoggerWrapper" with log4j-2.0-rc2 (was:
MyBatis 3.2.7 gives "java.lang.ClassNotFoundException:
org.apache.logging.log4j.spi.AbstractLoggerWrapper" since rc2)
> MyBatis 3.2.7 gives "java.lang.ClassNotFoundException:
> org.apache.logging.log4j.spi.AbstractLo
[
https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-548:
---
Fix Version/s: (was: 2.0-rc2)
2.0
> Log4j 2.0 with JBoss EAP
The Apache Log4j 2 team is pleased to announce the Log4j 2.0-rc2 release!
Apache log4j is a well known framework for logging application behavior. Log4j
2 is an upgrade to
Log4j that provides significant improvements over its predecessor, Log4j 1.x,
and provides
many of the improvements
pache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest
>>>>>>>> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 59.114
>>>>>>>> sec <<< FAILURE! - in
>>>>>>>> org.apache.logging.log4j.flume.appender.FlumeA
t;>>>>>> org.apache.logging.log4j.flume.appender.FlumeAppenderTest
>>>>>>> testBatch(org.apache.logging.log4j.flume.appender.FlumeAppenderTest)
>>>>>>> Time elapsed: 37.945 sec <<< ERROR!
>>>>>>> org.apache.l
ig.callAppenders(LoggerConfig.java:426)
>>>>> at
>>>>> org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:405)
>>>>> at
>>>>> org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:365)
>>
The vote passes with +1s from Remko Popma, Gary Gregory and Ralph Goers along
with a non-binding +1 from Matt Sicker.
I will proceed with the rest of the release process shortly.
Ralph
-
To unsubscribe, e-mail: log4j-dev-unsubsc
;>>>> Bogus.
>>>>> o LOG4J2-392: Resolved a problem with the previous solution for
>>>>> LOG4J2-392 that resulted in dropped events
>>>>> when using AsyncLoggerConfig with slow appenders when
>>>>> application is stopped. T
environment, but there's no log4j-web module available. If you want better
>>> web container support, please add the log4j-web JAR to your web archive or
>>> server lib directory
>>> .
>>> 2014-06-24 22:06:23,439 INFO Log4j appears to be running in a Servlet
>
>> 2014-06-24 22:06:22,270 INFO Log4j appears to be running in a Servlet
>>> environment, but there's no log4j-web module available. If you want better
>>> web container support, please add the log4j-web JAR to your web archive or
>>> server lib directory
>>&
rchive or
> server lib directory
> .
> No Event returned
> No Event returned
> No Event returned
> No Event returned
> No Event returned
> No Event returned
> No Event returned
> No Event returned
> No Event returned
> No Event returned
> No Event retur
AR to your web archive or
>> server lib directory
>> .
>> No Event returned
>> No Event returned
>> No Event returned
>> No Event returned
>> No Event returned
>> No Event returned
>> No Event returned
>> No Event returned
>> No Event retu
9602da; 2013-02-19
> 08:51:28-0500)
> Maven home: C:\Java\apache-maven-3.0.5
> Java version: 1.7.0_60, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_60\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1
: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Thoughts?
Gary
On Sat, Jun 21, 2014 at 8:19 PM, Ralph Goers
wrote:
> This is a vote to release Log4j 2.0-rc2, which will hopefully be the last
> release candidate.
>
>
log4j-perf module is excluded from the binary distribution
as discussed on the ML, but the apache-log4j-2.0-rc2-src artifact
contains the source files for the log4j-perf module. Just to clarify:
this is intentionally, and not a problem, right?
I noticed several other minor things, none of them sh
excluded from the binary distribution as
> discussed on the ML, but the apache-log4j-2.0-rc2-src artifact contains the
> source files for the log4j-perf module. Just to clarify: this is
> intentionally, and not a problem, right?
>
>
> I noticed several other minor things,
releases that these are not a problem:
> src/site/resources/js/jquery.js
> src/site/resources/js/jquery.min.js
>
> Also, the log4j-perf module is excluded from the binary distribution as
> discussed on the ML, but the apache-log4j-2.0-rc2-src artifact contains the
> source f
y distribution artifacts (although it is in the -src
>> artifact).
>> This seems similar to the warning for the two js files, and we agreed with
>> previous releases that these are not a problem:
>> src/site/resources/js/jquery.js
>> src/site/resources/js/jquery.
that these are not a problem:
> src/site/resources/js/jquery.js
> src/site/resources/js/jquery.min.js
>
> Also, the log4j-perf module is excluded from the binary distribution as
> discussed on the ML, but the apache-log4j-2.0-rc2-src artifact contains the
> source f
on as
discussed on the ML, but the apache-log4j-2.0-rc2-src artifact contains the
source files for the log4j-perf module. Just to clarify: this is
intentionally, and not a problem, right?
I noticed several other minor things, none of them showstoppers, just
making a note here so they can be fixed
t; big a deal. Running through a build right now.
>>>>>
>>>>>
>>>>> On 21 June 2014 19:21, Ralph Goers wrote:
>>>>>
>>>>>> Please note that the artifacts can be downloaded by doing:
>>>>>>
>
June 2014 19:21, Ralph Goers wrote:
>>>>>> Please note that the artifacts can be downloaded by doing:
>>>>>>
>>>>>> wget -e robots=off --cut-dirs=3 -r -p -np --no-check-certificate
>>>>>> https://repository.apache.org/content/repositorie
through a build right now.
>>>>
>>>>
>>>> On 21 June 2014 19:21, Ralph Goers wrote:
>>>>
>>>>> Please note that the artifacts can be downloaded by doing:
>>>>>
>>>>> wget -e robots=off --cut-dirs=3 -r -p -np --no-check
;>
>>>> wget -e robots=off --cut-dirs=3 -r -p -np --no-check-certificate
>>>> https://repository.apache.org/content/repositories/orgapachelogging-1003
>>>>
>>>> Ralph
>>>>
>>>>
>>>> On Jun 21, 2014, at 5:19 P
that the artifacts can be downloaded by doing:
>>>
>>> wget -e robots=off --cut-dirs=3 -r -p -np --no-check-certificate
>>> https://repository.apache.org/content/repositories/orgapachelogging-1003
>>>
>>> Ralph
>>>
>>>
>>> On Ju
/content/repositories/orgapachelogging-1003
>>
>> Ralph
>>
>>
>> On Jun 21, 2014, at 5:19 PM, Ralph Goers
>> wrote:
>>
>> This is a vote to release Log4j 2.0-rc2, which will hopefully be the last
>> release candidate.
>>
>> Please note tha
aded by doing:
>
> wget -e robots=off --cut-dirs=3 -r -p -np --no-check-certificate
> https://repository.apache.org/content/repositories/orgapachelogging-1003
>
> Ralph
>
>
> On Jun 21, 2014, at 5:19 PM, Ralph Goers
> wrote:
>
> This is a vote to release Log4j 2.0-r
Please note that the artifacts can be downloaded by doing:
wget -e robots=off --cut-dirs=3 -r -p -np --no-check-certificate
https://repository.apache.org/content/repositories/orgapachelogging-1003
Ralph
On Jun 21, 2014, at 5:19 PM, Ralph Goers wrote:
> This is a vote to release Log4j
This is a vote to release Log4j 2.0-rc2, which will hopefully be the last
release candidate.
Please note that I did not add the new logo to the web site. I will add that
after the release.
Please test and cast your votes.
[] +1, release the artifacts
[] -1, don't release because…
The
Good question. Someone needs to start a vote thread. But will we be voting
for only our top pick, top 3 or 4 or what?
Ralph
On May 15, 2014, at 9:15 AM, Gary Gregory wrote:
> So... what are we doing here?
>
> Gary
>
>
> On Wed, May 14, 2014 at 9:43 AM, Ralph Goers wrote:
>
> > On May 1
So... what are we doing here?
Gary
On Wed, May 14, 2014 at 9:43 AM, Ralph Goers wrote:
>
> > On May 14, 2014, at 4:04 AM, "Christian Grobmeier"
> wrote:
> >
> >> On 14 May 2014, at 8:52, Ralph Goers wrote:
> >>
> >> Yes the Jira outlines a process that was proposed by Christian in the
> Jira
I don't know if my vote counts, but I would go with ACBG
On May 13, 2014 5:36 PM, "Ralph Goers" wrote:
> I don’t recall that we had “rules”. Just that we were going to vote.
>
> Ralph
>
> On May 13, 2014, at 1:18 PM, Gary Gregory wrote:
>
> STV: ABEF
> (I do not like D at all FWIW)
> We can onl
I'm not sure this moves the ball forward, we need to follow the procedure
we initially presented...
Gary
On Tue, May 6, 2014 at 6:28 PM, Matt Sicker wrote:
> I like:
>
>
> https://issues.apache.org/jira/secure/attachment/12605823/apache-log4j-2.png
>
> https://issues.apache.org/jira/secure/att
and use a higher resolution.
>>>
>>>
>>>
>>>
>>>
>>> *Von:* Luigi Alice [mailto:luigi.al...@persis.de]
>>> *Gesendet:* Dienstag, 13. Mai 2014 14:49
>>> *An:* Log4J Developers List
>>> *Betreff:* AW: Log4J-2.0 New Logo
&
> On May 14, 2014, at 4:04 AM, "Christian Grobmeier"
> wrote:
>
>> On 14 May 2014, at 8:52, Ralph Goers wrote:
>>
>> Yes the Jira outlines a process that was proposed by Christian in the Jira
>> issue. However, that would be equivalent to someone creating an issue and
>> saying that a new fe
I recall that usually Jim or Sam is very helpful with setting up the
voting tool for such things.
Maybe somebody else involved in Infra is willing to help as well.
Somebody got time to ask there?
On 13 May 2014, at 22:00, Ralph Goers wrote:
Then we could do it manually. You can find some docu
neat vector graphic?
On 13 May 2014 08:13, Luigi Alice wrote:
Perhaps we can change the color and use a higher resolution.
*Von:* Luigi Alice [mailto:luigi.al...@persis.de]
*Gesendet:* Dienstag, 13. Mai 2014 14:49
*An:* Log4J Developers List
*Betreff:* AW: Log4J-2.0 New Logo
Pick this one
wrote:
The jira ticket outlines a process IIRC.
Gary
Original message
From: Ralph Goers
Date:05/13/2014 17:36 (GMT-05:00)
To: Log4J Developers List
Subject: Re: Log4J-2.0 New Logo
I don’t recall that we had “rules”. Just that we were going to
vote.
Ralph
On May 13, 2014
:
> The jira ticket outlines a process IIRC.
>
> Gary
>
>
> Original message
> From: Ralph Goers
> Date:05/13/2014 17:36 (GMT-05:00)
> To: Log4J Developers List
> Subject: Re: Log4J-2.0 New Logo
>
> I don’t recall that we had “rules”. Just th
Perhaps we can change the color and use a higher resolution.
Von: Luigi Alice [mailto:luigi.al...@persis.de]
Gesendet: Dienstag, 13. Mai 2014 14:49
An: Log4J Developers List
Betreff: AW: Log4J-2.0 New Logo
Pick this one… ☺
https://issues.apache.org/jira/secure/attachment/12616371
The jira ticket outlines a process IIRC.
Gary
Original message From: Ralph Goers
Date:05/13/2014 17:36 (GMT-05:00)
To: Log4J Developers List
Subject: Re: Log4J-2.0 New Logo
I don’t recall that we had “rules”. Just that we were going to vote.
Ralph
On May 13, 2014, at
1 - 100 of 550 matches
Mail list logo
