Re: What to do with the 6 issues left as 3.5.0-candidates?

Am 03/25/17 um 07:17 schrieb Hervé BOUTEMY: > MNG-6112 is harder to estimate side effects IMHO > and since this has been available for a long time, I'm really not satisfied > that it has been integrated *after vote for 3.0.5-beta-1 started* (and in > addition without any discussion) Issue has

Re: What to do with the 6 issues left as 3.5.0-candidates?

We really need Solaris and OSX Jenkins build nodes :-) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: What to do with the 6 issues left as 3.5.0-candidates?

Am 03/25/17 um 01:30 schrieb Christian Schulte: > Am 03/24/17 um 23:28 schrieb Stephen Connolly: >> Keep in mind that AIUI we aim to be BourneShell compatible in which case $( >> ) is not available > > Thanks for pointing this out. Our launchers have this in the first

Re: What to do with the 6 issues left as 3.5.0-candidates?

Am 03/24/17 um 23:28 schrieb Stephen Connolly: > Keep in mind that AIUI we aim to be BourneShell compatible in which case $( > ) is not available Thanks for pointing this out. Our launchers have this in the first line: #!/bin/sh /bin/sh should be a POSIX compatible shell. On the BSDs, OSX and

Re: What to do with the 6 issues left as 3.5.0-candidates?

Am 03/24/17 um 22:51 schrieb Stephen Connolly: > I am concerned that there are some quoting issues in mvn. > > In some cases we use var=`command` and in others we use var="`command`" > > Additionally we have a mixture of backtick and $(...) style. My > understanding is that the backticks are for

Re: What to do with the 6 issues left as 3.5.0-candidates?

Am 03/24/17 um 11:45 schrieb Stephen Connolly: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.5.0-candidate%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > Here is my opinions: > >

Re: [VOTE] Release Apache Maven 3.5.0-beta-1

Am 03/24/17 um 16:54 schrieb Karl Heinz Marbaise: > Hi, > > On 24/03/17 02:17, Hervé BOUTEMY wrote: >> we have absolutely no OSX user building Maven core ITs on his personal >> computer? >> seriously? >> Or is there no core IT that shows the issue? then it has to be discovered by >> hand? > > I

Re: [VOTE] Release Apache Maven 3.5.0-beta-1

Am 03/23/17 um 19:20 schrieb Christian Schulte: > Am 03/23/17 um 10:08 schrieb Stephen Connolly: >> Hervé do you think this ordering issue is serious enough to drop and run a >> beta-2? >> >> IMHO no as it is just a beta and we can add it as a known issue in the >&

Re: [VOTE] Release Apache Maven 3.5.0-beta-1

Am 03/23/17 um 10:08 schrieb Stephen Connolly: > Hervé do you think this ordering issue is serious enough to drop and run a > beta-2? > > IMHO no as it is just a beta and we can add it as a known issue in the > release notes. Unrelated to this issue there has been another report regarding the

Re: [2/2] maven git commit: [MNG-6113] Rename the 'Central Repository' to 'Maven Central Repository' in the 4.0.0 super POM.

Am 03/21/17 um 19:44 schrieb Hervé BOUTEMY: > -1 > > see MNG-5164 Thanks for pointing this out. I closed the issue "Won't Fix" and flagged it a duplicate of MNG-5164. Branch is dropped. This would have went unnoticed into the 3.4.0 release :-). Regards, -- Christian

Re: maven-3.x-jenkinsfile/MNG-6112 - build #1 - null

Am 03/21/17 um 03:57 schrieb Apache Jenkins Server: > See https://builds.apache.org/job/maven-3.x-jenkinsfile/job/MNG-6112/1/ > Seems "null" does not always indicate a successful build. Can someone take a look at this please and maybe update the Jenkinsfile to have a subject indicating failures

Re: @since 3.5.0-alpha-2

Am 03/20/17 um 20:25 schrieb Stephen Connolly: > Hervé requested to go straight to beta. > > Since tags should be for the official release not alphas or betas imho Ok. I'll update some since tags to 3.5.0 before the next release. No need for a JIRA issue, right? Regards, -- Christian

@since 3.5.0-alpha-2

There will be no alpha-2? Should I update those @since tags to match the new beta-1 name? Maybe something to add to the other discussions. Regards, -- Christian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For

Re: [DISCUSS] Planning process for 3.5.1

Am 03/19/17 um 12:43 schrieb Stephen Connolly: > So planning for 3.5.0 was total chaos... but it seems to have worked. > > How do we want to work for 3.5.1? We need to answer all the other questions first (versioning, bug vs. feature, branches, etc.). Question is: How to decide which

Re: [DISCUSS] Towards a common understanding of things

Am 03/20/17 um 01:47 schrieb Christian Schulte: > Am 03/20/17 um 01:11 schrieb Stephen Connolly: >> On Sun 19 Mar 2017 at 12:13, Stephen Connolly < >> stephen.alan.conno...@gmail.com> wrote: >> >>> We need to define: >>> >>> * what is a

Re: [DISCUSS] Towards a common understanding of things

Am 03/20/17 um 01:11 schrieb Stephen Connolly: > On Sun 19 Mar 2017 at 12:13, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> We need to define: >> >> * what is a bug vs what is an rfe >> >> * what are the different severities for bugs and rfes >> > > S1: software is unusable,

Re: [DISCUSS] How to work with branches

Am 03/19/17 um 18:34 schrieb Stephen Connolly: > Unlike the other discuss threads, I think I have some extra context that > means I am going to start from my proposal... or rather my requirements and > then proposal to solve those requirements. > > Requirements > === > > As a Release

Re: [DISCUSS] Towards a common understanding of things

Am 03/19/17 um 23:32 schrieb Hervé BOUTEMY: > for you, documentation is always right? > That's the first time I see that documentation is more important and always > more accurate than how the tool works > > If there is a discrepency between how the tool works and what is written in >

Re: [DISCUSS] Towards a common understanding of things

Am 19.03.2017 um 13:13 schrieb Stephen Connolly: > We need to define: > > * what is a bug vs what is an rfe I'll give it a try. Everything not working as documented/specified is a bug, when there is consensus the documentation/specification is stating the intended/correct behaviour. The design

Re: [DISCUSS] Towards a common understanding of things

Am 19.03.2017 um 13:13 schrieb Stephen Connolly: > We need to define: > > * what is a bug vs what is an rfe > > * what are the different severities for bugs and rfes > > * what severity bugs block: an alpha, a beta, a full release > > * what do the different release types mean? (My take, alpha

Re: Distribution file permission issue with current master.

Am 19.03.2017 um 10:39 schrieb Hervé BOUTEMY: > I updated parent pom, which brings a new m-assembly-p version that does not > have this bug Thanks. Regards, -- Christian - To unsubscribe, e-mail:

Re: Distribution file permission issue with current master.

Am 03/15/17 um 23:37 schrieb Hervé BOUTEMY: > no issue for me on Linux > I don't understand what happens to you: I suppose this is once again related > to FreeBSD > I can't do anything for you Upgrading the assembly plugin to 2.6 solves this. Should we consider upgrading the parent for alpha-2

Re: [08/17] maven git commit: [MNG-6182] ModelResolver interface enhancements.

Branch name is MNG-6182 Commit is Should I create a separate JIRA issue for this? Regards, --

Re: [08/17] maven git commit: [MNG-6182] ModelResolver interface enhancements.

Am 03/18/17 um 14:04 schrieb Stephen Connolly: > Given that these new methods actually have implementations, could we see > about having at least a unit test of the new code - since it will not be > covered by any test. There would be an integration test for the code. Since nothing uses it, no

Re: Distribution file permission issue with current master.

Am 03/18/17 um 20:33 schrieb Christian Schulte: > Am 03/18/17 um 20:33 schrieb Christian Schulte: >> Am 03/15/17 um 23:37 schrieb Hervé BOUTEMY: >>> no issue for me on Linux >>> I don't understand what happens to you: I suppose this is once again >>> re

Re: Distribution file permission issue with current master.

Am 03/18/17 um 20:33 schrieb Christian Schulte: > Am 03/15/17 um 23:37 schrieb Hervé BOUTEMY: >> no issue for me on Linux >> I don't understand what happens to you: I suppose this is once again related >> to FreeBSD >> I can't do anything for you > > I am

Re: Distribution file permission issue with current master.

Am 03/15/17 um 23:37 schrieb Hervé BOUTEMY: > no issue for me on Linux > I don't understand what happens to you: I suppose this is once again related > to FreeBSD > I can't do anything for you I am having the same issue on Jenkins with Linux, BTW. Seems the "unzip" command cannot handle our ZIPs

Re: Maven Resolver 1.1

Am 03/15/17 um 23:31 schrieb Hervé BOUTEMY: > it would be great if MNG-6183 description included a sample debug message > before the change and after the change: I can't get what this change is about > really Will update the issue. > And of course, I don't get the next step with Resolver

Re: Distribution file permission issue with current master.

Am 03/15/17 um 23:37 schrieb Hervé BOUTEMY: > no issue for me on Linux > I don't understand what happens to you: I suppose this is once again related > to FreeBSD > I can't do anything for you Thanks for taking a look. It's happening with the zip distribution only. It's not happening using the

Re: Release build failing with current master (was Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass a release build)

Am 03/15/17 um 23:00 schrieb Robert Scholte: > The javadoc-fix is easy, but the result of modello-maven-plugin:1.9.0:xdoc > now causes issues because html4 is not the same as balanced xml. Need to > think about how to fix this. > Maybe this commit should be reverted. Cannot tell. Stephen? Can

Re: Release build failing with current master (was Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass a release build)

Am 03/15/17 um 22:30 schrieb Robert Scholte: > ok, so that argument should be moved to a java8 activated profile. Can you do this, please? Regards, -- Christian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For

Re: Release build failing with current master (was Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass a release build)

Am 03/15/17 um 21:50 schrieb Michael Osipov: > Am 2017-03-15 um 21:39 schrieb Christian Schulte: >> Hi, >> >> this is a real issue. A release build using JDK 7 with current master is >> not possible. See >> >> <https://builds.apache.org/view/Maven%20

Release build failing with current master (was Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass a release build)

Hi, this is a real issue. A release build using JDK 7 with current master is not possible. See Exit code: 1 - javadoc: error - invalid flag: -Xdoclint:none Regards, --

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Am 03/14/17 um 01:27 schrieb Jeff Jensen: >> The date of the commit is not the date it got committed to master, but the > date it got committed to some branch, no longer existing after the commit. > If this is the way GIT works, so be it. I just don't like it. It could not > be more confusing. >

Distribution file permission issue with current master (attachment).

$ rm -rf apache-maven-3.5.0-SNAPSHOT rm: apache-maven-3.5.0-SNAPSHOT/lib/jansi-native: Permission denied rm: apache-maven-3.5.0-SNAPSHOT/lib: Directory not empty rm: apache-maven-3.5.0-SNAPSHOT: Directory not empty $ find apache-maven-3.5.0-SNAPSHOT apache-maven-3.5.0-SNAPSHOT

Distribution file permission issue with current master.

Hi, see the attachment. After unzipping the binary distribution, I cannot delete it anymore without updating file permissions. Regards, -- Christian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional

Re: Timeline for 3.5.0-alpha-2 / MNG-6057

Am 03/14/17 um 21:24 schrieb Stephen Connolly: > Not so easy. Was attempted before and hit issues with gpg signing. Can you remember what issues that were? It will sign the temporary pom java.io.File the same way the install plugin will install that and the deploy plugin will deploy that.

Re: Maven Resolver 1.1

Am 03/14/17 um 21:24 schrieb Christian Schulte: > Hi, > > are there any plans to release another Maven Resolver 1.0.x? Can I > update the POMs to 1.1-SNAPSHOT? See the comments I added in this > commit: > <https://git-wip-us.apache.org/repos/asf?p=mav

Maven Resolver 1.1

Hi, are there any plans to release another Maven Resolver 1.0.x? Can I update the POMs to 1.1-SNAPSHOT? See the comments I added in this commit: I would need to add some methods to the

Re: Timeline for 3.5.0-alpha-2 / MNG-6057

Am 12.03.2017 um 15:36 schrieb Karl Heinz Marbaise: > Hi, > > So after I finalized the implementation which seemed to be ok for > now...the IT's are currently not working based on particular reason > (explanations later). > > I would like to know the opinion of the Maven DEV's about this: > >

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Am 03/11/17 um 22:56 schrieb Stephen Connolly: > Hi all, > > I think it is a good thing if we take stock of where we are and how we are > doing. I would really appreciate if everyone could take a few minutes to > respond with their top three of two areas: > > * What is working well The Jenkins

Contributing Javadoc (was Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1)

Am 03/13/17 um 23:22 schrieb Laird Nelson: > On Mon, Mar 13, 2017 at 2:26 PM Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > Gentle reminder. If you can see this thread, you are entitled to > contribute. This thread is about discovering where the Maven project can > improve how

Re: Timeline for 3.5.0-alpha-2 / MNG-6057

Am 03/13/17 um 08:33 schrieb Hervé BOUTEMY: >> The flatten-maven-plugin solution appears to me like a workaround for >> some missing support in Maven core. Also a good reason to split build >> pom from deployed pom. Maybe all of this better be postponed to model >> version 5.0.0? > splitting build

Re: Timeline for 3.5.0-alpha-2 / MNG-6057

Am 03/12/17 um 15:36 schrieb Karl Heinz Marbaise: > Hi, > > So after I finalized the implementation which seemed to be ok for > now...the IT's are currently not working based on particular reason > (explanations later). > > I would like to know the opinion of the Maven DEV's about this: > >

Re: maven git commit: [MNG-6182] ModelResolver interface enhancements.

Am 03/10/17 um 23:33 schrieb Christian Schulte: > Am 03/10/17 um 20:16 schrieb Robert Scholte: >> On Fri, 10 Mar 2017 16:47:45 +0100, Christian Schulte <c...@schulte.it> >> wrote: >> >>> Am 03/10/17 um 10:42 schrieb Robert Scholte: >>>> Having a c

Re: maven git commit: [MNG-6182] ModelResolver interface enhancements.

Am 03/10/17 um 20:16 schrieb Robert Scholte: > On Fri, 10 Mar 2017 16:47:45 +0100, Christian Schulte <c...@schulte.it> > wrote: > >> Am 03/10/17 um 10:42 schrieb Robert Scholte: >>> Having a closer look at this commit, I actually don't like the idea that

Re: maven git commit: [MNG-6182] ModelResolver interface enhancements.

Am 03/10/17 um 10:42 schrieb Robert Scholte: > Having a closer look at this commit, I actually don't like the idea that > ModelResolver now supports versionRanges. > IMO the version should always be specific *before* resolving the model. > IIUC correctly this is required to supported

Re: Timeline for 3.5.0-alpha-2

Am 03/10/17 um 00:29 schrieb Stephen Connolly: > How are we doing? > > Are we ready to freeze? Nothing left to do on my side. There are a couple of issues in JIRA flagged "in progress" for -alpha-2. Not sure about them. - To

[IT MNG-6173] (was Re: Timeline for 3.5.0-alpha-2)

Am 03/04/17 um 14:56 schrieb Stephen Connolly: > We are still in alpha, so bugs with severity S1-S3 are eligible (and S4 > with a risk assessment) > Severity is something like this (but as a project we probably need to > define the categories for Maven core) > > S1: blows up for everyone, no

Re: Timeline for 3.5.0-alpha-2

Am 03/04/17 um 18:54 schrieb Hervé BOUTEMY: > I have one question, which is recurring for every issue: what is the impact? > > I understand the logic: it should fix a bug (that is told introduced in Maven > 3.3.1), and the bug is explained by the logic behind the javadoc. > But no pointer to any

Re: Timeline for 3.5.0-alpha-2

Am 03/04/17 um 18:54 schrieb Hervé BOUTEMY: > I have one question, which is recurring for every issue: what is the impact? > > I understand the logic: it should fix a bug (that is told introduced in Maven > 3.3.1), and the bug is explained by the logic behind the javadoc. > But no pointer to any

Re: Timeline for 3.5.0-alpha-2

Am 03/02/17 um 22:55 schrieb Stephen Connolly: > I'd like to declare feature freeze for alpha-2 on March 9th. > > If a feature does not land in alpha-2 it will not be in beta-1 (i.e. Only bug > fixes or rip out features that are causing S1/S2 issues will be in the diff > from alpha-2 to beta-1)

Re: [DISCUSS] 3.5.0 alpha/beta's on Central

Am 02/26/17 um 13:03 schrieb Stephen Connolly: > Even if we had a -1 as long as I have the binding votes *as release > manager* it would be my call whether to release or not. > > Now *personally* I much rather release with consensus, but any committer > can step up to be release manager for any

Re: [DISCUSS] 3.5.0 alpha/beta's on Central

Am 02/25/17 um 22:55 schrieb Karl Heinz Marbaise: > Hi, > > based on the started discussion about either to bring 3.5.0-alpha-1 to > Central or not I would suggest to discuss in a separate thread and > prevent using the VOTE's threads for that (as Stephen already mentioned). > > Using Central:

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

Am 02/25/17 um 17:25 schrieb Tibor Digana: >>> There are two commits for MNG-6078 part of -alpha-1. > > This was caused by system property duplicates in surefire ITs. > It is already fixed in a branch SUREFIRE_SYSPROP_DUPLICATES. If something works with 3.3.9 but not 3.5.0, we need to fix it in

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

Am 02/25/17 um 14:40 schrieb Tibor Digana: > @Stephen > @Michael-O > What changed in Maven after Michael used his snapshot version of > Maven-3.5.0-SNAPSHOT? > Michael said that surefire failed with ForkModeIT and he tested Surefire's > commits from HEAD to

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

Am 02/24/17 um 21:03 schrieb Stephen Connolly: > To reflect the practice we should use for these going forward +1 I should have included -alpha-0 in those ranges right from the start. Regards, -- Christian - To unsubscribe,

Re: maven-integration-testing git commit: 3.5.0-alpha-1 < 3.5.0

Am 02/24/17 um 20:48 schrieb steph...@apache.org: > Repository: maven-integration-testing > Updated Branches: > refs/heads/master 3883e005e -> c4cd8cf3b > > > 3.5.0-alpha-1 < 3.5.0 Thanks. - To unsubscribe, e-mail:

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

Am 02/24/17 um 18:34 schrieb Robert Scholte: > When running the maven-its, I get this failing test. I think the cause is > an invalid version range, right? Are you really running the IT master branch? There have been no commits to maven master without a successful IT run before. I wonder how

Escaping rules for filtering.

Hi, during testing various projects to build from inside a directory "Spaces & Special Char" I stumbled upon an issue also reported by users over the years. I'd like to know the status on this. Do we plan to implement any kind of escaping rules for filtering? Based on what? File extension? MIME

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

Can we have this patch included? I wanted to commit this to master yesterday when the build job succeeded. This is just pending the Jenkins update to get the job succeed. I would just merge it to master now.

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

Am 02/23/17 um 19:20 schrieb Michael Osipov: > So guys, > > I took a different approach to provide Tibor more information about the > failures. First of all, I added another platform for the test which is > exotic: HP-UX 11.31. The VM comes directly from HPE which is a > repackaged Oracle JVM.

Re: maven-3.x-jenkinsfile/master - build #54 - null

Am 02/23/17 um 09:07 schrieb Stephen Connolly: > Yes. Infra updated some Jenkins plugins and now the Windows path is too > long. > > I need them to upgrade to branch-api 2.0.7 (released yesterday) and set a > system property to resolve the issue Good to know. I updated various build jobs of the

Re: maven-3.x-jenkinsfile/master - build #54 - null

Am 02/23/17 um 06:18 schrieb Apache Jenkins Server: > See https://builds.apache.org/job/maven-3.x-jenkinsfile/job/master/54/ > Turns out the "null" in the subject does not indicate a successful build. Maven master currently does not build successfully. Regards, -- Christian

Re: Launcher script issues in 3.5.0.

Am 02/23/17 um 04:21 schrieb Igor Fedorenko: > On all platforms .mvn/ search is expected to start with directory > specified by -f parameter and keep doing "cd .." until it files .mvn/ > subdirectory or hits the filesystem root. What if I put a .mvn directory at the file system root? Will that

Re: Launcher script issues in 3.5.0.

Both issues seem to be related to MNG-5889. MNG-5889 branch created. If no one objects, I'll merge it to master when the build job completed successfully on Jenkins. Otherwise consider the MNG-5889 branch yours. Note: I just noticed that the Windows launcher does not stop searching for the .mvn

Re: Build of maven-dependency-analyzer fails on Windows.

Am 02/20/17 um 18:28 schrieb Robert Scholte: > On Mon, 20 Feb 2017 02:17:12 +0100, Christian Schulte <c...@schulte.it> > wrote: > >> Am 02/20/17 um 01:53 schrieb Christian Schulte: >>> Hi, >>> >>> I cannot build 'maven-dependency-analyzer' trunk

Re: Launcher script issues in 3.5.0.

Please see the attachment. Can someone please review this and apply the patches. Both launchers - Windows and Unix - should support directory names like "Spaces & Special Char" with this patch applied. I do not know what JIRA issue corresponds to these changes. Regards, -- Christian diff --git

Re: Launcher script issues in 3.5.0.

See the attached patch. This should make the Unix launcher support directory names like "Spaces & Special Char". At least here: SH_VERSION='@(#)PD KSH v5.2.14 99/07/13.2' Can someone review and apply this patch please. Thanks. Regards, -- Christian diff --git a/apache-maven/src/bin/mvn

Launcher script issues in 3.5.0.

Hi, our launchers (both Unix and Windows) still seem to be broken for directory names like "Spaces & Special Char". pwd /home/schulte $ mvn -version Apache Maven 3.5.0-SNAPSHOT (e6217a455547e5b3bcac310be18daf2a333cd5d1; 2017-02-21T01:24:24+01:00) Maven home:

Re: Fwd: How to name modules, automatic and otherwise

Am 02/19/17 um 04:38 schrieb Hervé BOUTEMY: > then I'm not sure checking rules on what is inside an artifact while > publishing in Central is the right thing to do: we don't do it currently > (checking that package names are consistent with groupId), then I feel we > should not do it either for

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

Am 02/20/17 um 01:10 schrieb Tibor Digana: > Can somebody explore what is different between these two surefire builds > (failed and successful) and why?: > https://builds.apache.org/view/Maven%20Master%20Release%20Status/ This one is run with current Maven master using JDK 7. >

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

Am 02/20/17 um 01:10 schrieb Tibor Digana: > I meant this build which is in good conditions > https://builds.apache.org/view/Maven%20Master%20Release%20Status/job/maven-master-release-status-test-surefire-linux/30/console > > Can somebody explore what is different between these two surefire

Re: Build of maven-dependency-analyzer fails on Windows.

Am 02/20/17 um 01:53 schrieb Christian Schulte: > Hi, > > I cannot build 'maven-dependency-analyzer' trunk on Windows. Is there > some dependency I could upgrade to get this going? This is what I am > doing locally: > > svn checkout /repos/asf/maven/shared/trunk/mave

Build of maven-dependency-analyzer fails on Windows.

Hi, I cannot build 'maven-dependency-analyzer' trunk on Windows. Is there some dependency I could upgrade to get this going? This is what I am doing locally: svn checkout /repos/asf/maven/shared/trunk/maven-dependency-analyzer cd maven-dependency-analyzer mvn verify

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

Am 02/20/17 um 01:10 schrieb Tibor Digana: > I meant this build which is in good conditions > https://builds.apache.org/view/Maven%20Master%20Release%20Status/job/maven-master-release-status-test-surefire-linux/30/console This points to a console with IT failures. That build never succeeded on

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

Am 02/19/17 um 23:58 schrieb Tibor Digana: > and they are getting really nervous. So we have to make a release and later > we will finish fix for FreeBSD. I am still facing native problem with > reliably streaming data over standard output streams with subprocess. > We with Kristian Roselvold were

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

Am 19.02.2017 um 21:10 schrieb Michael Osipov: > Am 2017-02-19 um 19:54 schrieb Christian Schulte: >> Am 02/19/17 um 19:52 schrieb Christian Schulte: >>> Am 02/19/17 um 19:47 schrieb Christian Schulte: >>>> Am 02/19/17 um 13:06 schrieb Michael Osipov: >>&

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

"Initially, the standard error stream is unbuffered; " Maybe just use System.err instead of System.out to avoid any buffering, if there is no other solution. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

Am 02/19/17 um 19:52 schrieb Christian Schulte: > Am 02/19/17 um 19:47 schrieb Christian Schulte: >> Am 02/19/17 um 13:06 schrieb Michael Osipov: >>> Socket give you, of course, a lot of control, but they also impose an >>> overhead compares to named pipes (mkfifo,

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

Am 02/19/17 um 19:47 schrieb Christian Schulte: > Am 02/19/17 um 13:06 schrieb Michael Osipov: >> Socket give you, of course, a lot of control, but they also impose an >> overhead compares to named pipes (mkfifo, CreateNamePipe). >> >> I think our biggest proble

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

Am 02/19/17 um 13:06 schrieb Michael Osipov: > Socket give you, of course, a lot of control, but they also impose an > overhead compares to named pipes (mkfifo, CreateNamePipe). > > I think our biggest problem is that stdout is subject to buffering > issues and in case if System#exit() status Z

Re: Fwd: How to name modules, automatic and otherwise

Am 02/18/17 um 12:25 schrieb Robert Scholte: > The idea from Hervé and Rémi is about having a publish rule in Central if > you want to publish a modular jar there which will prevent module name > collisions. > Because the groupId is already owned by a specific organisation, you could > use

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

Am 02/17/17 um 21:48 schrieb Michael Osipov: > Hi folks, > > Christian Schulte asked me a couple of days ago wether I am able to > build Surefire master with Maven master. It was constantly failing for > him on his OpenBSD machines. Since I have several real servers with > F

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

Am 02/18/17 um 11:41 schrieb Stephen Connolly: > We need help testing on Solaris 10/11 if anyone has access to such a system On a SPARC machine, if possible, please. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org

Re: [ANN] feature freeze Maven core 3.5.0

Am 02/18/17 um 12:25 schrieb Stephen Connolly: > Bug fixes only. Let's shake down towards the release. +1 Currently trying to make Jenkins build almost all Maven codebases automatically daily with Maven master. Setup isn't finished yet, though.

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

Am 02/17/17 um 19:18 schrieb Stephen Connolly: > Would it help yet to cut an alpha and start tracking bugs? > > I am starting to be concerned that the collective of volunteers are on a > death march with no end in site... so I am seeking ways to identify an end > where we can cut 3.5.0 and start

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

Am 02/14/17 um 20:25 schrieb Michael Osipov: > Who seconds MNG-6150 Javadoc improvements for 3.5.0 for FIX-3.5.0? > Functional changes, passes all tests. +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For

Re: Build Maven offline

Am 02/13/17 um 17:47 schrieb Guo Yunhe: >> Don't. Don't do the same as done here: >> https://www.rpmfind.net/linux/RPM/fedora/25/s390x/m/maven-3.3.9-6.fc25.noarch.html >> >> The completely disassembled your tarball and build Maven theirselves. This >> is a non-canoncial build which we are likely

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

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

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

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

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

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.

  1   2   3   4   5   6   7   >