Re: colorized Maven output

[Hervé BOUTEMY]

I tried on Windows: it does not work yet

Th eissue I'm facing is: we need to call AnsiConsole.systemInstall() for 
Windows
But if this call is added in MavenCli.doMain(), core ITs fail since there is 
confusion on System.out replacements...

I still didn't find any way to avoid this confusion: if somebody has an 
idea...

Regards,

Hervé

Le lundi 6 juin 2016 16:15:48 Petar Tahchiev a écrit :
> Sorry, I got confused by this: "if run with older Maven, color is always
> on".
> 
> I will try it later.
> 
> 2016-06-06 15:46 GMT+02:00 Tamás Cservenák :
> > I believe you need to build Maven itself from Herve's branch:
> > https://github.com/apache/maven/tree/MNG-3507
> > 
> > On Mon, Jun 6, 2016 at 3:14 PM Petar Tahchiev 
> > 
> > wrote:
> > > I might be doing smth wrong but I tested on windows 10 with Maven 3.3.9
> > 
> > and
> > 
> > > I didn't see any color.  Here's what I did:
> > > 
> > > 1) git clone g...@github.com:apache/maven-shared.git
> > > 2) cd maven-share/ && mvn clean install
> > > 3) git clone g...@github.com:apache/maven-integration-testing.git
> > > 4) cd maven-integration-testing && mvn clean install
> > > 
> > > I also tried to build only that particular module too:
> > > 5) cd maven-integration-testing\core-it-support\maven-it-helper\ && mvn
> > > clean install
> > > 
> > > The result is
> > > 
> > > ---
> > > 
> > >  T E S T S
> > > 
> > > ---
> > > Running org.apache.maven.it.MavenIntegrationTestCaseTest
> > > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.425
> > 
> > sec -
> > 
> > > in org.apache.maven.it.MavenIntegrationTestCaseTest
> > > 
> > > Results :
> > > 
> > > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> > > 
> > > [INFO]
> > > [INFO] --- maven-jar-plugin:2.5:jar (default-jar) @ maven-it-helper ---
> > 
> > > [INFO] Building jar:
> > C:\workspace\maven-integration-testing\core-it-support\maven-it-helper\tar
> > get\maven-it-helper-2.1-SNAPSHOT.jar> 
> > > and no color.
> > > 
> > > 2016-06-06 14:31 GMT+02:00 jieryn :
> > > > Also, to get Jenkins displaying ANSI escape codes for color you can
> > > > install https://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin
> > > > and then enable it per-job.
> > > > 
> > > > On Mon, Jun 6, 2016 at 2:33 AM, Romain Manni-Bucau
> > > > 
> > > >  wrote:
> > > > > Hi Hervé,
> > > > > 
> > > > > would it be possible to enhance this with such features:
> > > > > 
> > > > > 1. make colors configurables through a user config
> > 
> > (~/.m2/settings.xml?
> > 
> > > > or
> > > > 
> > > > > colors.xml)
> > > > > 2. make color config regex friendly. The idea is to be able to get a
> > > > > coloration like https://github.com/rmannibucau/maven-color which
> > > 
> > > depends
> > > 
> > > > > what is shown and not only the level
> > > > > 
> > > > > ?
> > > > > 
> > > > > Anyway thanks for moving forward this feature expected for too long
> > 
> > by
> > 
> > > a
> > > 
> > > > > LOT of users!
> > > > > 
> > > > > Romain Manni-Bucau
> > > > > @rmannibucau  |  Blog
> > > > >  | Github <
> > > > 
> > > > https://github.com/rmannibucau> |
> > > > 
> > > > > LinkedIn  | Tomitriber
> > > > >  | JavaEE Factory
> > > > > 
> > > > > 
> > > > > 2016-06-06 8:26 GMT+02:00 Hervé BOUTEMY :
> > > > >> Hi,
> > > > >> 
> > > > >> As you may have noticed, I created a MNG-3507 branch.
> > > > >> The idea here is to develop colorization not at slf4j
> > > > >> implementation
> > > > 
> > > > level,
> > > > 
> > > > >> but in core (and later plugins): slf4j implementation is only
> > > > 
> > > > responsible
> > > > 
> > > > >> for
> > > > >> DEBUG/INFO/WARNING/ERROR colorization, core and plugins are
> > > 
> > > responsible
> > > 
> > > > for
> > > > 
> > > > >> messages.
> > > > >> 
> > > > >> I implemented message colorization that J Dillon did in
> > 
> > slf4j-gossip:
> > > > the
> > > > 
> > > > >> only
> > > > >> part I still didn't do is the stacktrace enhancement.
> > > > >> Batch mode disables color: we can choose to create specific CLI
> > > 
> > > options
> > > 
> > > > >> later
> > > > >> if we prefer.
> > > > >> And the most important is that core provides jansi to plugins: any
> > > > 
> > > > plugin
> > > > 
> > > > >> using jansi benefits from jansi configuration (mainly
> > > > >> enable/disable
> > > > 
> > > > color)
> > > > 
> > > > >> As a proof of concept, I implemented color output in core ITs
> > 
> > invoker
> > 
> > > > [1]:
> > > > >> if
> > > > >> run with older Maven, color is always on (since core doesn't
> > > > >> provide
> > > > >> configured jansi), but if run with the branch, the plugin has color
> > > > >> deactivated in batch mode.
> > > > >> As you can see, also, Jenkins doesn't display ansi code nicely
> > 
> > [2]...
> 

[VOTE] Release Apache Maven JAR Plugin version 3.0.1

[Karl Heinz Marbaise]

Hi,

We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526&version=12335708

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20XX%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1276/
https://repository.apache.org/content/repositories/maven-1276/org/apache/maven/plugins/maven-jar-plugin/3.0.1/maven-jar-plugin-3.0.1-source-release.zip

Source release checksum(s):
maven-jar-plugin-3.0.1-source-release.zip sha1: 
195a324abe69bae09204bc8fefe11e1e11264155


Staging site:
http://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Resources Plugin version 3.0.1

[Anders Hammar]

+1

/Anders

On Fri, Jun 3, 2016 at 11:36 PM, Karl Heinz Marbaise 
wrote:

> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317827&version=12335752
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOURCES%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1275
>
> https://repository.apache.org/content/repositories/maven-1275/org/apache/maven/plugins/maven-resources-plugin/3.0.1/maven-resources-plugin-3.0.1-source-release.zip
>
> Source release checksum(s):
> maven-resources-plugin-source-release.zip sha1:
> 48cc449b95781beeca2ff278f09f5a2c6e9ad7fd
>
>
> Staging site:
> http://maven.apache.org/plugins-archives/maven-resources-plugin-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

[RESULT] [VOTE] Release Apache Maven Shared Component: Maven Archiver Version 3.1.0

[Karl Heinz Marbaise]

Hi,

The vote has passed with the following result:

+1 : Robert Scholte, Hervé Boutemy, Karl Heinz Marbaise

PMC quorum: reached

I will promote the artifacts to the central repo.

Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT] [VOTE] Release Apache Maven Shared Component: Maven Archiver Version 3.1.0

[Karl Heinz Marbaise]

Hi,

The vote has passed with the following result:

+1 : Hervé Boutemy, Robert Scholte, Karl Heinz Marbaise

PMC quorum: reached.

I will promote the artifacts to the central repo.

Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven-skins pull request #4: Hamburger menu with top-nav only

[mstanleyjones]

Github user mstanleyjones closed the pull request at:

https://github.com/apache/maven-skins/pull/4


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: colorized Maven output

[Hervé BOUTEMY]

great hint: it was already available in ASF Jenkins but I didn't see

I activated it and ran the tests: you can see the miracle result!
https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing-maven-3-embedded/7281/console

(notice that the output colorization is done at plugin level, not from Maven 
core since the build is done from Maven 3.0.x which does not support color)

Regards,

Hervé

Le lundi 6 juin 2016 08:31:17 jieryn a écrit :
> Also, to get Jenkins displaying ANSI escape codes for color you can
> install https://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin
> and then enable it per-job.
> 
> On Mon, Jun 6, 2016 at 2:33 AM, Romain Manni-Bucau
> 
>  wrote:
> > Hi Hervé,
> > 
> > would it be possible to enhance this with such features:
> > 
> > 1. make colors configurables through a user config (~/.m2/settings.xml? or
> > colors.xml)
> > 2. make color config regex friendly. The idea is to be able to get a
> > coloration like https://github.com/rmannibucau/maven-color which depends
> > what is shown and not only the level
> > 
> > ?
> > 
> > Anyway thanks for moving forward this feature expected for too long by a
> > LOT of users!
> > 
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Github
> >  | LinkedIn
> >  | Tomitriber
> >  | JavaEE Factory
> > 
> > 
> > 2016-06-06 8:26 GMT+02:00 Hervé BOUTEMY :
> >> Hi,
> >> 
> >> As you may have noticed, I created a MNG-3507 branch.
> >> The idea here is to develop colorization not at slf4j implementation
> >> level,
> >> but in core (and later plugins): slf4j implementation is only responsible
> >> for
> >> DEBUG/INFO/WARNING/ERROR colorization, core and plugins are responsible
> >> for
> >> messages.
> >> 
> >> I implemented message colorization that J Dillon did in slf4j-gossip: the
> >> only
> >> part I still didn't do is the stacktrace enhancement.
> >> Batch mode disables color: we can choose to create specific CLI options
> >> later
> >> if we prefer.
> >> And the most important is that core provides jansi to plugins: any plugin
> >> using jansi benefits from jansi configuration (mainly enable/disable
> >> color)
> >> 
> >> As a proof of concept, I implemented color output in core ITs invoker
> >> [1]:
> >> if
> >> run with older Maven, color is always on (since core doesn't provide
> >> configured jansi), but if run with the branch, the plugin has color
> >> deactivated in batch mode.
> >> As you can see, also, Jenkins doesn't display ansi code nicely [2]...
> >> 
> >> I also updated some IT test code to strip ansi codes [3] and not choke
> >> with
> >> color on.
> >> 
> >> I still need to test on Windows, if nobody beats me at it.
> >> 
> >> If nobody objects, I'll merge code to master and update slf4j-gossip
> >> accordingly (a lot of features are now in core): the discussion on
> >> changing
> >> default slf4j implementation will happen a little bit later.
> >> 
> >> Regards,
> >> 
> >> Hervé
> >> 
> >> 
> >> [1]
> >> http://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/1
> >> 3bd5416
> >> 
> >> [2]
> >> https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testin
> >> g-maven-3-embedded/7280/console
> >> 
> >> [3] http://svn.apache.org/r1746888
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: colorized Maven output

[Hervé BOUTEMY]

Le lundi 6 juin 2016 08:33:01 Romain Manni-Bucau a écrit :
> Hi Hervé,
> 
> would it be possible to enhance this with such features:
> 
> 1. make colors configurables through a user config (~/.m2/settings.xml? or
> colors.xml)
I would prefer avoiding creating something complex if we can avoid it: are you 
sure this is necessary?

> 2. make color config regex friendly. The idea is to be able to get a
> coloration like https://github.com/rmannibucau/maven-color which depends
> what is shown and not only the level?
no: the idea of MNG-3507 branch is to avoid that

In slf4j-gossip implementation J Dillon did, color is done by post-processing 
logging messages: here, such regex would make sense

But MNG-3507 is about avoiding such logging message post-processing: instead 
Maven core highlights core tracking, and each plugin highlights its own 
messages, directly in the plugin


This is exactly because of that completely different opposite that I wanted to 
share: do you think slf4j implementation-specific post-processing is a better 
alternative than in-plugin color support (coordinated from Maven core)?

> 
> Anyway thanks for moving forward this feature expected for too long by a
> LOT of users!
I really like the output prepared by J Dillon: now I build with it and I want 
to have it integrated!!!

thanks for your feedback: we need it to make a great long-expected feature

Regards,

Hervé

> 
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Github 
> | LinkedIn  | Tomitriber
>  | JavaEE Factory
> 
> 
> 2016-06-06 8:26 GMT+02:00 Hervé BOUTEMY :
> > Hi,
> > 
> > As you may have noticed, I created a MNG-3507 branch.
> > The idea here is to develop colorization not at slf4j implementation
> > level,
> > but in core (and later plugins): slf4j implementation is only responsible
> > for
> > DEBUG/INFO/WARNING/ERROR colorization, core and plugins are responsible
> > for
> > messages.
> > 
> > I implemented message colorization that J Dillon did in slf4j-gossip: the
> > only
> > part I still didn't do is the stacktrace enhancement.
> > Batch mode disables color: we can choose to create specific CLI options
> > later
> > if we prefer.
> > And the most important is that core provides jansi to plugins: any plugin
> > using jansi benefits from jansi configuration (mainly enable/disable
> > color)
> > 
> > As a proof of concept, I implemented color output in core ITs invoker [1]:
> > if
> > run with older Maven, color is always on (since core doesn't provide
> > configured jansi), but if run with the branch, the plugin has color
> > deactivated in batch mode.
> > As you can see, also, Jenkins doesn't display ansi code nicely [2]...
> > 
> > I also updated some IT test code to strip ansi codes [3] and not choke
> > with
> > color on.
> > 
> > I still need to test on Windows, if nobody beats me at it.
> > 
> > If nobody objects, I'll merge code to master and update slf4j-gossip
> > accordingly (a lot of features are now in core): the discussion on
> > changing
> > default slf4j implementation will happen a little bit later.
> > 
> > Regards,
> > 
> > Hervé
> > 
> > 
> > [1]
> > http://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/13
> > bd5416
> > 
> > [2]
> > https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing
> > -maven-3-embedded/7280/console
> > 
> > [3] http://svn.apache.org/r1746888
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

maven-assembly-plugin release?

[Jesse McConnell]

We are looking to get Jetty building with java 9 now and are a touch stuck
with the latest maven-assembly-plugin needing to be released for 3.0.0.  We
notice the issue we need resolved seems to have been fixed up last week and
we are curious if there is a release date targeted?

cheers,
Jesse

--
jesse mcconnell
jesse.mcconn...@gmail.com

Backward compatibility analysis report

[Ponomarenko Andrey]

Hello,

I've prepared backward compatibility/API changes report for the Maven core 
libraries here:

http://abi-laboratory.pro/java/tracker/timeline/maven/

I hope the report will help users, maintainers and developers to maintain 
backward compatibility. The reports are updated daily by the 
japi-compliance-checker and japi-tracker tools: 
https://github.com/lvc/japi-compliance-checker

Please let me know if there are some false positives in the report.

Thank you.

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Commit #2a944f0 causes Continous Integration hang

[frank . jakop]

Hello Surefire developers,

recently we switched from Surefire 2.18.0 to 2.19.1 and since then we
encounter a strange behaviour with our CI infrastructure.

We're running TeamCity build agents on Windows XP and Windows 7 and on the
XP machines the build times increased by factor >25. I've tracked the
commit down which is the first to produce these oddities and it's commit #
2a944f0687ee8 "[SUREFIRE-580] Allow "fail fast" or stop running on first
failure".
Since this is a rather large commit I was not able to understand completely
what was done there, so my question is, what change could be responsible.
As I look at my build agents when they hang I see in the thread dump there
are 2 threads which consume much time, notably doing some xml file parsing
and the other doing java.io.WinNTFileSystem.list.

Perhaps someone, especially Tibor17, could give me a hint what to look for.

Best Regards

Frank Jakop
Teamleiter


arxes-tolina GmbH
Salzufer 8, 10587 Berlin
http://www.arxes-tolina.de

Telefon: +49 (30) 26 47 45 - 141
Telefax: +49 (30) 26 47 45 - 7711
frank.ja...@arxes-tolina.de

Amtsgericht Berlin-Charlottenburg, HRB 84278
Sitz: Berlin, Geschäftsführer: Dr. Peter Heilmann, Norbert Bochynek, Ralf
Berndt

Re: colorized Maven output

[Petar Tahchiev]

Sorry, I got confused by this: "if run with older Maven, color is always
on".

I will try it later.

2016-06-06 15:46 GMT+02:00 Tamás Cservenák :

> I believe you need to build Maven itself from Herve's branch:
> https://github.com/apache/maven/tree/MNG-3507
>
> On Mon, Jun 6, 2016 at 3:14 PM Petar Tahchiev 
> wrote:
>
> > I might be doing smth wrong but I tested on windows 10 with Maven 3.3.9
> and
> > I didn't see any color.  Here's what I did:
> >
> > 1) git clone g...@github.com:apache/maven-shared.git
> > 2) cd maven-share/ && mvn clean install
> > 3) git clone g...@github.com:apache/maven-integration-testing.git
> > 4) cd maven-integration-testing && mvn clean install
> >
> > I also tried to build only that particular module too:
> > 5) cd maven-integration-testing\core-it-support\maven-it-helper\ && mvn
> > clean install
> >
> > The result is
> >
> > ---
> >  T E S T S
> > ---
> > Running org.apache.maven.it.MavenIntegrationTestCaseTest
> > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.425
> sec -
> > in org.apache.maven.it.MavenIntegrationTestCaseTest
> >
> > Results :
> >
> > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> >
> > [INFO]
> > [INFO] --- maven-jar-plugin:2.5:jar (default-jar) @ maven-it-helper ---
> > [INFO] Building jar:
> >
> >
> C:\workspace\maven-integration-testing\core-it-support\maven-it-helper\target\maven-it-helper-2.1-SNAPSHOT.jar
> >
> > and no color.
> >
> > 2016-06-06 14:31 GMT+02:00 jieryn :
> >
> > > Also, to get Jenkins displaying ANSI escape codes for color you can
> > > install https://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin
> > > and then enable it per-job.
> > >
> > > On Mon, Jun 6, 2016 at 2:33 AM, Romain Manni-Bucau
> > >  wrote:
> > > > Hi Hervé,
> > > >
> > > > would it be possible to enhance this with such features:
> > > >
> > > > 1. make colors configurables through a user config
> (~/.m2/settings.xml?
> > > or
> > > > colors.xml)
> > > > 2. make color config regex friendly. The idea is to be able to get a
> > > > coloration like https://github.com/rmannibucau/maven-color which
> > depends
> > > > what is shown and not only the level
> > > >
> > > > ?
> > > >
> > > > Anyway thanks for moving forward this feature expected for too long
> by
> > a
> > > > LOT of users!
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau  |  Blog
> > > >  | Github <
> > > https://github.com/rmannibucau> |
> > > > LinkedIn  | Tomitriber
> > > >  | JavaEE Factory
> > > > 
> > > >
> > > > 2016-06-06 8:26 GMT+02:00 Hervé BOUTEMY :
> > > >
> > > >> Hi,
> > > >>
> > > >> As you may have noticed, I created a MNG-3507 branch.
> > > >> The idea here is to develop colorization not at slf4j implementation
> > > level,
> > > >> but in core (and later plugins): slf4j implementation is only
> > > responsible
> > > >> for
> > > >> DEBUG/INFO/WARNING/ERROR colorization, core and plugins are
> > responsible
> > > for
> > > >> messages.
> > > >>
> > > >> I implemented message colorization that J Dillon did in
> slf4j-gossip:
> > > the
> > > >> only
> > > >> part I still didn't do is the stacktrace enhancement.
> > > >> Batch mode disables color: we can choose to create specific CLI
> > options
> > > >> later
> > > >> if we prefer.
> > > >> And the most important is that core provides jansi to plugins: any
> > > plugin
> > > >> using jansi benefits from jansi configuration (mainly enable/disable
> > > color)
> > > >>
> > > >> As a proof of concept, I implemented color output in core ITs
> invoker
> > > [1]:
> > > >> if
> > > >> run with older Maven, color is always on (since core doesn't provide
> > > >> configured jansi), but if run with the branch, the plugin has color
> > > >> deactivated in batch mode.
> > > >> As you can see, also, Jenkins doesn't display ansi code nicely
> [2]...
> > > >>
> > > >> I also updated some IT test code to strip ansi codes [3] and not
> choke
> > > with
> > > >> color on.
> > > >>
> > > >> I still need to test on Windows, if nobody beats me at it.
> > > >>
> > > >> If nobody objects, I'll merge code to master and update slf4j-gossip
> > > >> accordingly (a lot of features are now in core): the discussion on
> > > changing
> > > >> default slf4j implementation will happen a little bit later.
> > > >>
> > > >> Regards,
> > > >>
> > > >> Hervé
> > > >>
> > > >>
> > > >> [1]
> > > >>
> > >
> >
> http://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/13bd5416
> > > >>
> > > >> [2]
> > > >>
> > >
> >
> https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing-maven-3-embedded/7280/console
> > > >>
> > > >> [3] http://svn.apache.org/r1746888
> > > >>
> > > >>
> ---

Re: colorized Maven output

[Tamás Cservenák]

I believe you need to build Maven itself from Herve's branch:
https://github.com/apache/maven/tree/MNG-3507

On Mon, Jun 6, 2016 at 3:14 PM Petar Tahchiev  wrote:

> I might be doing smth wrong but I tested on windows 10 with Maven 3.3.9 and
> I didn't see any color.  Here's what I did:
>
> 1) git clone g...@github.com:apache/maven-shared.git
> 2) cd maven-share/ && mvn clean install
> 3) git clone g...@github.com:apache/maven-integration-testing.git
> 4) cd maven-integration-testing && mvn clean install
>
> I also tried to build only that particular module too:
> 5) cd maven-integration-testing\core-it-support\maven-it-helper\ && mvn
> clean install
>
> The result is
>
> ---
>  T E S T S
> ---
> Running org.apache.maven.it.MavenIntegrationTestCaseTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.425 sec -
> in org.apache.maven.it.MavenIntegrationTestCaseTest
>
> Results :
>
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
>
> [INFO]
> [INFO] --- maven-jar-plugin:2.5:jar (default-jar) @ maven-it-helper ---
> [INFO] Building jar:
>
> C:\workspace\maven-integration-testing\core-it-support\maven-it-helper\target\maven-it-helper-2.1-SNAPSHOT.jar
>
> and no color.
>
> 2016-06-06 14:31 GMT+02:00 jieryn :
>
> > Also, to get Jenkins displaying ANSI escape codes for color you can
> > install https://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin
> > and then enable it per-job.
> >
> > On Mon, Jun 6, 2016 at 2:33 AM, Romain Manni-Bucau
> >  wrote:
> > > Hi Hervé,
> > >
> > > would it be possible to enhance this with such features:
> > >
> > > 1. make colors configurables through a user config (~/.m2/settings.xml?
> > or
> > > colors.xml)
> > > 2. make color config regex friendly. The idea is to be able to get a
> > > coloration like https://github.com/rmannibucau/maven-color which
> depends
> > > what is shown and not only the level
> > >
> > > ?
> > >
> > > Anyway thanks for moving forward this feature expected for too long by
> a
> > > LOT of users!
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Github <
> > https://github.com/rmannibucau> |
> > > LinkedIn  | Tomitriber
> > >  | JavaEE Factory
> > > 
> > >
> > > 2016-06-06 8:26 GMT+02:00 Hervé BOUTEMY :
> > >
> > >> Hi,
> > >>
> > >> As you may have noticed, I created a MNG-3507 branch.
> > >> The idea here is to develop colorization not at slf4j implementation
> > level,
> > >> but in core (and later plugins): slf4j implementation is only
> > responsible
> > >> for
> > >> DEBUG/INFO/WARNING/ERROR colorization, core and plugins are
> responsible
> > for
> > >> messages.
> > >>
> > >> I implemented message colorization that J Dillon did in slf4j-gossip:
> > the
> > >> only
> > >> part I still didn't do is the stacktrace enhancement.
> > >> Batch mode disables color: we can choose to create specific CLI
> options
> > >> later
> > >> if we prefer.
> > >> And the most important is that core provides jansi to plugins: any
> > plugin
> > >> using jansi benefits from jansi configuration (mainly enable/disable
> > color)
> > >>
> > >> As a proof of concept, I implemented color output in core ITs invoker
> > [1]:
> > >> if
> > >> run with older Maven, color is always on (since core doesn't provide
> > >> configured jansi), but if run with the branch, the plugin has color
> > >> deactivated in batch mode.
> > >> As you can see, also, Jenkins doesn't display ansi code nicely [2]...
> > >>
> > >> I also updated some IT test code to strip ansi codes [3] and not choke
> > with
> > >> color on.
> > >>
> > >> I still need to test on Windows, if nobody beats me at it.
> > >>
> > >> If nobody objects, I'll merge code to master and update slf4j-gossip
> > >> accordingly (a lot of features are now in core): the discussion on
> > changing
> > >> default slf4j implementation will happen a little bit later.
> > >>
> > >> Regards,
> > >>
> > >> Hervé
> > >>
> > >>
> > >> [1]
> > >>
> >
> http://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/13bd5416
> > >>
> > >> [2]
> > >>
> >
> https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing-maven-3-embedded/7280/console
> > >>
> > >> [3] http://svn.apache.org/r1746888
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > >> For additional commands, e-mail: dev-h...@maven.apache.org
> > >>
> > >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
>
> --
> Regards, Petar!
> Karlovo, Bulgaria.
> ---
> Public PGP Key at:
> htt

Re: colorized Maven output

[Petar Tahchiev]

I might be doing smth wrong but I tested on windows 10 with Maven 3.3.9 and
I didn't see any color.  Here's what I did:

1) git clone g...@github.com:apache/maven-shared.git
2) cd maven-share/ && mvn clean install
3) git clone g...@github.com:apache/maven-integration-testing.git
4) cd maven-integration-testing && mvn clean install

I also tried to build only that particular module too:
5) cd maven-integration-testing\core-it-support\maven-it-helper\ && mvn
clean install

The result is

---
 T E S T S
---
Running org.apache.maven.it.MavenIntegrationTestCaseTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.425 sec -
in org.apache.maven.it.MavenIntegrationTestCaseTest

Results :

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0

[INFO]
[INFO] --- maven-jar-plugin:2.5:jar (default-jar) @ maven-it-helper ---
[INFO] Building jar:
C:\workspace\maven-integration-testing\core-it-support\maven-it-helper\target\maven-it-helper-2.1-SNAPSHOT.jar

and no color.

2016-06-06 14:31 GMT+02:00 jieryn :

> Also, to get Jenkins displaying ANSI escape codes for color you can
> install https://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin
> and then enable it per-job.
>
> On Mon, Jun 6, 2016 at 2:33 AM, Romain Manni-Bucau
>  wrote:
> > Hi Hervé,
> >
> > would it be possible to enhance this with such features:
> >
> > 1. make colors configurables through a user config (~/.m2/settings.xml?
> or
> > colors.xml)
> > 2. make color config regex friendly. The idea is to be able to get a
> > coloration like https://github.com/rmannibucau/maven-color which depends
> > what is shown and not only the level
> >
> > ?
> >
> > Anyway thanks for moving forward this feature expected for too long by a
> > LOT of users!
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Github <
> https://github.com/rmannibucau> |
> > LinkedIn  | Tomitriber
> >  | JavaEE Factory
> > 
> >
> > 2016-06-06 8:26 GMT+02:00 Hervé BOUTEMY :
> >
> >> Hi,
> >>
> >> As you may have noticed, I created a MNG-3507 branch.
> >> The idea here is to develop colorization not at slf4j implementation
> level,
> >> but in core (and later plugins): slf4j implementation is only
> responsible
> >> for
> >> DEBUG/INFO/WARNING/ERROR colorization, core and plugins are responsible
> for
> >> messages.
> >>
> >> I implemented message colorization that J Dillon did in slf4j-gossip:
> the
> >> only
> >> part I still didn't do is the stacktrace enhancement.
> >> Batch mode disables color: we can choose to create specific CLI options
> >> later
> >> if we prefer.
> >> And the most important is that core provides jansi to plugins: any
> plugin
> >> using jansi benefits from jansi configuration (mainly enable/disable
> color)
> >>
> >> As a proof of concept, I implemented color output in core ITs invoker
> [1]:
> >> if
> >> run with older Maven, color is always on (since core doesn't provide
> >> configured jansi), but if run with the branch, the plugin has color
> >> deactivated in batch mode.
> >> As you can see, also, Jenkins doesn't display ansi code nicely [2]...
> >>
> >> I also updated some IT test code to strip ansi codes [3] and not choke
> with
> >> color on.
> >>
> >> I still need to test on Windows, if nobody beats me at it.
> >>
> >> If nobody objects, I'll merge code to master and update slf4j-gossip
> >> accordingly (a lot of features are now in core): the discussion on
> changing
> >> default slf4j implementation will happen a little bit later.
> >>
> >> Regards,
> >>
> >> Hervé
> >>
> >>
> >> [1]
> >>
> http://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/13bd5416
> >>
> >> [2]
> >>
> https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing-maven-3-embedded/7280/console
> >>
> >> [3] http://svn.apache.org/r1746888
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF  55A5 1965 8550 C311 0611

Re: colorized Maven output

[jieryn]

Also, to get Jenkins displaying ANSI escape codes for color you can
install https://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin
and then enable it per-job.

On Mon, Jun 6, 2016 at 2:33 AM, Romain Manni-Bucau
 wrote:
> Hi Hervé,
>
> would it be possible to enhance this with such features:
>
> 1. make colors configurables through a user config (~/.m2/settings.xml? or
> colors.xml)
> 2. make color config regex friendly. The idea is to be able to get a
> coloration like https://github.com/rmannibucau/maven-color which depends
> what is shown and not only the level
>
> ?
>
> Anyway thanks for moving forward this feature expected for too long by a
> LOT of users!
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Github  |
> LinkedIn  | Tomitriber
>  | JavaEE Factory
> 
>
> 2016-06-06 8:26 GMT+02:00 Hervé BOUTEMY :
>
>> Hi,
>>
>> As you may have noticed, I created a MNG-3507 branch.
>> The idea here is to develop colorization not at slf4j implementation level,
>> but in core (and later plugins): slf4j implementation is only responsible
>> for
>> DEBUG/INFO/WARNING/ERROR colorization, core and plugins are responsible for
>> messages.
>>
>> I implemented message colorization that J Dillon did in slf4j-gossip: the
>> only
>> part I still didn't do is the stacktrace enhancement.
>> Batch mode disables color: we can choose to create specific CLI options
>> later
>> if we prefer.
>> And the most important is that core provides jansi to plugins: any plugin
>> using jansi benefits from jansi configuration (mainly enable/disable color)
>>
>> As a proof of concept, I implemented color output in core ITs invoker [1]:
>> if
>> run with older Maven, color is always on (since core doesn't provide
>> configured jansi), but if run with the branch, the plugin has color
>> deactivated in batch mode.
>> As you can see, also, Jenkins doesn't display ansi code nicely [2]...
>>
>> I also updated some IT test code to strip ansi codes [3] and not choke with
>> color on.
>>
>> I still need to test on Windows, if nobody beats me at it.
>>
>> If nobody objects, I'll merge code to master and update slf4j-gossip
>> accordingly (a lot of features are now in core): the discussion on changing
>> default slf4j implementation will happen a little bit later.
>>
>> Regards,
>>
>> Hervé
>>
>>
>> [1]
>> http://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/13bd5416
>>
>> [2]
>> https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing-maven-3-embedded/7280/console
>>
>> [3] http://svn.apache.org/r1746888
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org