+1
Le jeudi 9 juin 2011, Tamás Cservenák a écrit :
> 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.
>
> We solved 5 issues:
> http://jira.codehaus.org/secure/R
+1
Le jeudi 9 juin 2011, Stephen Connolly a écrit :
> Hi,
>
> We solved 5 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11139&styleName=
> Html&version=17146
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=tr
Le mardi 7 juin 2011, Paul Gier a écrit :
> On 05/27/2011 11:02 AM, Paul Gier wrote:
> > Maven 3 currently treats unrecognised version qualifiers as newer
> > releases than the GA release. For example:
> >
> > 1.0 is older than 1.0-xyz
> >
> > It also looks like this was reversed at some point,
Le vendredi 27 mai 2011, John Casey a écrit :
> On 5/27/11 1:03 PM, Benson Margulies wrote:
> > This seems to me to call out for an 'extension point' that supplies an
> > object that implements a protocol for making version decisions.
>
> That would bring up the issue of how Maven switches between
well if you are i18n-ing your logging messages you should always include a
code in the log message, that way you just google the code and presto
changeo you have your answer...
what I find is there is a logging level above which it makes sense to
i18n... usually somewhere around info/warn, but bel
No problem, just let it flow ;)
Actually I'm not sure why all this internationalization on internal error
messages at all ^^
To be honest: it _s u c k s_ to have german error messages in my logs!
Or imagine to live in Hungary: You can google almost _nothing_ that will help
you if you only have
Oops, sorry all. I was responding to Ralph about logging. This doesn't
really have much to do with Maven.
On 6/11/11 9:03 AM, "Clark, Gil W." wrote:
>Interesting thread. So we are using Splunk as our log "viewer" and it has
>built in ability to map message ids to the localized strings. But,
Interesting thread. So we are using Splunk as our log "viewer" and it has
built in ability to map message ids to the localized strings. But, it's
expensive for Splunk to do this (both in $ and processing time). So while
its architecturally more pure it requires a good log viewer that everyone
ha
Are there any other log4j-2.0 activities?
If not, then why not move it to the trunk (or an official 2.0 branch)?
I will give it a try.
LieGrue,
strub
--- On Sat, 6/11/11, Ralph Goers wrote:
> From: Ralph Goers
> Subject: Re: Get thee to the Core...
> To: "Maven Developers List"
> Date: Saturd
Well, I make no guarantee that it is done "right". I do guarantee that if you
want to help I'll welcome it.
On Jun 11, 2011, at 12:12 AM, Stephen Connolly wrote:
> I'll take a look... I'm keen to see logging done right
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mist
Yes - I have been working on it. I wouldn't call it close to production ready.
I would call it time for more user involvement. I've been working on it for
almost a year taking everything I've learned from Log4j 1.x, SLF4J/Logback and
a proprietary framework I wrote for my employer. The Logging
I'll take a look... I'm keen to see logging done right
- 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 11 Jun 2011 06:50, "Ralph Goers" wrote:
12 matches
Mail list logo
