date:20170412

[ANN] Apache Maven Surefire Plugin 2.20 Released

2017-04-12 Thread Tibor Digana

The Apache Maven team is pleased to announce the release of the Apache
Maven Surefire Plugin, version 2.20.

The release contains 70 bug fixes.
Again we received contributions from the community in form of bug reports
and bug fixes.
Thank you and keep them coming!

http://maven.apache.org/plugins/maven-surefire-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-surefire-plugin
  2.20


or for failsafe:


  org.apache.maven.plugins
  maven-failsafe-plugin
  2.20


or for surefire-report:

  org.apache.maven.plugins
  maven-surefire-report-plugin
  2.20


Release Notes - Maven Surefire - Version 2.20

Bug

   - [SUREFIRE-725 ] -
   Test result output ist sent to System.out instead of using logger
   - [SUREFIRE-1198 ]
   - Failsafe does not allow to configure the jar file to use
   - [SUREFIRE-1216 ]
   - TEST-*.xml files generated by Surefire are invalid
   - [SUREFIRE-1217 ]
   - Differentiate XML schema for failsafe and surefire
   - [SUREFIRE-1239 ]
   - ExecutionException java.lang.RuntimeException:
   org.apache.maven.surefire.report.ReporterException: When writing xml report
   stdout/stderr (No such file or directory)
   - [SUREFIRE-1244 ]
   - NumberFormatException in parallel test run with runOrder = failedFirst
   - [SUREFIRE-1250 ]
   - Regex testcase filtering: exception when hashmark is regex-quoted
   - [SUREFIRE-1252 ]
   - Tests not being run when using XML suite file with TestNG
   - [SUREFIRE-1268 ]
   - With JUnit listener, redirectTestOutputToFile is ignored
   - [SUREFIRE-1278 ]
   - TestNG tests are run with group name that ends with specified group
   - [SUREFIRE-1284 ]
   - Statistics file should not be determined as (directory of
   surefire-reports).getParentFile().getParentFile(). It is a problem if
   report directory is customized. Statistics file should be located in
   project dir.
   - [SUREFIRE-1289 ]
   - forkedProcessTimeoutInSeconds should not use ping timer of 10 seconds but
   0.1 sec period timer
   - [SUREFIRE-1290 ]
   - Orphan Fork JVMs should be killed after any previous finished with fatal
   error
   - [SUREFIRE-1295 ]
   - JVM crashes in forks do not log the name of the failing test
   - [SUREFIRE-1296 ]
   - The project build directory should not be determined as (directory of
   surefire-reports).getParentFile(). It is a problem if report directory is
   customized.
   - [SUREFIRE-1305 ]
   - surefire fails on parallel tests when newline character is in test
   description
   - [SUREFIRE-1312 ]
   - Classpath containing url special characters with Reflections not working
   - [SUREFIRE-1313 ]
   - Unify console report result in SurefirePlugin and VerifyMojo
   - [SUREFIRE-1315 ]
   - Fix stylistic errors in DefaultReporterFactory
   - [SUREFIRE-1322 ]
   - Surefire and Failsafe should dump critical errors in dump file and console
   - [SUREFIRE-1324 ]
   - Surefire incorrectly suppresses exceptions when closing resources.
   - [SUREFIRE-1333 ]
   - Process pending events from forked process after exited and then finish
   forked Thread.
   - [SUREFIRE-1341 ]
   - Documentation of configuration parameters in Failsafe should mention IT
   instead or Test.java
   - [SUREFIRE-1342 ]
   - Acknowledge normal exit of JVM and drain shared memory between processes
   - [SUREFIRE-1349 ]
   - FreeBSD cross process communication needs to commit stdout data in forked
   JVM within a synchronized block
   - [SUREFIRE-1352 ]
   - Dump file [date]-jvmRun[N] where N should be real fork number
   - [SUREFIRE-1354

Re: [EXTERNAL] Re: Any way to change the color scheme in Maven 3.5.0?

2017-04-12 Thread Hervé BOUTEMY

looks natural

any taker for Jira issue and/or PR?

Regards,

Hervé

Le mercredi 12 avril 2017, 12:26:07 CEST Justin Georgeson a écrit :
> I vote for a help plugin goal, like help:color-style. It could show a brief
> summary and how to customize, list available settings, and print active
> settings.
> 
> -Original Message-
> From: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
> Sent: Tuesday, April 11, 2017 8:10 PM
> To: Maven Users List 
> Subject: [EXTERNAL] Re: Any way to change the color scheme in Maven 3.5.0?
> 
> External Sender: Use caution with links/attachments.
> 
> 
> 
> the big question for me is: how to make that list available? A new CLI
> option? A new goal in a plugin? which one? help? other ideas?
> 
> Once we know where to put the feature, the content can be reworked adapted
> to the context
> 
> Regards,
> 
> Hervé
> 
> Le mardi 11 avril 2017, 21:35:19 CEST Robert Scholte a écrit :
> > I still wonder if we want to have this.
> > It is less interesting which colors are used, but instead more
> > interesting the colors you want.
> > So having a list with the available options would be good enough for me.
> > 
> > Robert
> > 
> > On Tue, 11 Apr 2017 00:42:15 +0200, Hervé BOUTEMY
> >  > ree.fr=DwIFAw=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3
> > PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=2L1RhrmrIqeZgpxGINVHucet-6gs3s
> > qlQV0EAtYNCEw=nYBx902DpsALmMqWPOBqbilCAvKsThvCi1wMNZvOomE= >
> > 
> > wrote:
> > > there is no feature now to dump effective config as text: didn't
> > > think at this scenario
> > > 
> > > PRs welcome or at least ideas on where to add this feature to make
> > > it usable
> > > 
> > > Regards,
> > > 
> > > Hervé
> > > 
> > > Le lundi 10 avril 2017, 07:35:49 CEST Francesco ChicchiriccÃ² a écrit :
> > >> On 2017-04-10 09:16 (+0200), Karl Heinz Marbaise
> > >> 
> > >> 
> > >> wrote:
> > >> > Hi,
> > >> > 
> > >> > On 10/04/17 09:11, Francesco Chicchiriccï¿½ wrote:
> > >> > > On 2017-04-10 08:58 (+0200), Karl Heinz Marbaise
> > >> > > 
> > > 
> > > wrote:
> > >> > >> Hi,
> > >> > >> 
> > >> > >> On 10/04/17 08:45, Francesco ChicchiriccÃ² wrote:
> > >> > >>> Thanks HervÃ©,
> > >> > >>> appending
> > >> > >>> 
> > >> > >>> -Dstyle.success=green
> > >> > >>> 
> > >> > >>> to my MAVEN_OPTS did the trick.
> > >> > >>> 
> > >> > >>> Is there any place where defaults for all styles (debug,
> > >> > >>> info, warning, error, success, warning, failure, strong, mojo
> > >> > >>> and
> > >> 
> > >> project)
> > >> 
> > >> > >>> are reported? Thanks!> >>
> > >> > >> 
> > >> > >> Yes if you do a mvn -X clean:
> > >> > >> ...
> > >> > >> 
> > >> > >> [DEBUG]   Imported: org.slf4j.helpers.*
> > >> > >>  > >> > >> d=DwIFAw=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBh
> > >> > >> AqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=2L1RhrmrIqeZgpxGINVHucet-6gs3
> > >> > >> sqlQV0EAtYNCEw=_9tu6Cs8fwmFyem4zc2ihzD2rL1RHVNlTeWNS5-acLc= >
> > >> > >> >> > >> [DEBUG]   Imported: org.slf4j.spi.*
> > >> > >>  > >> > >> d=DwIFAw=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBh
> > >> > >> AqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=2L1RhrmrIqeZgpxGINVHucet-6gs3
> > >> > >> sqlQV0EAtYNCEw=_9tu6Cs8fwmFyem4zc2ihzD2rL1RHVNlTeWNS5-acLc= >
> > >> > >> >> > >> [DEBUG] Populating class realm maven.api [INFO] Error
> > >> > >> stacktraces are turned on.
> > >> > >> [DEBUG] Message scheme: color
> > >> > >> [DEBUG] Message styles: debug info warning error success
> > >> > >> failure
> > >> 
> > >> strong
> > >> 
> > >> > >> mojo project
> > >> > >> [DEBUG] Reading global settings from
> > >> 
> > >> /usr/local/maven/conf/settings.xml
> > >> 
> > >> > >> [DEBUG] Reading user settings from
> > >> > >> /Users/kama/.m2/settings.xml [DEBUG] Reading global toolchains
> > >> > >> from /usr/local/maven/conf/toolchains.xml
> > >> > >> [DEBUG] Reading user toolchains from
> > >> > >> /Users/kama/.m2/toolchains.xml
> > >> > > 
> > >> > > Sorry, I don't get it: where do I see, i.e., that
> > >> > > https://urldefense.proofpoint.com/v2/url?u=http-3A__style.info;
> > >> > > d=DwIFAw=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3
> > >> > > PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=2L1RhrmrIqeZgpxGINVHuce
> > >> > > t-6gs3sqlQV0EAtYNCEw=qxOWjrA4IAwf-c9x4Tj4feaA6XHKd--2MpsU3ZaF
> > >> > > Tas=  is
> > >> 
> > >> blue by
> > >> 
> > >> > > default?>
> > >> > 
> > >> > The following line is colored by the appropriate colors which are
> > >> > used...you should not do a redirect into a pipe via less/more etc..
> > >> > 
> > >> > >> [DEBUG] Message styles: debug info warning error success
> > >> > >> failure
> > >> 
> > >> strong
> > >> 
> > >> I see:
> > >> 
> > >> https://urldefense.proofpoint.com/v2/url?u=http-3A__pasteboard.co_2
> > >>

Stale wiki link question [was: Re: dependency question]

2017-04-12 Thread Robert Kielty

Hi,

I was interested in the below thread wrt to the deprecation of LATEST , RELEASE 
etc.

There is a ref http://docs.codehaus.org/display/MAVEN/Versioning on 
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-VersionComparison

I registered myself on the wiki and did a bit of digging and found the 
following page  https://cwiki.apache.org/confluence/display/MAVENOLD/Versioning

Would it be correct and or useful to update the above codehaus ref on 
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-VersionComparison
 to point to https://cwiki.apache.org/confluence/display/MAVENOLD/Versioning ?

Kind regards,
Robert Kielty
-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
Sent: 11 April 2017 22:57
To: Maven Users List
Subject: Re: dependency question

Hi,


On 11/04/17 23:38, Stephen Connolly wrote:
> On Tue 11 Apr 2017 at 20:55, Curtis Rueden  wrote:
>
>> Hi Stephen,
>>
 There is a special version keyword LATEST which means the very
 newest version, snapshot or otherwise. And RELEASE means the newest
 release
 (non-SNAPSHOT) version.
>>>
>>> Support for those were dropped in Maven 3
>>
>> By "support" do you mean "social support" as opposed to technical
>> functionality?
>
>
> They were supposed to be removed.
>
> If they are working now, that's a bug

Unfortunately they are working ;-(..

https://issues.apache.org/jira/browse/MNG-6206

Kind regards
Karl Heinz Marbaise

>
>
>>
>> Because they are still present in the codebase, and they still work
>> technically:
>>https://github.com/apache/maven/blob/master/maven-
>> resolver-provider/src/main/java/org/apache/maven/repository/internal/
>> DefaultVersionResolver.java#L188-L197
>>
>> Regards,
>> Curtis
>>
>> --
>> Curtis Rueden
>> LOCI software architect - https://loci.wisc.edu/software
>> ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden
>>
>>
>> On Tue, Apr 11, 2017 at 2:44 PM, Stephen Connolly <
>> stephen.alan.conno...@gmail.com> wrote:
>>
>>> On Tue 11 Apr 2017 at 16:02, Curtis Rueden  wrote:
>>>
 Hi Hector,

> This is fine as long as the dependency is always set to
>> x.y.z-Snapshot
> and the dependency is always overwritten this way.  What if the
> producer produces x.y.z.1-Snapshot, x.y.z.2-Snapshot,
>> x.y.z.3-Snapshot
> and I want the dependent build to always get the latest in this
> case, x.y.z.3-Snapshot ?

 There is a special version keyword LATEST which means the very
 newest version, snapshot or otherwise. And RELEASE means the newest
 release
 (non-SNAPSHOT) version.
>>>
>>>
>>> Support for those were dropped in Maven 3
>>>
>>> *and* anyway they were only for *plugin* versions because the plugin
>>> version does not support ranges.
>>>
>>> For dependency versions, define a range
>>>


 Similar to version ranges, Maven will have to ask the remote
 repository about the latest known version in these cases, and will then 
 use that.

 I want to emphasize, as others have mentioned, that using any of
 these strategies will result in _irreproducible builds_. That is,
 your code
>>> might
 build today, and then the same code will fail to build in the
 future, because the versions will resolve differently. The only way
 (I know of)
>>> to
 achieve reproducible builds is to use fixed release versions, always.

 Regards,
 Curtis

 --
 Curtis Rueden
 LOCI software architect - https://loci.wisc.edu/software
 ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden


 On Tue, Apr 11, 2017 at 9:57 AM, Magnanao, Hector <
>>> hector.magna...@sap.com
>
 wrote:

> This is fine as long as the dependency is always set to
>> x.y.z-Snapshot
 and
> the dependency is always overwritten this way.  What if the
> producer produces x.y.z.1-Snapshot, x.y.z.2-Snapshot,
> x.y.z.3-Snapshot and I
>>> want
> the dependent build to always get the latest in this case,
> x.y.z.3-Snapshot ? The difference with this scenario is that the
>>> producer
> will always have a new build number.
> As for your solution of using the range,  do I always have to
> change
>>> the
> pom file in the dependent build whenever a new build is produced
> by
>> the
> producer ?
>
> -Original Message-
> From: Benson Margulies [mailto:bimargul...@gmail.com]
> Sent: Monday, April 10, 2017 10:39 AM
> To: Maven Users List 
> Subject: Re: dependency question
>
> On Mon, Apr 10, 2017 at 8:18 AM, Magnanao, Hector
>  wrote:
>> I'm still a little confused about the answers I'm getting.  So,
>> if
 build
> A is being updated with a new build number(even for a snapshot),
> and

RE: [EXTERNAL] Re: Any way to change the color scheme in Maven 3.5.0?

2017-04-12 Thread Justin Georgeson

I vote for a help plugin goal, like help:color-style. It could show a brief 
summary and how to customize, list available settings, and print active 
settings.

-Original Message-
From: Hervé BOUTEMY [mailto:herve.bout...@free.fr] 
Sent: Tuesday, April 11, 2017 8:10 PM
To: Maven Users List 
Subject: [EXTERNAL] Re: Any way to change the color scheme in Maven 3.5.0?

External Sender: Use caution with links/attachments.



the big question for me is: how to make that list available? A new CLI option?
A new goal in a plugin? which one? help? other ideas?

Once we know where to put the feature, the content can be reworked adapted to 
the context

Regards,

Hervé

Le mardi 11 avril 2017, 21:35:19 CEST Robert Scholte a écrit :
> I still wonder if we want to have this.
> It is less interesting which colors are used, but instead more 
> interesting the colors you want.
> So having a list with the available options would be good enough for me.
>
> Robert
>
> On Tue, 11 Apr 2017 00:42:15 +0200, Hervé BOUTEMY 
>  ree.fr=DwIFAw=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3
> PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=2L1RhrmrIqeZgpxGINVHucet-6gs3s
> qlQV0EAtYNCEw=nYBx902DpsALmMqWPOBqbilCAvKsThvCi1wMNZvOomE= >
>
> wrote:
> > there is no feature now to dump effective config as text: didn't 
> > think at this scenario
> >
> > PRs welcome or at least ideas on where to add this feature to make 
> > it usable
> >
> > Regards,
> >
> > Hervé
> >
> > Le lundi 10 avril 2017, 07:35:49 CEST Francesco ChicchiriccÃ² a écrit :
> >> On 2017-04-10 09:16 (+0200), Karl Heinz Marbaise 
> >> 
> >>
> >> wrote:
> >> > Hi,
> >> >
> >> > On 10/04/17 09:11, Francesco Chicchiriccï¿½ wrote:
> >> > > On 2017-04-10 08:58 (+0200), Karl Heinz Marbaise 
> >> > > 
> >
> > wrote:
> >> > >> Hi,
> >> > >>
> >> > >> On 10/04/17 08:45, Francesco ChicchiriccÃ² wrote:
> >> > >>> Thanks HervÃ©,
> >> > >>> appending
> >> > >>>
> >> > >>> -Dstyle.success=green
> >> > >>>
> >> > >>> to my MAVEN_OPTS did the trick.
> >> > >>>
> >> > >>> Is there any place where defaults for all styles (debug, 
> >> > >>> info, warning, error, success, warning, failure, strong, mojo 
> >> > >>> and
> >>
> >> project)
> >>
> >> > >>> are reported? Thanks!> >>
> >> > >>
> >> > >> Yes if you do a mvn -X clean:
> >> > >> ...
> >> > >>
> >> > >> [DEBUG]   Imported: org.slf4j.helpers.* 
> >> > >>  >> > >>  > >> > >> [DEBUG]   Imported: org.slf4j.spi.* 
> >> > >>  >> > >>  > >> > >> [DEBUG] Populating class realm maven.api
> >> > >> [INFO] Error stacktraces are turned on.
> >> > >> [DEBUG] Message scheme: color
> >> > >> [DEBUG] Message styles: debug info warning error success 
> >> > >> failure
> >>
> >> strong
> >>
> >> > >> mojo project
> >> > >> [DEBUG] Reading global settings from
> >>
> >> /usr/local/maven/conf/settings.xml
> >>
> >> > >> [DEBUG] Reading user settings from 
> >> > >> /Users/kama/.m2/settings.xml [DEBUG] Reading global toolchains 
> >> > >> from /usr/local/maven/conf/toolchains.xml
> >> > >> [DEBUG] Reading user toolchains from 
> >> > >> /Users/kama/.m2/toolchains.xml
> >> > >
> >> > > Sorry, I don't get it: where do I see, i.e., that 
> >> > > https://urldefense.proofpoint.com/v2/url?u=http-3A__style.info;
> >> > > d=DwIFAw=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3
> >> > > PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=2L1RhrmrIqeZgpxGINVHuce
> >> > > t-6gs3sqlQV0EAtYNCEw=qxOWjrA4IAwf-c9x4Tj4feaA6XHKd--2MpsU3ZaF
> >> > > Tas=  is
> >>
> >> blue by
> >>
> >> > > default?>
> >> >
> >> > The following line is colored by the appropriate colors which are 
> >> > used...you should not do a redirect into a pipe via less/more etc..
> >> >
> >> > >> [DEBUG] Message styles: debug info warning error success 
> >> > >> failure
> >>
> >> strong
> >>
> >> I see:
> >>
> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__pasteboard.co_2
> >> wnAdZx8P.png=DwIFAw=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo
> >> =dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=2L1RhrmrIqeZgpxGIN
> >> VHucet-6gs3sqlQV0EAtYNCEw=DsBpenyyfz6ZTQ0kf3ynnjMnVQwN8mHlS9Gss3C
> >> z5ho=
> >>
> >> but still do not have the equivalent color name (e.g. that info is
> >> 'blue': I
> >> can guess it, naturally...).
> >>
> >> Regards.
> >>
> >> ---
> >> -- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For

[ANN] Apache Maven Surefire Plugin 2.20 Released

Re: [EXTERNAL] Re: Any way to change the color scheme in Maven 3.5.0?

Stale wiki link question [was: Re: dependency question]

RE: [EXTERNAL] Re: Any way to change the color scheme in Maven 3.5.0?

4 matches

Site Navigation

Mail list logo

Footer information