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

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

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

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

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

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] <

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

+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: > >

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

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

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

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

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

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

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

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:

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

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

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

@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

[ANN] Apache Maven Archetype Plugin 3.0.0 Released

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.

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

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 > >

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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,

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

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

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

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

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

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

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

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:

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

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

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

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 >