On Jul 17, 2012, at 11:17 AM, Gary Gregory wrote:
> Checkstyle notes a license header problem here:
>
> http://people.apache.org/~rgoers/log4j2/log4j-core/xref/org/apache/logging/log4j/core/config/plugins/ResolverUtil.html#1
>
Yes, I copied that class from struts so I left the header as they h
Checkstyle notes a license header problem here:
http://people.apache.org/~rgoers/log4j2/log4j-core/xref/org/apache/logging/log4j/core/config/plugins/ResolverUtil.html#1
Gary
On Sun, Jul 15, 2012 at 2:44 AM, Ralph Goers wrote:
> This is a vote to release Log4j 2.0-alpha1, which will be the first
On Tue, Jul 17, 2012 at 8:00 PM, Ralph Goers wrote:
> Thanks for this excellent feedback Christian. Based on this I am going to
> cancel the vote as I agree, there are some items here that really need to be
> fixed. I will answer a few below.
Cool!
I can try to fix some issue myself tomorrow,
[
https://issues.apache.org/jira/browse/LOG4J2-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-62.
-
Resolution: Invalid
Closing this since the question doesn't apply to Log4j 2.
> Configure
Thanks for this excellent feedback Christian. Based on this I am going to
cancel the vote as I agree, there are some items here that really need to be
fixed. I will answer a few below.
On Jul 17, 2012, at 1:10 AM, Christian Grobmeier wrote:
> Hello,
>
> tag is building (mvn test) and the report
https://issues.apache.org/bugzilla/show_bug.cgi?id=53557
Jacob Kjome changed:
What|Removed |Added
OS||All
--- Comment #1 from Jacob Kjome
[
https://issues.apache.org/jira/browse/LOG4J2-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416032#comment-13416032
]
Reshmi Choudhury commented on LOG4J2-62:
Thanks for your reply.
Yes, we are using
https://issues.apache.org/bugzilla/show_bug.cgi?id=53557
Priority: P2
Bug ID: 53557
Assignee: log4j-dev@logging.apache.org
Summary: Configure java.util.logging messages to custom log
files using log4j.xml
Severity: normal
https://issues.apache.org/bugzilla/show_bug.cgi?id=53548
--- Comment #3 from grobmeier ---
I think the easiest way is to rename that class (the companion one).
Not sure if it is an general agreement but I really try to avoid classes with
same names/paths as it always leads to problems (at least
Hello,
tag is building (mvn test) and the reports (rat etc) look all fine. I
would like to suggest we add Findbugs after this release.
MD5/ASC files all are fine. I could see that LICENSES files etc were
all fine too.
I have some minor stuff here:
- Incosistent use of name: Apache Log4j2 2.0-a
Hello,
On Tue, Jul 17, 2012 at 6:42 AM, Ralph Goers wrote:
> This vote has now been open for 2 days and no one has reviewed it? I would
> appreciate you taking the time to look at it.
I am already working on it. Its ~100 files to download (including
md5/asc) so this is not so tribial :-)
Anywa
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project logging-log4j-extras-test has an issue affecting its community
integratio
12 matches
Mail list logo