Hi,
I sorted out the ITs running in embedded mode and here's what I came up with.
I patched SLF4J Simple to work around some static initialization that locked in
the log level and the output stream. So the problem in the ITs is not that the
output doesn't arrive in the individual files for each
Arnaud,
It's all in there now. While I was fixing the logging in embedded mode for
SLF4J Simple, I updated the Logback branch to do the same.
I had to patch SLF4J Simple to get around some static initialization that
doesn't work in embedded mode so I haven't updated trunk, but the Logback
bran
GitHub user agudian opened a pull request:
https://github.com/apache/maven-surefire/pull/13
[SUREFIRE-839] Tests not matching categories would fail build
Fixed in a way that does not break forkMode=onceperthread (enhanced the IT
for that). Tests are now filtered right before handing
Github user agudian closed the pull request at:
https://github.com/apache/maven-surefire/pull/12
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
GitHub user agudian opened a pull request:
https://github.com/apache/maven-surefire/pull/12
[SUREFIRE-839] Tests not matching categories would fail build
Fixed in a way that does not break forkMode=onceperthread (enhanced the IT
for that), refined the logic of JUnitCoreProvider.canR
Nothing has been released yet. This is what this cycle is for and frankly after
11 months of not releasing while adding JSR330 and SLF4J it's to be expected.
But Hervé is working on it and I'm fixing up the error Kristian verified so
it's getting review and if it takes 5 more re-spins so be it.
On Dec 8, 2012, at 9:22 AM, Hervé BOUTEMY wrote:
> Le vendredi 7 décembre 2012 09:32:33 Jason van Zyl a écrit :
>> Hervé I will assume you're looking at this. Let me know if you need any
>> help.
>
> yes, I'm working on it
> from latest discussion, the ideal is:
>
> 1. compatibility:
> for plu
+1, that sounds like a good balance between old compat behaviour and moving
forward!
> Strategies to write a plugin using slf4j-api from core without requiring
> Maven
> 3.1 still need to be found:
Maybe that's easier than you think.
Just declare an slf4j-api dependency to the plugin. If the
Le vendredi 7 décembre 2012 09:32:33 Jason van Zyl a écrit :
> Hervé I will assume you're looking at this. Let me know if you need any
> help.
yes, I'm working on it
from latest discussion, the ideal is:
1. compatibility:
for plugin descriptors without information, don't expose core's slf4j-api,
Lol.
I think it will be really safer to have it off by default in 3.2 and
we might change it in another version depending of the community
feedback.
But for all if that it won't be before 2013.
-
Arnaud
Le 8 déc. 2012 à 13:24, Kristian Rosenvold
a écrit :
> I fear meeting the millitant
I fear meeting the millitant arch-Linux users running in strict C64
emulation. Maybe just enable colour by defalt for all fruity
computers ?
K
Den 8. des. 2012 kl. 13:10 skrev "Arnaud Héritier" :
> And windows which has a support near to the Amiga ;)
>
> -
> Arnaud
>
> Le 8 déc. 2012 à
And windows which has a support near to the Amiga ;)
-
Arnaud
Le 8 déc. 2012 à 12:55, Kristian Rosenvold
a écrit :
> Disable color by default in batch mode then. I suppose we could detect
> is users are running AmigaOS or aix and disable by default there too.
>
> Kristian
>
> Den 8. des
In jenkins you have a Jansi plugin that interprets ANSI codes and
create colors in output. I'm using it and it is working fine.
For maven there was a customizable step to create colors in the
console. We'll need to find a solution to not have a conflict.
-
Arnaud
Le 8 déc. 2012 à 12:34,
Disable color by default in batch mode then. I suppose we could detect
is users are running AmigaOS or aix and disable by default there too.
Kristian
Den 8. des. 2012 kl. 12:34 skrev Chris Graham :
> AIX still does not do well with ANSI style colour.
>
> And I wonder how Jenkins would cope parsi
AIX still does not do well with ANSI style colour.
And I wonder how Jenkins would cope parsing the output.
Seriously 2013 soon or not, don't break the output and introduce crap into the
output stream.
Sent from my iPhone
On 08/12/2012, at 10:14 PM, Kristian Rosenvold
wrote:
> Seriously this
Seriously this sounds like something you'd want to configure i.
MAVEN_OPTS, so I'd be inclined to do color by default in 2012, soon
2013.
K
Den 8. des. 2012 kl. 11:14 skrev Chris Graham :
> Which is what I thought.
>
> +1 to off by default then.
>
> Sent from my iPhone
>
> On 08/12/2012, at 9:11
Which is what I thought.
+1 to off by default then.
Sent from my iPhone
On 08/12/2012, at 9:11 PM, Arnaud Héritier wrote:
> http://en.m.wikipedia.org/wiki/ANSI_escape_code
>
> It adds some extras character that you'll see if the console doesn't
> support it
>
> -
> Arnaud
>
> Le 8 d
http://en.m.wikipedia.org/wiki/ANSI_escape_code
It adds some extras character that you'll see if the console doesn't
support it
-
Arnaud
Le 8 déc. 2012 à 11:03, Chris Graham a écrit :
I'd like to know how it is implemented and what happens when it is run on a
terminal that does not sup
I'd like to know how it is implemented and what happens when it is run on a
terminal that does not support it.
-Chris
Sent from my iPhone
On 08/12/2012, at 8:54 AM, Stephen Connolly
wrote:
> +1 from me
>
> On Friday, 7 December 2012, Jesse McConnell wrote:
>
>> I sure hope colored logging
19 matches
Mail list logo
