We partly use slf4j internally already for tests, etc.
But moving the whole Logger mess over to slf4j would be really great. There are
lots of tests (I sadly also found productive code too) still using
System.out.println.
The question is if we (internally) drop
+1
2011/6/9 Stephen Connolly stephen.alan.conno...@gmail.com:
Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11139styleName=Htmlversion=17146
There are still a couple of issues left in JIRA:
+1
-Lukas
Stephen Connolly wrote:
Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11139styleName=Htmlversion=17146
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11139status=1
Staging
+1 (non-binding)
On Thu, Jun 9, 2011 at 5:49 PM, Jesse Glick jesse.gl...@oracle.com wrote:
Non-binding +1; no apparent problems in NetBeans integration during basic
interactive tests.
-
To unsubscribe, e-mail:
+1 (binding)
LieGrue,
strub
--- On Fri, 6/10/11, Brian Demers brian.dem...@gmail.com wrote:
From: Brian Demers brian.dem...@gmail.com
Subject: Re: [VOTE] Release Maven Indexer version 4.1.1
To: Maven Developers List dev@maven.apache.org
Date: Friday, June 10, 2011, 1:44 PM
+1 (non-binding)
On 6/10/11 3:48 AM, Mark Struberg wrote:
We partly use slf4j internally already for tests, etc.
But moving the whole Logger mess over to slf4j would be really great. There are
lots of tests (I sadly also found productive code too) still using
System.out.println.
The question is if we
personally, there are a number of issues I have had with how
slf4j/logback handles message formatting for i18n... other than the
logging frameworks I have rolled myself, slf4j is the closest I've
seen to logging done right... but it is still a bit far off the right
path...
Oh logging why do you
lest anyone think I'm doing NIH, the logging frameworks I have
implemented myself (they were under commercial license for previous
employer) were less than perfect, but having seen my mistakes I think
I have a better handle on the right path to take!
On 10 June 2011 16:42, Stephen Connolly
On Fri, Jun 10, 2011 at 5:43 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
but having seen my mistakes I think
I have a better handle on the right path to take!
Strange enough, that's almost definitely what Ceki Gülcü would say ... :-)
--
Capitalism is the astounding belief
the problem is: logging gets tricky once you have OSGIi or
ThreadContextClassLoaders in place...
So I'd favour slf4j. We don't need a 'perfect' solution - we just need
something better than we had in place ;)
LieGrue,
strub
--- On Fri, 6/10/11, Jochen Wiedmann jochen.wiedm...@gmail.com wrote:
+1
2011/6/9 Tamás Cservenák ta...@cservenak.net:
Hi,
Current 4.1.1 version is mostly bugfix release for latest 4.0.1
improving indexer robustness, lessen unnecessary IO burden and smaller
POM fixes regarding site publishing.
no staged one ? you will publish it after the release ?
We solved
+1
Damian
I will be out of the office starting 10.06.2011 and will not return until
14.06.2011.
I have no acces to my mailbox, I will reply to your message upon return.
Thank you!
can somebody update the wiki, I'm only on a phone
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 10 Jun 2011 20:44, Julia Antonova juli...@jtbrussia.com wrote:
I will be
God I love this meme.
On Fri, Jun 10, 2011 at 4:56 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
can somebody update the wiki, I'm only on a phone
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct
HI all,
Just my 2 cents :
Main problem with jumping into Maven core development is understanding of
internal architecture and core parts. Also this affects development of
plugins. Thus IMO improving this can definitely animate Maven ecosystem
(Core, Core Plugins, Mojo, ...) in general.
Another
On 2011-06-09 23:45, Benson Margulies wrote:
I'd like to offer a small suggestion.
One of the big barriers to maven happiness is the difficulty of
understanding, in some cases, why it does what it does.
This suggests to me three efforts that might offer an opportunity to
learn core code
On Sat, Jun 11, 2011 at 6:26 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
can somebody update the wiki, I'm only on a phone
Updated.
One day I will calculate the proper holidays instead of elapsed calendars days.
It's a bit unfair to be jealous of inflated numbers because they
I'm not sure what you are after John. Logback provides a formatter where you
can do
logger.debug(Hello, {}, John) and it will replace the curly braces with
John. My Log4J 2.0 will do the same thing. MessageFormat is fairly slow,
but if you wanted to use that instead my Log4J 2.0
Actually, SLF4J's tie to Ceki's I18n project is one thing I really dislike.
IMO, localization should be done at the last possible moment. If you really
want an internationalized log then you should be logging message ids and data
and then doing the localization in your log viewer, not as you
SLF4J isn't a logging framework. It is an API. While Logback is much better
than Log4J 1.x it still has significant architectural problems.
Ralph
On Jun 10, 2011, at 9:20 AM, Mark Struberg wrote:
the problem is: logging gets tricky once you have OSGIi or
ThreadContextClassLoaders in
Well, I could use feedback on
https://svn.apache.org/repos/asf/logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers/
On Jun 10, 2011, at 8:43 AM, Stephen Connolly wrote:
lest anyone think I'm doing NIH, the logging frameworks I have
implemented myself (they were under commercial license for
22 matches
Mail list logo
