Re: I think we are ready for 3.5.0-alpha-1

[Tibor Digana]

Exactly this is the problem - forkMode and reuseForks in one function.
I will open Jira and push a fix.

On Mon, Feb 13, 2017 at 2:44 AM, Stuart McCulloch [via Maven] <
ml-node+s40175n5898461...@n5.nabble.com> wrote:

> So I tweaked ForkedLauncher from maven-verifier to dump out the forked
> command to log.txt and at least one of the failing ITs has a duplicated
> system property on the command-line:
>
> mvn -e --batch-mode -Dmaven.repo.local=/tmp/maven-
> surefire/surefire-integration-tests/../surefire-setup-
> integration-tests/target/it-repo 
> org.apache.maven.plugins:maven-clean-plugin:clean
> -Dsurefire.version=2.19.2-SNAPSHOT -DtestNgVersion=5.7
> -DtestNgClassifier=jdk15 -DforkMode=perthread -DreuseForks=false
> -DreuseForks=true -DthreadCount=1 -DtestProperty=testValue_${
> surefire.threadNumber}_${surefire.forkNumber} org.apache.maven.plugins.
> surefire:maven-dump-pid-plugin:dump-pid test
>
> specifically:
>
> -DreuseForks=false -DreuseForks=true
>
> Looking at SurefireLauncher.java
>
> https://github.com/apache/maven-surefire/blob/master/
> surefire-integration-tests/src/test/java/org/apache/
> maven/surefire/its/fixture/SurefireLauncher.java
>
> 1.  the reuseForks method adds a new system property argument each time
> it’s called:  -DreuseForks=
> 2.  the forkPerThread method calls forkMode( "perthread" ).reuseForks(
> false )
> 3.  the forkOncePerThread calls forkPerThread().reuseForks( true )
>
> So any test using SurefireLauncher’s “forkOncePerThread” method will end
> up with two “reuseForks” system property options on the command-line - and
> will therefore be affected by the change in system property option
> precedence.
>
> This explains why ForkModeIT fails for me locally with master, but passes
> with 3.3.9 - with current master the -DreuseForks=false option wins,
> whereas with 3.3.9 the -DreuseForks=true options wins.
>
> If I change SurefireLauncher.forkOncePerThread to avoid duplicating this
> system property, ie:
>
> return forkMode( "perthread" ).reuseForks( true );
>
> then ForkModeIT passes with both current master and previous Maven
> releases.
>
> Hope that helps...
>
> --
> Cheers, Stuart
>
>
> On Monday, 13 February 2017 at 01:32, Stuart McCulloch wrote:
>
> > Ironically I got those results the wrong way round when cutting+pasting
> :)
> >
> > To clarify, when testing
> >
> > mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate
> >
> > with previous Maven releases the last option wins:
> >
> > -Dmaven.repo.local=/tmp/zzz
> >
> > whereas with current master the first option wins:
> >
> > -Dmaven.repo.local=/tmp/aaa
> >
> > On Monday, 13 February 2017 at 00:19, Stuart McCulloch wrote:
> >
> > > Using the following command on a small test project:
> > >
> > > mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate
> > >
> > > and checking whether the “aaa” or “zzz” directory is created gives
> these results for previous Maven releases:
> > >
> > > 2.0.11 aaa
> > > 2.2.1 aaa
> > > 3.0.5 aaa
> > > 3.1.1 aaa
> > > 3.2.5 aaa
> > > 3.3.9 aaa
> > >
> > > whereas current master gives a different result:
> > >
> > > master zzz
> > >
> > > which confirms the precedence of CLI arguments is currently reversed
> on master compared to previous releases
> > >
> > > --
> > > Cheers, Stuart
> > >
> > >
> > > On Sunday, 12 February 2017 at 23:53, Stuart McCulloch wrote:
> > >
> > > > git bisect is pointing to the following commit:
> > > >
> > > > https://github.com/apache/maven/commit/
> ca4303031357a7decaee8de770b71fb2c2fedd28
> > > >
> > > > if I revert this change then the wrong PID issue disappears and
> ForkModeIT passes again
> > > >
> > > > I suspect that reversing the whole array of system property
> definitions, while solving MNG-6078, is breaking precedence of arguments on
> the CLI (which then affects these tests)
> > > >
> > > > On Sunday, 12 February 2017 at 20:26, Tibor Digana wrote:
> > > >
> > > > > So this is a local build status of surefire running on the top of
> certain
> > > > > Maven Version.
> > > > > Maven 3.3.9 OK on my side
> > > > > Maven 3.5.0-SNAPSHOT failed. Wrong PIDs, other tests failed on
> freebsd and
> > > > > not on Win7, so I asked Michael for logs which I do not have.
> > > > > So I am going to investigate.
> > > > >
> > > > > On Sun, Feb 12, 2017 at 9:05 PM, stephenconnolly [via Maven] <
> > > > > [hidden email]
>  (mailto:[hidden
> email] )> wrote:
> > > > >
> > > > > > Can you pop on HipChat with infra?
> > > > > >
> > > > > > You may need them to grab the files from the agent for you (or
> modify the
> > > > > > Jenkinsfile temporarily to archive the bits you need)
> > > > > >
> > > > > > On Sun 12 Feb 2017 at 19:55, Tibor Digana <[hidden email]
> > > > > > > wrote:
> > > > > >
> > > > > > > There is build process for surefire
> > > > > > >
> > > > > > > 

Re: I think we are ready for 3.5.0-alpha-1

[Stuart McCulloch]

So I tweaked ForkedLauncher from maven-verifier to dump out the forked command 
to log.txt and at least one of the failing ITs has a duplicated system property 
on the command-line:

mvn -e --batch-mode 
-Dmaven.repo.local=/tmp/maven-surefire/surefire-integration-tests/../surefire-setup-integration-tests/target/it-repo
 org.apache.maven.plugins:maven-clean-plugin:clean 
-Dsurefire.version=2.19.2-SNAPSHOT -DtestNgVersion=5.7 -DtestNgClassifier=jdk15 
-DforkMode=perthread -DreuseForks=false -DreuseForks=true -DthreadCount=1 
-DtestProperty=testValue_${surefire.threadNumber}_${surefire.forkNumber} 
org.apache.maven.plugins.surefire:maven-dump-pid-plugin:dump-pid test

specifically:

-DreuseForks=false -DreuseForks=true

Looking at SurefireLauncher.java

https://github.com/apache/maven-surefire/blob/master/surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/fixture/SurefireLauncher.java

1.  the reuseForks method adds a new system property argument each time it’s 
called:  -DreuseForks=
2.  the forkPerThread method calls forkMode( "perthread" ).reuseForks( false )
3.  the forkOncePerThread calls forkPerThread().reuseForks( true )

So any test using SurefireLauncher’s “forkOncePerThread” method will end up 
with two “reuseForks” system property options on the command-line - and will 
therefore be affected by the change in system property option precedence.

This explains why ForkModeIT fails for me locally with master, but passes with 
3.3.9 - with current master the -DreuseForks=false option wins, whereas with 
3.3.9 the -DreuseForks=true options wins.

If I change SurefireLauncher.forkOncePerThread to avoid duplicating this system 
property, ie:

return forkMode( "perthread" ).reuseForks( true );

then ForkModeIT passes with both current master and previous Maven releases.

Hope that helps...

--  
Cheers, Stuart


On Monday, 13 February 2017 at 01:32, Stuart McCulloch wrote:

> Ironically I got those results the wrong way round when cutting+pasting :)
>  
> To clarify, when testing
>  
> mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate
>  
> with previous Maven releases the last option wins:
>  
> -Dmaven.repo.local=/tmp/zzz
>  
> whereas with current master the first option wins:
>  
> -Dmaven.repo.local=/tmp/aaa  
>  
> On Monday, 13 February 2017 at 00:19, Stuart McCulloch wrote:
>  
> > Using the following command on a small test project:
> >  
> > mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate
> >  
> > and checking whether the “aaa” or “zzz” directory is created gives these 
> > results for previous Maven releases:
> >  
> > 2.0.11 aaa
> > 2.2.1 aaa
> > 3.0.5 aaa
> > 3.1.1 aaa
> > 3.2.5 aaa
> > 3.3.9 aaa
> >  
> > whereas current master gives a different result:
> >  
> > master zzz  
> >  
> > which confirms the precedence of CLI arguments is currently reversed on 
> > master compared to previous releases
> >  
> > --  
> > Cheers, Stuart
> >  
> >  
> > On Sunday, 12 February 2017 at 23:53, Stuart McCulloch wrote:
> >  
> > > git bisect is pointing to the following commit:
> > >  
> > > https://github.com/apache/maven/commit/ca4303031357a7decaee8de770b71fb2c2fedd28
> > >  
> > > if I revert this change then the wrong PID issue disappears and 
> > > ForkModeIT passes again
> > >  
> > > I suspect that reversing the whole array of system property definitions, 
> > > while solving MNG-6078, is breaking precedence of arguments on the CLI 
> > > (which then affects these tests)  
> > >  
> > > On Sunday, 12 February 2017 at 20:26, Tibor Digana wrote:
> > >  
> > > > So this is a local build status of surefire running on the top of 
> > > > certain
> > > > Maven Version.
> > > > Maven 3.3.9 OK on my side
> > > > Maven 3.5.0-SNAPSHOT failed. Wrong PIDs, other tests failed on freebsd 
> > > > and
> > > > not on Win7, so I asked Michael for logs which I do not have.
> > > > So I am going to investigate.
> > > >  
> > > > On Sun, Feb 12, 2017 at 9:05 PM, stephenconnolly [via Maven] <
> > > > ml-node+s40175n5898384...@n5.nabble.com 
> > > > (mailto:ml-node+s40175n5898384...@n5.nabble.com)> wrote:
> > > >  
> > > > > Can you pop on HipChat with infra?
> > > > >  
> > > > > You may need them to grab the files from the agent for you (or modify 
> > > > > the
> > > > > Jenkinsfile temporarily to archive the bits you need)
> > > > >  
> > > > > On Sun 12 Feb 2017 at 19:55, Tibor Digana <[hidden email]
> > > > > > wrote:
> > > > >  
> > > > > > There is build process for surefire
> > > > > >  
> > > > > > https://builds.apache.org/view/Maven/job/maven-master-
> > > > > release-status-test-surefire-linux
> > > > > > with Jenkins file.
> > > > > > This particular build fails with test
> > > > > >  
> > > > > > Surefire141PluggableProvidersIT
> > > > > >  
> > > > > > It is only one and different from your local build result.
> > > > > >  
> > > > > > I asked Stephen to enable Workspace, because I need to have 

Re: I think we are ready for 3.5.0-alpha-1

[Stuart McCulloch]

Ironically I got those results the wrong way round when cutting+pasting :)

To clarify, when testing

mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate

with previous Maven releases the last option wins:

-Dmaven.repo.local=/tmp/zzz

whereas with current master the first option wins:

-Dmaven.repo.local=/tmp/aaa  

On Monday, 13 February 2017 at 00:19, Stuart McCulloch wrote:

> Using the following command on a small test project:
>  
> mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate
>  
> and checking whether the “aaa” or “zzz” directory is created gives these 
> results for previous Maven releases:
>  
> 2.0.11 aaa
> 2.2.1 aaa
> 3.0.5 aaa
> 3.1.1 aaa
> 3.2.5 aaa
> 3.3.9 aaa
>  
> whereas current master gives a different result:
>  
> master zzz  
>  
> which confirms the precedence of CLI arguments is currently reversed on 
> master compared to previous releases
>  
> --  
> Cheers, Stuart
>  
>  
> On Sunday, 12 February 2017 at 23:53, Stuart McCulloch wrote:
>  
> > git bisect is pointing to the following commit:
> >  
> > https://github.com/apache/maven/commit/ca4303031357a7decaee8de770b71fb2c2fedd28
> >  
> > if I revert this change then the wrong PID issue disappears and ForkModeIT 
> > passes again
> >  
> > I suspect that reversing the whole array of system property definitions, 
> > while solving MNG-6078, is breaking precedence of arguments on the CLI 
> > (which then affects these tests)  
> >  
> > On Sunday, 12 February 2017 at 20:26, Tibor Digana wrote:
> >  
> > > So this is a local build status of surefire running on the top of certain
> > > Maven Version.
> > > Maven 3.3.9 OK on my side
> > > Maven 3.5.0-SNAPSHOT failed. Wrong PIDs, other tests failed on freebsd and
> > > not on Win7, so I asked Michael for logs which I do not have.
> > > So I am going to investigate.
> > >  
> > > On Sun, Feb 12, 2017 at 9:05 PM, stephenconnolly [via Maven] <
> > > ml-node+s40175n5898384...@n5.nabble.com 
> > > (mailto:ml-node+s40175n5898384...@n5.nabble.com)> wrote:
> > >  
> > > > Can you pop on HipChat with infra?
> > > >  
> > > > You may need them to grab the files from the agent for you (or modify 
> > > > the
> > > > Jenkinsfile temporarily to archive the bits you need)
> > > >  
> > > > On Sun 12 Feb 2017 at 19:55, Tibor Digana <[hidden email]
> > > > > wrote:
> > > >  
> > > > > There is build process for surefire
> > > > >  
> > > > > https://builds.apache.org/view/Maven/job/maven-master-
> > > > release-status-test-surefire-linux
> > > > > with Jenkins file.
> > > > > This particular build fails with test
> > > > >  
> > > > > Surefire141PluggableProvidersIT
> > > > >  
> > > > > It is only one and different from your local build result.
> > > > >  
> > > > > I asked Stephen to enable Workspace, because I need to have files from
> > > > > target folders for analysis to understand what is going on the 
> > > > > machine.
> > > > > Stephen told me that I should trigger rebuild. So I did and launched
> > > > >  
> > > >  
> > > > "Build
> > > > > with Parameters" but the build failed not running Maven build, however
> > > > > Workspace appears now.
> > > > >  
> > > > > How can I force trigger the build?
> > > > >  
> > > > >  
> > > > > https://builds.apache.org/view/Maven/job/maven-master-
> > > > release-status-test-surefire-linux/11/console
> > > > >  
> > > > > There is another build process, old one actually, and it is 
> > > > > successful.
> > > > > The difference is because I think race condition when JVM error once
> > > > >  
> > > >  
> > > > goes
> > > > > to std/err and other log in the first build with Jenkins file.
> > > > > This can, I think, be only one more assertion statement in IT but I 
> > > > > need
> > > > >  
> > > >  
> > > > to
> > > > > see Workspace.
> > > > >  
> > > > >  
> > > > >  
> > > > >  
> > > > >  
> > > > > On Sun, Feb 12, 2017 at 5:04 PM, Christian Schulte [via Maven] <
> > > > > [hidden email] 
> > > > > >
> > > > >  
> > > >  
> > > > wrote:
> > > > >  
> > > > > > @Stephen: Are there any Jenkins jobs left running the plugin ITs 
> > > > > > with
> > > > > > current Maven master? Surefire has it's own git repository. Do we 
> > > > > > have
> > > > > > some Jenkins job for this as well? It's important to run all those 
> > > > > > ITs
> > > > > > (plugins from subversion and the ones with theire own repository) 
> > > > > > with
> > > > > > what we are going to release as 3.5.0 before releasing it.
> > > > > >  
> > > > > > Regards,
> > > > > > --
> > > > > > Christian
> > > > > >  
> > > > > >  
> > > > > > -
> > > > > > To unsubscribe, e-mail: [hidden email]
> > > > > > 
> > > > > > For additional commands, e-mail: [hidden email]
> > > > > > 
> > > > > >  

Re: I think we are ready for 3.5.0-alpha-1

[Tibor Digana]

Good catch, Stuart, but this would be only valid if we duplicated some
system property in two different POMs.
This is what I wrote in our private emails:

If I use Maven 3.5.0-SNAPSHOT and if I run this command then everything is
ok, means one PID:
surefire-integration-tests\target\ForkModeTestNGIT_
testForkModeOncePerThreadSingleThread>mvn -o -Dsurefire.version=2.19.2-SNAPSHOT
-DforkMode=perthread -DreuseForks=true -DthreadCount=1 test

If I run it in build process, then it is 3 PIDs. It looks like these system
properties are different or something else.
I will debug the build process tomorrow.

On Mon, Feb 13, 2017 at 1:20 AM, Stuart McCulloch [via Maven] <
ml-node+s40175n5898443...@n5.nabble.com> wrote:

> Using the following command on a small test project:
>
> mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate
>
> and checking whether the “aaa” or “zzz” directory is created gives these
> results for previous Maven releases:
>
> 2.0.11 aaa
> 2.2.1 aaa
> 3.0.5 aaa
> 3.1.1 aaa
> 3.2.5 aaa
> 3.3.9 aaa
>
> whereas current master gives a different result:
>
> master zzz
>
> which confirms the precedence of CLI arguments is currently reversed on
> master compared to previous releases
>
> --
> Cheers, Stuart
>
>
> On Sunday, 12 February 2017 at 23:53, Stuart McCulloch wrote:
>
> > git bisect is pointing to the following commit:
> >
> > https://github.com/apache/maven/commit/ca4303031357a7decaee8de770b71f
> b2c2fedd28
> >
> > if I revert this change then the wrong PID issue disappears and
> ForkModeIT passes again
> >
> > I suspect that reversing the whole array of system property definitions,
> while solving MNG-6078, is breaking precedence of arguments on the CLI
> (which then affects these tests)
> >
> > On Sunday, 12 February 2017 at 20:26, Tibor Digana wrote:
> >
> > > So this is a local build status of surefire running on the top of
> certain
> > > Maven Version.
> > > Maven 3.3.9 OK on my side
> > > Maven 3.5.0-SNAPSHOT failed. Wrong PIDs, other tests failed on freebsd
> and
> > > not on Win7, so I asked Michael for logs which I do not have.
> > > So I am going to investigate.
> > >
> > > On Sun, Feb 12, 2017 at 9:05 PM, stephenconnolly [via Maven] <
> > > [hidden email] 
> (mailto:[hidden email]
> )> wrote:
> > >
> > > > Can you pop on HipChat with infra?
> > > >
> > > > You may need them to grab the files from the agent for you (or
> modify the
> > > > Jenkinsfile temporarily to archive the bits you need)
> > > >
> > > > On Sun 12 Feb 2017 at 19:55, Tibor Digana <[hidden email]
> > > > > wrote:
> > > >
> > > > > There is build process for surefire
> > > > >
> > > > > https://builds.apache.org/view/Maven/job/maven-master-
> > > > release-status-test-surefire-linux
> > > > > with Jenkins file.
> > > > > This particular build fails with test
> > > > >
> > > > > Surefire141PluggableProvidersIT
> > > > >
> > > > > It is only one and different from your local build result.
> > > > >
> > > > > I asked Stephen to enable Workspace, because I need to have files
> from
> > > > > target folders for analysis to understand what is going on the
> machine.
> > > > > Stephen told me that I should trigger rebuild. So I did and
> launched
> > > > >
> > > >
> > > > "Build
> > > > > with Parameters" but the build failed not running Maven build,
> however
> > > > > Workspace appears now.
> > > > >
> > > > > How can I force trigger the build?
> > > > >
> > > > >
> > > > > https://builds.apache.org/view/Maven/job/maven-master-
> > > > release-status-test-surefire-linux/11/console
> > > > >
> > > > > There is another build process, old one actually, and it is
> successful.
> > > > > The difference is because I think race condition when JVM error
> once
> > > > >
> > > >
> > > > goes
> > > > > to std/err and other log in the first build with Jenkins file.
> > > > > This can, I think, be only one more assertion statement in IT but
> I need
> > > > >
> > > >
> > > > to
> > > > > see Workspace.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Sun, Feb 12, 2017 at 5:04 PM, Christian Schulte [via Maven] <
> > > > > [hidden email]  type=node=5898384=1>>
> > > > >
> > > >
> > > > wrote:
> > > > >
> > > > > > @Stephen: Are there any Jenkins jobs left running the plugin ITs
> with
> > > > > > current Maven master? Surefire has it's own git repository. Do
> we have
> > > > > > some Jenkins job for this as well? It's important to run all
> those ITs
> > > > > > (plugins from subversion and the ones with theire own
> repository) with
> > > > > > what we are going to release as 3.5.0 before releasing it.
> > > > > >
> > > > > > Regards,
> > > > > > --
> > > > > > Christian
> > > > > >
> > > > > >
> > > > > > -
>
> > > > > > To unsubscribe, e-mail: [hidden email]
> > > > 

Re: I think we are ready for 3.5.0-alpha-1

[Stuart McCulloch]

Using the following command on a small test project:

mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate

and checking whether the “aaa” or “zzz” directory is created gives these 
results for previous Maven releases:

2.0.11 aaa
2.2.1 aaa
3.0.5 aaa
3.1.1 aaa
3.2.5 aaa
3.3.9 aaa

whereas current master gives a different result:

master zzz  

which confirms the precedence of CLI arguments is currently reversed on master 
compared to previous releases

--  
Cheers, Stuart


On Sunday, 12 February 2017 at 23:53, Stuart McCulloch wrote:

> git bisect is pointing to the following commit:
>  
> https://github.com/apache/maven/commit/ca4303031357a7decaee8de770b71fb2c2fedd28
>  
> if I revert this change then the wrong PID issue disappears and ForkModeIT 
> passes again
>  
> I suspect that reversing the whole array of system property definitions, 
> while solving MNG-6078, is breaking precedence of arguments on the CLI (which 
> then affects these tests)  
>  
> On Sunday, 12 February 2017 at 20:26, Tibor Digana wrote:
>  
> > So this is a local build status of surefire running on the top of certain
> > Maven Version.
> > Maven 3.3.9 OK on my side
> > Maven 3.5.0-SNAPSHOT failed. Wrong PIDs, other tests failed on freebsd and
> > not on Win7, so I asked Michael for logs which I do not have.
> > So I am going to investigate.
> >  
> > On Sun, Feb 12, 2017 at 9:05 PM, stephenconnolly [via Maven] <
> > ml-node+s40175n5898384...@n5.nabble.com 
> > (mailto:ml-node+s40175n5898384...@n5.nabble.com)> wrote:
> >  
> > > Can you pop on HipChat with infra?
> > >  
> > > You may need them to grab the files from the agent for you (or modify the
> > > Jenkinsfile temporarily to archive the bits you need)
> > >  
> > > On Sun 12 Feb 2017 at 19:55, Tibor Digana <[hidden email]
> > > > wrote:
> > >  
> > > > There is build process for surefire
> > > >  
> > > > https://builds.apache.org/view/Maven/job/maven-master-
> > > release-status-test-surefire-linux
> > > > with Jenkins file.
> > > > This particular build fails with test
> > > >  
> > > > Surefire141PluggableProvidersIT
> > > >  
> > > > It is only one and different from your local build result.
> > > >  
> > > > I asked Stephen to enable Workspace, because I need to have files from
> > > > target folders for analysis to understand what is going on the machine.
> > > > Stephen told me that I should trigger rebuild. So I did and launched
> > > >  
> > >  
> > > "Build
> > > > with Parameters" but the build failed not running Maven build, however
> > > > Workspace appears now.
> > > >  
> > > > How can I force trigger the build?
> > > >  
> > > >  
> > > > https://builds.apache.org/view/Maven/job/maven-master-
> > > release-status-test-surefire-linux/11/console
> > > >  
> > > > There is another build process, old one actually, and it is successful.
> > > > The difference is because I think race condition when JVM error once
> > > >  
> > >  
> > > goes
> > > > to std/err and other log in the first build with Jenkins file.
> > > > This can, I think, be only one more assertion statement in IT but I need
> > > >  
> > >  
> > > to
> > > > see Workspace.
> > > >  
> > > >  
> > > >  
> > > >  
> > > >  
> > > > On Sun, Feb 12, 2017 at 5:04 PM, Christian Schulte [via Maven] <
> > > > [hidden email] >
> > > >  
> > >  
> > > wrote:
> > > >  
> > > > > @Stephen: Are there any Jenkins jobs left running the plugin ITs with
> > > > > current Maven master? Surefire has it's own git repository. Do we have
> > > > > some Jenkins job for this as well? It's important to run all those ITs
> > > > > (plugins from subversion and the ones with theire own repository) with
> > > > > what we are going to release as 3.5.0 before releasing it.
> > > > >  
> > > > > Regards,
> > > > > --
> > > > > Christian
> > > > >  
> > > > >  
> > > > > -
> > > > > To unsubscribe, e-mail: [hidden email]
> > > > > 
> > > > > For additional commands, e-mail: [hidden email]
> > > > > 
> > > > >  
> > > > >  
> > > > >  
> > > > > --
> > > > > If you reply to this email, your message will be added to the
> > > > >  
> > > >  
> > > >  
> > >  
> > > discussion
> > > > > below:
> > > > > http://maven.40175.n5.nabble.com/I-think-we-are-ready-for-
> > > > >  
> > > >  
> > >  
> > > 3-5-0-alpha-1-
> > > > > tp5897626p5898337.html
> > > > > To start a new topic under Maven Developers, email
> > > > > [hidden email] 
> > > > > To unsubscribe from Maven Developers, click here
> > > > > <
> > > > >  
> > > > > .
> > > > > NAML
> > > > > <
> > > > >  
> > > >  
> > > > http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?
> > > >  
> > >  
> > > 

Re: I think we are ready for 3.5.0-alpha-1

[Stuart McCulloch]

git bisect is pointing to the following commit:

https://github.com/apache/maven/commit/ca4303031357a7decaee8de770b71fb2c2fedd28

if I revert this change then the wrong PID issue disappears and ForkModeIT 
passes again

I suspect that reversing the whole array of system property definitions, while 
solving MNG-6078, is breaking precedence of arguments on the CLI (which then 
affects these tests) 

On Sunday, 12 February 2017 at 20:26, Tibor Digana wrote:

> So this is a local build status of surefire running on the top of certain
> Maven Version.
> Maven 3.3.9 OK on my side
> Maven 3.5.0-SNAPSHOT failed. Wrong PIDs, other tests failed on freebsd and
> not on Win7, so I asked Michael for logs which I do not have.
> So I am going to investigate.
> 
> On Sun, Feb 12, 2017 at 9:05 PM, stephenconnolly [via Maven] <
> ml-node+s40175n5898384...@n5.nabble.com 
> (mailto:ml-node+s40175n5898384...@n5.nabble.com)> wrote:
> 
> > Can you pop on HipChat with infra?
> > 
> > You may need them to grab the files from the agent for you (or modify the
> > Jenkinsfile temporarily to archive the bits you need)
> > 
> > On Sun 12 Feb 2017 at 19:55, Tibor Digana <[hidden email]
> > > wrote:
> > 
> > > There is build process for surefire
> > > 
> > > https://builds.apache.org/view/Maven/job/maven-master-
> > release-status-test-surefire-linux
> > > with Jenkins file.
> > > This particular build fails with test
> > > 
> > > Surefire141PluggableProvidersIT
> > > 
> > > It is only one and different from your local build result.
> > > 
> > > I asked Stephen to enable Workspace, because I need to have files from
> > > target folders for analysis to understand what is going on the machine.
> > > Stephen told me that I should trigger rebuild. So I did and launched
> > > 
> > 
> > "Build
> > > with Parameters" but the build failed not running Maven build, however
> > > Workspace appears now.
> > > 
> > > How can I force trigger the build?
> > > 
> > > 
> > > https://builds.apache.org/view/Maven/job/maven-master-
> > release-status-test-surefire-linux/11/console
> > > 
> > > There is another build process, old one actually, and it is successful.
> > > The difference is because I think race condition when JVM error once
> > > 
> > 
> > goes
> > > to std/err and other log in the first build with Jenkins file.
> > > This can, I think, be only one more assertion statement in IT but I need
> > > 
> > 
> > to
> > > see Workspace.
> > > 
> > > 
> > > 
> > > 
> > > 
> > > On Sun, Feb 12, 2017 at 5:04 PM, Christian Schulte [via Maven] <
> > > [hidden email] >
> > > 
> > 
> > wrote:
> > > 
> > > > @Stephen: Are there any Jenkins jobs left running the plugin ITs with
> > > > current Maven master? Surefire has it's own git repository. Do we have
> > > > some Jenkins job for this as well? It's important to run all those ITs
> > > > (plugins from subversion and the ones with theire own repository) with
> > > > what we are going to release as 3.5.0 before releasing it.
> > > > 
> > > > Regards,
> > > > --
> > > > Christian
> > > > 
> > > > 
> > > > -
> > > > To unsubscribe, e-mail: [hidden email]
> > > > 
> > > > For additional commands, e-mail: [hidden email]
> > > > 
> > > > 
> > > > 
> > > > 
> > > > --
> > > > If you reply to this email, your message will be added to the
> > > > 
> > > 
> > > 
> > 
> > discussion
> > > > below:
> > > > http://maven.40175.n5.nabble.com/I-think-we-are-ready-for-
> > > > 
> > > 
> > 
> > 3-5-0-alpha-1-
> > > > tp5897626p5898337.html
> > > > To start a new topic under Maven Developers, email
> > > > [hidden email] 
> > > > To unsubscribe from Maven Developers, click here
> > > > <
> > > > 
> > > > .
> > > > NAML
> > > > <
> > > > 
> > > 
> > > http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?
> > > 
> > 
> > macro=macro_viewer=instant_html%21nabble%3Aemail.naml&
> > base=nabble.naml.namespaces.BasicNamespace-nabble.view.
> > web.template.NabbleNamespace-nabble.view.web.template 
> > (http://web.template.NabbleNamespace-nabble.view.web.template).
> > NodeNamespace=notify_subscribers%21nabble%
> > 3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_
> > instant_email%21nabble%3Aemail.naml
> > > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > --
> > > View this message in context:
> > > http://maven.40175.n5.nabble.com/I-think-we-are-ready-for-3-5-0-alpha-1-
> > > 
> > 
> > tp5897626p5898378.html
> > > Sent from the Maven Developers mailing list archive at Nabble.com 
> > > (http://Nabble.com).
> > 
> > 
> > --
> > Sent from my phone
> > 
> > 
> > --
> > If you reply to this email, your message will be added to the discussion
> > below:
> > 

Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass plugin integration tests on Windows

[Christian Schulte]

This is the result of a plugins build on Windows using current Maven
3.5.0-SNAPSHOT master.

Am 02/12/17 um 23:44 schrieb Apache Jenkins Server:
> This is an automated email to notify the Maven developer list that there are 
> unreleased changes in the GIT master branch of Maven that have passed a 
> release build not passing plugin integration tests on Windows.
> 
> 
> 
> Please review the following build job for any issues with changes to the 
> Maven master branch.
> 
> 
> 
> -Jenkins
> 


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

Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass plugin integration tests on Linux

[Christian Schulte]

This is the result of a plugins build on linux using current Maven
3.5.0-SNAPSHOT master.

Am 02/12/17 um 23:19 schrieb Apache Jenkins Server:
> This is an automated email to notify the Maven developer list that there are 
> unreleased changes in the GIT master branch of Maven that have passed a 
> release build not passing plugin integration tests on Linux.
> 
> 
> 
> Please review the following build job for any issues with changes to the 
> Maven master branch.
> 
> 
> 
> -Jenkins
> 


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

Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass plugin integration tests on Windows

[Christian Schulte]

This is the result of a Surefire build on Windows using current Maven
3.5.0-SNAPSHOT master.

Am 02/12/17 um 23:16 schrieb Apache Jenkins Server:
> This is an automated email to notify the Maven developer list that there are 
> unreleased changes in the GIT master branch of Maven that have passed a 
> release build not passing a surefire build on Windows including integration 
> tests.
> 
> 
> 
> Please review the following build job for any issues with changes to the 
> Maven master branch.
> 
> 
> 
> -Jenkins
> 


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

Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass a surefire build including integration tests on Linux

[Christian Schulte]

This is the result of a Surefire build on linux using current Maven
3.5.0-SNAPSHOT master.

Am 02/12/17 um 22:51 schrieb Apache Jenkins Server:
> This is an automated email to notify the Maven developer list that there are 
> unreleased changes in the GIT master branch of Maven that have passed a 
> release build not passing a surefire build on Linux including integration 
> tests.
> 
> 
> 
> Please review the following build job for any issues with changes to the 
> Maven master branch.
> 
> 
> 
> -Jenkins
> 


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

Re: I think we are ready for 3.5.0-alpha-1

[Christian Schulte]

Build has run. Results are: Core ITs ran successfully. Plugin ITs
failed. Surefire build failed. Workspaces are here:



Apache Maven Remote Resources Plugin ... FAILURE

/bin/sh: 1: mvn: not found

Maybe a launcher issue?



Same on Windows.

'mvn' is not recognized as an internal or external command,
operable program or batch file.

I'll take a look tomorrow.



Looking at the console output, this pretty much looks the same as what I
am getting locally:





Windows seems to be affected as well. Console output is here:



The easiest way to trigger all those jobs is to start the following
build job:



This will trigger all the other build jobs in correct order.

Note: I setup those jobs during working on the pre-reset-master branch
when I noticed that it's not enough to just run the core ITs. Those jobs
never succeeded since I created them. That's what I was working on
before resetting the branches. I would not have exepected those jobs to
fail after the reset.

The maven-master-release-status job is setup to run once a week. It is
this job sending those [PING] subject mails every now and then. When all
jobs succeed, it would (hopefully) send a mail stating that master is in
a releaseable state.

Regards,
-- 
Christian


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

Re: I think we are ready for 3.5.0-alpha-1

[Christian Schulte]

Am 12.02.2017 um 20:54 schrieb Tibor Digana:
> There is build process for surefire
> https://builds.apache.org/view/Maven/job/maven-master-release-status-test-surefire-linux
> with Jenkins file.
> This particular build fails with test
> 
> Surefire141PluggableProvidersIT
> 
> It is only one and different from your local build result.
> 
> I asked Stephen to enable Workspace, because I need to have files from
> target folders for analysis to understand what is going on the machine.
> Stephen told me that I should trigger rebuild. So I did and launched "Build
> with Parameters" but the build failed not running Maven build, however
> Workspace appears now.
> 
> How can I force trigger the build?

This is my amateur trial and error pseudo-pipeline setup. You can
trigger that "pipeline" by starting an initial build job here. This will
trigger all the other jobs.



I just started a build. If you login to Jenkins, you should be able to
access the different workspaces. Maybe a permission issue. Just login
and the workspace should be there.

Regards,
-- 
Christian


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

Re: I think we are ready for 3.5.0-alpha-1

[Christian Schulte]

I never checked different Maven versions or Surefire tags. Only the
pre-reset-master branch for a few weeks (3.4.0-SNAPSHOT back then) and
now with current Maven master (3.5.0-SNAPSHOT). The only changes to the
Maven core which could have an impact to multi-threading behaviour can
be some dependency upgrade introducing issues. We maybe just need to
find out which dependency upgrade introduces the issues. Plexus comes to
mind.


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

Re: I think we are ready for 3.5.0-alpha-1

[Tibor Digana]

So this is a local build status of surefire running on the top of certain
Maven Version.
Maven 3.3.9 OK on my side
Maven 3.5.0-SNAPSHOT failed. Wrong PIDs, other tests failed on freebsd and
not on Win7, so I asked Michael for logs which I do not have.
So I am going to investigate.

On Sun, Feb 12, 2017 at 9:05 PM, stephenconnolly [via Maven] <
ml-node+s40175n5898384...@n5.nabble.com> wrote:

> Can you pop on HipChat with infra?
>
> You may need them to grab the files from the agent for you (or modify the
> Jenkinsfile temporarily to archive the bits you need)
>
> On Sun 12 Feb 2017 at 19:55, Tibor Digana <[hidden email]
> > wrote:
>
> > There is build process for surefire
> >
> > https://builds.apache.org/view/Maven/job/maven-master-
> release-status-test-surefire-linux
> > with Jenkins file.
> > This particular build fails with test
> >
> > Surefire141PluggableProvidersIT
> >
> > It is only one and different from your local build result.
> >
> > I asked Stephen to enable Workspace, because I need to have files from
> > target folders for analysis to understand what is going on the machine.
> > Stephen told me that I should trigger rebuild. So I did and launched
> "Build
> > with Parameters" but the build failed not running Maven build, however
> > Workspace appears now.
> >
> > How can I force trigger the build?
> >
> >
> > https://builds.apache.org/view/Maven/job/maven-master-
> release-status-test-surefire-linux/11/console
> >
> > There is another build process, old one actually, and it is successful.
> > The difference is because I think race condition when JVM error once
> goes
> > to std/err and other log in the first build with Jenkins file.
> > This can, I think, be only one more assertion statement in IT but I need
> to
> > see Workspace.
> >
> >
> >
> >
> >
> > On Sun, Feb 12, 2017 at 5:04 PM, Christian Schulte [via Maven] <
> > [hidden email] >
> wrote:
> >
> > > @Stephen: Are there any Jenkins jobs left running the plugin ITs with
> > > current Maven master? Surefire has it's own git repository. Do we have
> > > some Jenkins job for this as well? It's important to run all those ITs
> > > (plugins from subversion and the ones with theire own repository) with
> > > what we are going to release as 3.5.0 before releasing it.
> > >
> > > Regards,
> > > --
> > > Christian
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: [hidden email]
> > > 
> > > For additional commands, e-mail: [hidden email]
> > > 
> > >
> > >
> > >
> > > --
> > > If you reply to this email, your message will be added to the
> discussion
> > > below:
> > > http://maven.40175.n5.nabble.com/I-think-we-are-ready-for-
> 3-5-0-alpha-1-
> > > tp5897626p5898337.html
> > > To start a new topic under Maven Developers, email
> > > [hidden email] 
> > > To unsubscribe from Maven Developers, click here
> > > <
> > >
> > > .
> > > NAML
> > > <
> > http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?
> macro=macro_viewer=instant_html%21nabble%3Aemail.naml&
> base=nabble.naml.namespaces.BasicNamespace-nabble.view.
> web.template.NabbleNamespace-nabble.view.web.template.
> NodeNamespace=notify_subscribers%21nabble%
> 3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_
> instant_email%21nabble%3Aemail.naml
> > >
> > >
> >
> >
> >
> >
> > --
> > View this message in context:
> > http://maven.40175.n5.nabble.com/I-think-we-are-ready-for-3-5-0-alpha-1-
> tp5897626p5898378.html
> > Sent from the Maven Developers mailing list archive at Nabble.com.
>
> --
> Sent from my phone
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://maven.40175.n5.nabble.com/I-think-we-are-ready-for-3-5-0-alpha-1-
> tp5897626p5898384.html
> To start a new topic under Maven Developers, email
> ml-node+s40175n142166...@n5.nabble.com
> To unsubscribe from Maven Developers, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://maven.40175.n5.nabble.com/I-think-we-are-ready-for-3-5-0-alpha-1-tp5897626p5898389.html
Sent from the Maven Developers mailing list archive at Nabble.com.

Re: I think we are ready for 3.5.0-alpha-1

[Stephen Connolly]

Can you pop on HipChat with infra?

You may need them to grab the files from the agent for you (or modify the
Jenkinsfile temporarily to archive the bits you need)

On Sun 12 Feb 2017 at 19:55, Tibor Digana  wrote:

> There is build process for surefire
>
> https://builds.apache.org/view/Maven/job/maven-master-release-status-test-surefire-linux
> with Jenkins file.
> This particular build fails with test
>
> Surefire141PluggableProvidersIT
>
> It is only one and different from your local build result.
>
> I asked Stephen to enable Workspace, because I need to have files from
> target folders for analysis to understand what is going on the machine.
> Stephen told me that I should trigger rebuild. So I did and launched "Build
> with Parameters" but the build failed not running Maven build, however
> Workspace appears now.
>
> How can I force trigger the build?
>
>
> https://builds.apache.org/view/Maven/job/maven-master-release-status-test-surefire-linux/11/console
>
> There is another build process, old one actually, and it is successful.
> The difference is because I think race condition when JVM error once goes
> to std/err and other log in the first build with Jenkins file.
> This can, I think, be only one more assertion statement in IT but I need to
> see Workspace.
>
>
>
>
>
> On Sun, Feb 12, 2017 at 5:04 PM, Christian Schulte [via Maven] <
> ml-node+s40175n5898337...@n5.nabble.com> wrote:
>
> > @Stephen: Are there any Jenkins jobs left running the plugin ITs with
> > current Maven master? Surefire has it's own git repository. Do we have
> > some Jenkins job for this as well? It's important to run all those ITs
> > (plugins from subversion and the ones with theire own repository) with
> > what we are going to release as 3.5.0 before releasing it.
> >
> > Regards,
> > --
> > Christian
> >
> >
> > -
> > To unsubscribe, e-mail: [hidden email]
> > 
> > For additional commands, e-mail: [hidden email]
> > 
> >
> >
> >
> > --
> > If you reply to this email, your message will be added to the discussion
> > below:
> > http://maven.40175.n5.nabble.com/I-think-we-are-ready-for-3-5-0-alpha-1-
> > tp5897626p5898337.html
> > To start a new topic under Maven Developers, email
> > ml-node+s40175n142166...@n5.nabble.com
> > To unsubscribe from Maven Developers, click here
> > <
> http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code=142166=dGlib3JkaWdhbmFAYXBhY2hlLm9yZ3wxNDIxNjZ8LTI4OTQ5MjEwMg==
> >
> > .
> > NAML
> > <
> http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >
>
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/I-think-we-are-ready-for-3-5-0-alpha-1-tp5897626p5898378.html
> Sent from the Maven Developers mailing list archive at Nabble.com.

-- 
Sent from my phone

Re: I think we are ready for 3.5.0-alpha-1

[Tibor Digana]

There is build process for surefire
https://builds.apache.org/view/Maven/job/maven-master-release-status-test-surefire-linux
with Jenkins file.
This particular build fails with test

Surefire141PluggableProvidersIT

It is only one and different from your local build result.

I asked Stephen to enable Workspace, because I need to have files from
target folders for analysis to understand what is going on the machine.
Stephen told me that I should trigger rebuild. So I did and launched "Build
with Parameters" but the build failed not running Maven build, however
Workspace appears now.

How can I force trigger the build?

https://builds.apache.org/view/Maven/job/maven-master-release-status-test-surefire-linux/11/console

There is another build process, old one actually, and it is successful.
The difference is because I think race condition when JVM error once goes
to std/err and other log in the first build with Jenkins file.
This can, I think, be only one more assertion statement in IT but I need to
see Workspace.





On Sun, Feb 12, 2017 at 5:04 PM, Christian Schulte [via Maven] <
ml-node+s40175n5898337...@n5.nabble.com> wrote:

> @Stephen: Are there any Jenkins jobs left running the plugin ITs with
> current Maven master? Surefire has it's own git repository. Do we have
> some Jenkins job for this as well? It's important to run all those ITs
> (plugins from subversion and the ones with theire own repository) with
> what we are going to release as 3.5.0 before releasing it.
>
> Regards,
> --
> Christian
>
>
> -
> To unsubscribe, e-mail: [hidden email]
> 
> For additional commands, e-mail: [hidden email]
> 
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://maven.40175.n5.nabble.com/I-think-we-are-ready-for-3-5-0-alpha-1-
> tp5897626p5898337.html
> To start a new topic under Maven Developers, email
> ml-node+s40175n142166...@n5.nabble.com
> To unsubscribe from Maven Developers, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://maven.40175.n5.nabble.com/I-think-we-are-ready-for-3-5-0-alpha-1-tp5897626p5898378.html
Sent from the Maven Developers mailing list archive at Nabble.com.

[ANN] Apache Maven Archetype Plugin 3.0.0 Released

[Robert Scholte]

The Apache Maven team is pleased to announce the release of the Apache  
Maven Archetype Plugin, version 3.0.0


The Archetype Plugin allows the user to create a Maven project from an  
existing template called an archetype.

It also allows the user to create an archetype from an existing project.

https://maven.apache.org/archetype/maven-archetype-plugin/

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


  org.apache.maven.plugins
  maven-archetype-plugin
  3.0.0


You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-archetype-plugin/download.cgi

Release Notes - Maven Archetype - Version 3.0.0

** Bug
* [ARCHETYPE-283] - archetype:generate does not use   
in settings.xml when looking for archetype-catalog.xml

* [ARCHETYPE-358] - Following mirror configuration from settings.xml
* [ARCHETYPE-488] - Goal integration-test of maven-archetype-plugin  
fails with 'Cannot run additions goals." in version 3.3.1
* [ARCHETYPE-499] - Files with no extension are not included when one  
creates archetype from project

* [ARCHETYPE-501] - Bug generating project with blank property
* [ARCHETYPE-502] - XMLOutputter generates files with inconsistent  
line ending on Windows
* [ARCHETYPE-503] - Unit tests with archetype-post-generate.groovy  
fail on Windows

* [ARCHETYPE-504] - Property excludePatterns is in required properties
* [ARCHETYPE-509] - RequiredProperty not set in batch mode
* [ARCHETYPE-510] - Achetype 1.0.x descriptor documentation is not  
generated any more
* [ARCHETYPE-513] - Files in excludePatterns having a default filtered  
extension are still included

* [ARCHETYPE-517] - Maven doesn't fail if invocation goals fail

** Improvement
* [ARCHETYPE-204] - Add option to use remote repositories that are  
password protected

* [ARCHETYPE-241] - Filtering of directory name same as filenames
* [ARCHETYPE-438] - Remove support for specifying catalogs through  
direct URLs

* [ARCHETYPE-439] - Remove archetypeRepository param
* [ARCHETYPE-472] - Upgrade Apache Velocity Engine to 1.7
* [ARCHETYPE-491] - Allow to run integration test with another  
archetype as parent project

* [ARCHETYPE-496] - Allow user to specify archetype tests in project
* [ARCHETYPE-514] - Tests fail with empty repository and 'mvn verify'
* [ARCHETYPE-515] - Migrate plugin to Maven3

** New Feature
* [ARCHETYPE-487] - Input validation for required properties defined  
in artifact descriptor
* [ARCHETYPE-494] - Provide a way to change the generated project  
after archetype:generate execution


** Task
* [ARCHETYPE-433] - Remove unused archetype registry stuff
* [ARCHETYPE-434] - Fix cyclic dependency between archetype-common and  
maven-archetype-plugin

* [ARCHETYPE-437] - Remove support for the create goal

Enjoy,

-The Apache Maven team

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

[RESULT] [VOTE] Release Apache Maven Archetype (Plugin) version 3.0.0

[Robert Scholte]

Hi,

The vote has passed with the following result:

+1 : Robert Scholte, Olivier Lamy, Karl Heinz Marbaise

PMC quorum: reached

I will promote the artifacts to the central repo.

On Wed, 08 Feb 2017 18:17:32 +0100, Robert Scholte   
wrote:



Hi,

We solved 27 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122=12330297=Text

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

Staging repo:
https://repository.apache.org/content/repositories/maven-1322
https://repository.apache.org/content/repositories/maven-1322/org/apache/maven/archetype/maven-archetype/3.0.0/maven-archetype-3.0.0-source-release.zip

Source release checksum(s):
maven-archetype-3.0.0-source-release.zip sha1:  
2be3f477ce00a159358737fe7ce83ffba76de5b0


Staging site:
https://maven.apache.org/archetype-archives/archetype-LATEST/

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

Vote open for at least 72 hours.

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

-
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: I think we are ready for 3.5.0-alpha-1

[Christian Schulte]

@Stephen: Are there any Jenkins jobs left running the plugin ITs with
current Maven master? Surefire has it's own git repository. Do we have
some Jenkins job for this as well? It's important to run all those ITs
(plugins from subversion and the ones with theire own repository) with
what we are going to release as 3.5.0 before releasing it.

Regards,
-- 
Christian


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

Re: I think we are ready for 3.5.0-alpha-1

[Christian Schulte]

This is what happens when building (mvn verify -X -l surefire.log) the
2.19.1 tag with current Maven master.

Failed tests:
testForkModeOncePerThreadSingleThread(org.apache.maven.surefire.its.ForkModeTestNGIT):
pid 1 didn't match pid 2 expected:<[18462]@t60.schulte.it test...> but
was:<[55738]@t60.schulte.it test...>

testForkModeOncePerThreadTwoThreads(org.apache.maven.surefire.its.ForkModeTestNGIT):
number of different pids is not as expected expected:<2> but was:<3>

testSecurityManager(org.apache.maven.surefire.its.jiras.Surefire34SecurityManagerIT):
wrong number of errors expected:<1> but was:<0>

shouldNotBeVerbose(org.apache.maven.surefire.its.CheckTestNgReportTestIT):
log pattern does not match nTimes(..)

testForkModeOncePerThreadSingleThread(org.apache.maven.surefire.its.ForkModeIT):
pid 1 didn't match pid 2 expected:<[48251]@t60.schulte.it test...> but
was:<[52396]@t60.schulte.it test...>

testForkModeOncePerThreadTwoThreads(org.apache.maven.surefire.its.ForkModeIT):
number of different pids is not as expected expected:<2> but was:<3>

I'll send the log file in a separate private mail. It's nearly 1MB of
size (gzipped).

Regards,
-- 
Christian



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

Re: I think we are ready for 3.5.0-alpha-1

[Michael Osipov]

Am 2017-02-12 um 13:45 schrieb Christian Schulte:

Am 02/12/17 um 11:29 schrieb Michael Osipov:

Am 2017-02-12 um 06:53 schrieb Tibor Digana:

What surefire tag exactly?


I know understand what he wants now, use Maven 3.3.9/3.5.0-SNAPSHOT and
build 2.12.4 and 2.19.1 (default-bindings.xml) on FreeBSD with OpenJDK 7.


Yes. Just 2.19.1. Can you build that tag on FreeBSD successfully. I am
getting IT failures. That's why I started to look into surefire. Haven't
checked 2.12.4, though. Will do that now.


This is what I have:

Test 1 (3.3.9, both tags):
===

[mosipov@bsd10 ~/Projekte/maven-surefire]$ mvn -v
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-10T17:41:47+01:00)
Maven home: /usr/local/apache-maven-3.3.9
Java version: 1.7.0_111, vendor: Oracle Corporation
Java home: /usr/local/openjdk7/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "freebsd", version: "10.3-release-p11", arch: "amd64", family: "unix"
[mosipov@bsd10 ~/Projekte/maven-surefire]$ git branch
* (HEAD losgelöst bei surefire-2.19.1)
  master
[mosipov@bsd10 ~/Projekte/maven-surefire]$ mvn clean verify -Prun-its
...
[INFO] Maven Surefire Integration Tests ... SUCCESS [  01:24 h]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 01:33 h
[INFO] Finished at: 2017-02-12T13:07:40+01:00
[INFO] Final Memory: 51M/212M
[INFO] 
[mosipov@bsd10 ~/Projekte/maven-surefire]$ git branch
* (HEAD losgelöst bei surefire-2.12.4)
  master
[mosipov@bsd10 ~/Projekte/maven-surefire]$ mvn clean verify -Prun-its
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ surefire-api ---
[INFO] Surefire report directory: 
/usr/home/mosipov/Projekte/maven-surefire/surefire-api/target/surefire-reports
[INFO] Using configured provider org.apache.maven.surefire.junit.JUnit3Provider
[INFO] Using configured provider 
org.apache.maven.surefire.shadefire.junit.JUnit3Provider

---
 T E S T S
---
Fehler: Hauptklasse org.apache.maven.surefire.booter.ForkedBooter konnte nicht 
gefunden oder geladen werden

Results :

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

[INFO] Maven Surefire Integration Tests ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 11.366 s
[INFO] Finished at: 2017-02-12T13:23:37+01:00
[INFO] Final Memory: 24M/58M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project 
surefire-api: Error occurred in starting fork, check output in log -> [Help 1]

===

Test 2 (3.5.0-SNAPSHOT from MNG-6169, both tags):
===

[mosipov@bsd10 ~/Projekte/maven-surefire]$ git branch
* (HEAD losgelöst bei surefire-2.12.4)
  master
[mosipov@bsd10 ~/Projekte/maven-surefire]$ 
~/apache-maven-3.5.0-SNAPSHOT/bin/mvn clean verify -Prun-its
[INFO] Using configured provider 
org.apache.maven.surefire.shadefire.junit.JUnit3Provider

---
 T E S T S
---
Fehler: Hauptklasse org.apache.maven.surefire.booter.ForkedBooter konnte nicht 
gefunden oder geladen werden

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] Maven Surefire Integration Tests ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 11.879 s
[INFO] Finished at: 2017-02-12T13:44:38+01:00
[INFO] Final Memory: 22M/53M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project 
surefire-api: Error occurred in starting fork, check output in log -> [Help 1]
[mosipov@bsd10 ~/Projekte/maven-surefire]$ git branch
* (HEAD losgelöst bei surefire-2.19.1)
  master
[mosipov@bsd10 ~/Projekte/maven-surefire]$ 
~/apache-maven-3.5.0-SNAPSHOT/bin/mvn clean verify -Prun-its
Failed tests:   
testForkModeOncePerThreadSingleThread(org.apache.maven.surefire.its.ForkModeTestNGIT): pid 
1 didn't match pid 2 expected:<111[70]@bsd10.local testVal...> but 
was:<111[69]@bsd10.local testVal...>
  

[GitHub] maven-surefire issue #142: SUREFIRE-1330: Import provider code donated by JU...

[britter]

Github user britter commented on the issue:

https://github.com/apache/maven-surefire/pull/142
  
Thank you! I will continue then with the detection code in 
ABstractSurefireMojo.


---
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: I think we are ready for 3.5.0-alpha-1

[Christian Schulte]

Am 02/12/17 um 11:29 schrieb Michael Osipov:
> Am 2017-02-12 um 06:53 schrieb Tibor Digana:
>> What surefire tag exactly?
> 
> I know understand what he wants now, use Maven 3.3.9/3.5.0-SNAPSHOT and 
> build 2.12.4 and 2.19.1 (default-bindings.xml) on FreeBSD with OpenJDK 7.

Yes. Just 2.19.1. Can you build that tag on FreeBSD successfully. I am
getting IT failures. That's why I started to look into surefire. Haven't
checked 2.12.4, though. Will do that now.


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

Re: [VOTE] Release Apache Maven Archetype (Plugin) version 3.0.0

[Karl Heinz Marbaise]

Hi,

tested with Maven 3.0.5, 3.1.1, 3.2.5, 3.3.9

without any issue.

so +1 from me..

Kind regards
Karl Heinz Marbaise

On 08/02/17 18:17, Robert Scholte wrote:

Hi,

We solved 27 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122=12330297=Text


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


Staging repo:
https://repository.apache.org/content/repositories/maven-1322
https://repository.apache.org/content/repositories/maven-1322/org/apache/maven/archetype/maven-archetype/3.0.0/maven-archetype-3.0.0-source-release.zip


Source release checksum(s):
maven-archetype-3.0.0-source-release.zip sha1:
2be3f477ce00a159358737fe7ce83ffba76de5b0

Staging site:
https://maven.apache.org/archetype-archives/archetype-LATEST/

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

Vote open for at least 72 hours.

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


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

Re: [VOTE] Release Apache Maven Archetype (Plugin) version 3.0.0

[Olivier Lamy]

+1

On Thu, 9 Feb 2017 at 4:17 am, Robert Scholte  wrote:

> Hi,
>
> We solved 27 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122=12330297=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317122%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1322
>
> https://repository.apache.org/content/repositories/maven-1322/org/apache/maven/archetype/maven-archetype/3.0.0/maven-archetype-3.0.0-source-release.zip
>
> Source release checksum(s):
> maven-archetype-3.0.0-source-release.zip sha1:
> 2be3f477ce00a159358737fe7ce83ffba76de5b0
>
> Staging site:
> https://maven.apache.org/archetype-archives/archetype-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: I think we are ready for 3.5.0-alpha-1

[Michael Osipov]

Am 2017-02-12 um 06:53 schrieb Tibor Digana:

What surefire tag exactly?


I know understand what he wants now, use Maven 3.3.9/3.5.0-SNAPSHOT and 
build 2.12.4 and 2.19.1 (default-bindings.xml) on FreeBSD with OpenJDK 7.



On Sun, Feb 12, 2017 at 1:56 AM, Christian Schulte [via Maven] <
ml-node+s40175n5898195...@n5.nabble.com> wrote:


Am 02/12/17 um 00:59 schrieb Michael Osipov:


Am 2017-02-12 um 00:49 schrieb Christian Schulte:

Am 02/11/17 um 23:03 schrieb Michael Osipov:

The lifecylce plugins have been moved to MNG-6169. MPLUGIN has been
retained with 3.3 because there were failures. One IT is failing,
MNG-5572. I am looking into the cause right now.


Out of curiosity. @Michael: Do you have a FreeBSD box or something else
BSD at hand? Can you build the surefire tag of that version locally
without any issues? I am getting IT failures on OpenBSD here. On

Jenkins

nothing is failing. Would be interesting how that looks on FreeBSD.


Yes, sure. FreeBSD is my main Unix test platform. So you want me to run
ITs with MNG-6169, is that right?


No. A surefire build of the tag corresponding to the version in core.
That build will run various surefire related ITs. Can you build that
surefire tag successfully?


-
To unsubscribe, e-mail: [hidden email]

For additional commands, e-mail: [hidden email]




--
If you reply to this email, your message will be added to the discussion
below:
http://maven.40175.n5.nabble.com/I-think-we-are-ready-for-3-5-0-alpha-1-
tp5897626p5898195.html
To start a new topic under Maven Developers, email
ml-node+s40175n142166...@n5.nabble.com
To unsubscribe from Maven Developers, click here

.
NAML







--
View this message in context: 
http://maven.40175.n5.nabble.com/I-think-we-are-ready-for-3-5-0-alpha-1-tp5897626p5898200.html
Sent from the Maven Developers mailing list archive at Nabble.com.




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