Re: [VOTE] Release Apache Maven Surefire Plugin version 2.20.1

2017-09-14 Thread Michael Osipov
Am 2017-09-11 um 05:33 schrieb Tibor Digana: Hi, We solved 24 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12340297 There are 101 issues left in JIRA:

Re: [VOTE] Release Apache Maven 3.5.1

2017-09-14 Thread Mark Derricutt
> +2 non-binding from Mark! I was discussing this with a coworker and he made the comment that if this change could break Mojos, maybe it shouldn't be in a point release - whats the policy on changes that may potentially break existing plugins? -- "Great artists are extremely selfish and

Re: [VOTE] Release Apache Maven 3.5.1

2017-09-14 Thread Petr Široký
Argh, I forgot to link the plugin source: https://github.com/kiegroup/droolsjbpm-integration/tree/7.3.0.Final/kie-maven-plugin On Thu, Sep 14, 2017 at 2:41 PM Petr Široký wrote: > Hello, > > I am seeing a (probably) similar issue with our custom plugin. > > See the

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.20.1

2017-09-14 Thread Petr Široký
+1 non-binding. Tested on several projects with thousands of tests (both surefire and failsafe ones). No issue found. Env: Fedora 25 Oracle JDK 8 Maven 3.5.0. Petr On Thu, Sep 14, 2017 at 8:00 AM Tibor Digana wrote: > (again from my Apache mail account) > Pls

Re: [VOTE] Release Apache Maven 3.5.1

2017-09-14 Thread Stephen Connolly
On 14 September 2017 at 04:43, Mark Derricutt wrote: > > +2 non-binding from Mark! > > I was discussing this with a coworker and he made the comment that if this > change could break Mojos, maybe it shouldn't be in a point release - whats > the policy on changes that may

Re: [VOTE] Release Apache Maven 3.5.1

2017-09-14 Thread Petr Široký
Hello, I am seeing a (probably) similar issue with our custom plugin. See the reproducer: https://github.com/psiroky/reproducers/tree/mvn351-kie-maven-plugin (works fine with maven 3.5.0, but fails with NPE with the RC of maven 3.5.1). I am not yet sure if the plugin is just doing something

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.20.1

2017-09-14 Thread Tibor Digana
+1 On Thu, Sep 14, 2017 at 2:27 PM, Petr Široký wrote: > +1 non-binding. Tested on several projects with thousands of tests (both > surefire and failsafe ones). No issue found. > > Env: > Fedora 25 > Oracle JDK 8 > Maven 3.5.0. > > Petr > > > On Thu, Sep 14, 2017 at 8:00

[ANN] Apache Maven Dependency Plugin Version 3.0.2 Released

2017-09-14 Thread Karl Heinz Marbaise
The Apache Maven team is pleased to announce the release of the Apache Maven Dependency Plugin Version 3.0.2. https://maven.apache.org/plugins/maven-dependency-plugin/ Important Note since 3.0.0: * Maven 3.X only * JDK 6 minimum requirement You should specify the version in your project's

[ANN] Apache Maven JLink Plugin Version 3.0.0-alpha-1 Released

2017-09-14 Thread Karl Heinz Marbaise
The Apache Maven team is pleased to announce the release of the Apache Maven JLink Plugin Version 3.0.0-alpha-1 release https://maven.apache.org/plugins/maven-jlink-plugin/ The plugin has got the major version 3 to make clear this plugin is only for Maven 3+. * Maven 3.X only * JDK 7

Re: [VOTE] Release Apache Maven 3.5.1

2017-09-14 Thread Petr Široký
I was able to easily fix our plugin by e.g. replacing "Thread.currentThread().getContextClassLoader()" with "this.getClass().getClassLoader()" (in the Mojo class) to get the plugin classloader. I don't know though if the "Thread.currentThread().getContextClassLoader()" is just misuse on our side

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.20.1

2017-09-14 Thread Tibor Digana
(again from my Apache mail account) Pls participate in the vote and test. On Thu, Sep 14, 2017 at 7:59 AM, Tibor Digana wrote: > Pls participate in the vote and test. > > On Mon, Sep 11, 2017 at 5:33 AM, Tibor Digana > wrote: > >> Hi,

Re: [VOTE] Release Apache Maven 3.5.1

2017-09-14 Thread Hervé BOUTEMY
+1 works well in everything I tested, colour on Windows with GitBash or Cygwin or any other Unix layer taken apart (in fact anything on WIndows that provides "TERM=xterm") workaround for those Windows users: add -Djansi.force=true to MAVEN_OPTS the only drawback will only be if you redirect