[RESULT] [VOTE] Release Maven Resolver version 1.1.0

Hi, The vote has passed with the following result: +1: Michael Osipov, Manfred Moser, Hervé Boutemy, Karl Heinz Marbaise, Olivier Lamy, Tamás Cservenák PMC quorum: reached I will promote the artifacts to the central repo, the source release ZIP file and add this release the board report

Re: [MNG-6130] Loss of profile information in workaround for MNG-4900

Osipov <micha...@apache.org> wrote: Am 2017-05-15 um 22:29 schrieb Michael Osipov: Am 2017-05-15 um 22:10 schrieb Robert Scholte: I think I miss a unittest or integration-test, just to be sure. The reporter says: "It's very tricky and hopefully not necessary, since the 1-line fix

Re: Expected speed of commit over HTTP?

Am 2017-07-06 um 13:16 schrieb Paul Hammant: For something that's 500MB in size (random binary data) I'm experiencing commits taking 10x longer than a straight copy to the drive the Svn repo is on. Both timings are on the same Ubuntu 17.04 machine, with the boot drive being the starting

Re: [ANN] First call to round up issues for 3.5.1

Some of them are assigned to me. I won't make it before Wednesday but like to address them in 3.5.1. Michael Am 2017-04-27 um 12:55 schrieb Robert Scholte: Let me start going through the list of candidates: Maven - Version 3.5.1-candidate ** Sub-task * [MNG-6186] - switch to improved

Re: Re: [ANN] First call to round up issues for 3.5.1

> Gesendet: Freitag, 28. April 2017 um 02:08 Uhr > Von: "Hervé BOUTEMY" > An: "Maven Developers List" > Betreff: Re: [ANN] First call to round up issues for 3.5.1 > > > * [MNG-6186] - switch to improved HawtJNI > > Robert: Improvements have not

Re: Maven JIRA Projects - Issue Type

Am 2017-08-18 um 20:59 schrieb Robert Scholte: I like the idea of having our own scheme for all projects. That will also give the option to remove types like "Question"; now once used we're always asking them to use other ways to get an answer. But it is an option, so it is kind of valid to

Re: [ANN] First call to round up issues for 3.5.1

Am 2017-05-02 um 14:13 schrieb Jon Harper: Hi, https://issues.apache.org/jira/browse/MNG-6184 (a.k.a. https://issues.apache.org/jira/browse/MNG-5592 ) still affects maven today. It's an old bug so the fix could be delayed, but it is relevant now because the bug is in the aether code that was

Re: [MNG-6169] Lifecycle/binding plugin version updates

Am 2017-05-13 um 00:30 schrieb Hervé BOUTEMY: Le vendredi 12 mai 2017, 13:50:37 CEST Michael Osipov a écrit : Am 2017-05-12 um 08:25 schrieb Hervé BOUTEMY: Jenkins build is not flaky: it is strict on dependency resolution from cache, which is an intent, not a bug This pretty much explains

Re: [MNG-6169] Lifecycle/binding plugin version updates

Le jeudi 11 mai 2017, 22:30:43 CEST Michael Osipov a écrit : Who seconds MNG-6169 for 3.5.1? I have a fully working branch (MNG-6169_2/not-updated-MJAR-MCOMPILER) passing all ITs on Windows 10 and FreeBSD 10.3-RELEASE. Jenkins build is flaky with notorious file://target/null artifact not fo

Re: Re: [MNG-5567] Zip files are not included in classpaths at all

about the missing > support for zip-files. > > Robert > > On Thu, 11 May 2017 19:45:49 +0200, Michael Osipov <micha...@apache.org> > wrote: > > > Am 2017-05-11 um 19:39 schrieb Jörg Schaible: > >> Michael Osipov wrote: > &g

Re: [VOTE] Release Apache Maven Dependency Plugin version 3.0.1

Am 2017-05-11 um 23:30 schrieb Karl Heinz Marbaise: Hi, We solved 13 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227=12338874 There are still a couple of issues left in JIRA:

Re: [MNG-6169] Lifecycle/binding plugin version updates

Am 2017-05-15 um 09:20 schrieb Stephen Connolly: On Sun 14 May 2017 at 08:51, Hervé BOUTEMY wrote: thank you Robert: this is exactly the logic I was looking for, and explanation of changes over time to improve user experience through reproducibility. Now the question

[MNG-5567] Zip files are not included in classpaths at all

Folks, what to do with this issue? There has been too much discussion about a simple and valid extension. It is actually a no-brainer..ITs are pending... Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org

Re: [MNG-6169] Lifecycle/binding plugin version updates

Am 2017-05-11 um 22:46 schrieb Robert Scholte: Is m-compiler-p on 3.6.1? please change to 3.5.1 until jigsaw stuff works correctly. Yes, it is 3.5.1. I will downgrade to 3.5.1 shortly. Michael Oorspronkelijk bericht Van: Michael Osipov <micha...@apache.org> Datum

Re: [MNG-5567] Zip files are not included in classpaths at all

Am 2017-05-11 um 19:39 schrieb Jörg Schaible: Michael Osipov wrote: Folks, what to do with this issue? There has been too much discussion about a simple and valid extension. It is actually a no-brainer..ITs are pending... I won't call it no-brainer if you scew up existing project setups

Detect optional dependencies in IT (MNG-5935)

Hi folks, I am currently working on an IT for MNG-5935 and see currently no option for optional flag output from the maven-it-plugin-dependency-resolution. Artifact#isOptional() is never printed. Here is the commit:

[MNG-5935] Optional true getting lost in managed dependencies when transitive

Who seconds MNG-5935 for 3.5.1? IT has been added too. Jenkins job is running... Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

[MNG-6228] Optionality not displayed in dependency tree when run in debug mode

Who seconds MNG-6228 for 3.5.1? This is merely debug log statement improvement as a help for MNG-5935. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail:

Re: [VOTE] Release Apache Maven Shared Component: Maven Artifact Transfer version 0.9.1

Am 2017-05-10 um 20:41 schrieb Karl Heinz Marbaise: Hi, I need one more PMC vote...other votes are appreciated. here it is: +1 On 07/05/17 15:46, Karl Heinz Marbaise wrote: Hi, We solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12340502 There

[MNG-6130] Loss of profile information in workaround for MNG-4900

Who seconds 6130 for 3.5.1? This is a one-line fix and all ITs pass. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [MNG-6130] Loss of profile information in workaround for MNG-4900

7 21:55:38 +0200, Michael Osipov <micha...@apache.org> wrote: Who seconds 6130 for 3.5.1? This is a one-line fix and all ITs pass. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional command

Re: [VOTE] Release Apache Maven Dependency Plugin version 3.0.1

Karl Heinz, the vote is over, do you want to continue with the release? Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: Open Maven resolvers issue and release 1.1.0

to change: code or documentation. Right, I will pick up the dependency updates have this seconded by someone and start 1.1.0 release. On Mon, 15 May 2017 17:12:04 +0200, Michael Osipov <micha...@apache.org> wrote: Hi folks, what to do with the remaining issues (pre-reset? Here is th

Re: Open Maven resolvers issue and release 1.1.0

Here are some minor issues for 1.1.0: MRESOLVER-22 Upgrade to Maven Parent 30 MRESOLVER-23 Avoid implicit primitive type casts MRESOLVER-24 Turn some IllegalArgumentExceptions into IllegalStateExceptions Who seconds them? - To

Re: [MNG-6169] Lifecycle/binding plugin version updates

Am 2017-05-13 um 22:38 schrieb Hervé BOUTEMY: Le samedi 13 mai 2017, 00:58:45 CEST Michael Osipov a écrit : Am 2017-05-13 um 00:30 schrieb Hervé BOUTEMY: Le vendredi 12 mai 2017, 13:50:37 CEST Michael Osipov a écrit : Am 2017-05-12 um 08:25 schrieb Hervé BOUTEMY: Jenkins build is not flaky

Re: [MNG-6169] Lifecycle/binding plugin version updates

Am 2017-05-13 um 23:39 schrieb Michael Osipov: Am 2017-05-13 um 22:38 schrieb Hervé BOUTEMY: Le samedi 13 mai 2017, 00:58:45 CEST Michael Osipov a écrit : Am 2017-05-13 um 00:30 schrieb Hervé BOUTEMY: Le vendredi 12 mai 2017, 13:50:37 CEST Michael Osipov a écrit : Am 2017-05-12 um 08:25

Several MRESOLVER issues

Folks, who seconds the following issues for Maven Resolver 1.1: MRESOLVER-4: Use java.util.Objects#requireNonNull to intercept null input MRESOLVER-5: Update minimum Java version to 1.7 MRESOLVER-6: Use java.nio.charset.StandardCharsets wherever possible Michael

Re: [MNG-6169] Lifecycle/binding plugin version updates

to that issue as comment (and not only in git commit message) would be useful before merging so that this change is understood when reading the code Did update JIRA issues. I will go ahead and merge the commit. Regards, Hervé Le dimanche 14 mai 2017, 00:25:10 CEST Michael Osipov a écrit : I

Open Maven resolvers issue and release 1.1.0

Hi folks, what to do with the remaining issues (pre-reset? Here is the list: MRESOLVER-3 Update dependencies MRESOLVER-8 ScopeDependencySelector incorrectly de-selects direct dependencies MRESOLVER-9 DefaultDependencyCollector does not correctly handle dependency management MRESOLVER-10 New

[MNG-6169] Lifecycle/binding plugin version updates

Who seconds MNG-6169 for 3.5.1? I have a fully working branch (MNG-6169_2/not-updated-MJAR-MCOMPILER) passing all ITs on Windows 10 and FreeBSD 10.3-RELEASE. Jenkins build is flaky with notorious file://target/null artifact not found. Some bindings haven't been updated because they cause

Re: [MNG-6169] Lifecycle/binding plugin version updates

Am 2017-05-12 um 19:23 schrieb Chas Honton: How can the super pom be explicitly added to the project's pom? Not necessary, the Super POM is in a JAR distributed with Maven and automatically used. On May 12, 2017, at 4:50 AM, Michael Osipov <micha...@apache.org> wrote: Am 2017-05-12

Re: [MNG-6169] Lifecycle/binding plugin version updates

Am 2017-05-11 um 22:46 schrieb Robert Scholte: Is m-compiler-p on 3.6.1? please change to 3.5.1 until jigsaw stuff works correctly. Version has been downgraded. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For

Re: [MNG-6169] Lifecycle/binding plugin version updates

Am 2017-05-12 um 08:25 schrieb Hervé BOUTEMY: Jenkins build is not flaky: it is strict on dependency resolution from cache, which is an intent, not a bug Traced down last missing dependencies and added them to Bootstrap IT. Branch MNG-6169 created on the Core ITs. Michael

Aw: Re: svn commit: r1799189 - /maven/plugins/trunk/maven-assembly-plugin/pom.xml

How is this possible? I ran the UTs twice. Did you check the dep tree? 3.0.0 should have been mediated. > Gesendet: Montag, 19. Juni 2017 um 22:13 Uhr > Von: "Guillaume Boué" <gb...@apache.org> > An: dev@maven.apache.org, "Michael Osipov" <micha...

Re: [ANN] First call to round up issues for 3.5.1

Am 2017-06-23 um 16:27 schrieb Robert Scholte: MNG-6220: Add CLI options to control color output by introducing system property style.color=[auto*|enabled|disabled] This definitively needs polish and a value style like tree/grep. I left several comments on the PR.

Re: svn commit: r1799189 - /maven/plugins/trunk/maven-assembly-plugin/pom.xml

he end of the week. Michael Le 20/06/2017 à 13:46, Michael Osipov a écrit : How is this possible? I ran the UTs twice. Did you check the dep tree? 3.0.0 should have been mediated. Gesendet: Montag, 19. Juni 2017 um 22:13 Uhr Von: "Guillaume Boué" <gb...@apache.org> An: dev

Re: [VOTE] Release Apache Maven Shared Component: Maven Reporting Impl 3.0.0

Am 2017-06-21 um 20:16 schrieb Karl Heinz Marbaise: Hi, We solved 14 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12332979 There are still a couple of issues left in JIRA:

Re: Heads up, Plexus IO/Archiver is going Java 7

Am 2017-05-22 um 09:13 schrieb Plamen Totev: Hi, As the branch is now merged is there anything that blocks the release of Plexus IO 3.0.0? I need to do some more stuff like parent release, etc. It is in my pipeline. Will try to do this by the end of the week. Michael

[MNG-6084] Support JSR 250 annotations

Who seconds MNG-6084 for 3.5.1? This one was developed by Dan Tran. I added non-functional fixes to it. All ITs pass as well as its own IT. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional

Releasing Maven Resolver 1.1.0

Hi folks, is there anything holding us back from MRESOLVER 1.1.0? I'd like to start the release by the end of the week and have it integrated into Maven 3.5.1. Any objections? Michael - To unsubscribe, e-mail:

Re: [MNG-6084] Support JSR 250 annotations

Am 2017-05-25 um 05:11 schrieb Dan Tran: Thanks Michael for pushing this out. Looking forward to use it in 3.5.1 Just to be sure, you are officially seconding it? On Wed, May 24, 2017 at 4:04 PM, Michael Osipov <micha...@apache.org> wrote: Who seconds MNG-6084 for 3.5.1? Th

Re: [MNG-6164] Collections inconsistently immutable

Am 2017-05-25 um 21:12 schrieb Michael Osipov: Who seconds MNG-6164 for 3.5.1? This is a non-functional consistency fix. All ITs pass. Anyone? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional

Re: Releasing Maven Resolver 1.1.0

before the release? Regards, Hervé [1] http://maven.apache.org/resolver-archives/resolver-LATEST/ [2] http://wiki.eclipse.org/Aether Le vendredi 26 mai 2017, 16:18:02 CEST Michael Osipov a écrit : Hi folks, is there anything holding us back from MRESOLVER 1.1.0? I'd like to start t

Re: Releasing Maven Resolver 1.1.0

Le vendredi 26 mai 2017, 16:18:02 CEST Michael Osipov a écrit : Hi folks, is there anything holding us back from MRESOLVER 1.1.0? I'd like to start the release by the end of the week and have it integrated into Maven 3.5.1. Any objections? Michael

Re: [MNG-6164] Collections inconsistently immutable

and see return, we can postpone to 3.6 if we think this is too problematic. Michael Le dimanche 28 mai 2017, 12:01:20 CEST Michael Osipov a écrit : Am 2017-05-25 um 21:12 schrieb Michael Osipov: Who seconds MNG-6164 for 3.5.1? This is a non-functional consistency fix. All ITs pass. Anyone

Re: Releasing Maven Resolver 1.1.0

28 May 2017 11:15:00 +0200, Michael Osipov <micha...@apache.org> wrote: Am 2017-05-28 um 09:43 schrieb Hervé BOUTEMY: are there seconders for http://git-wip-us.apache.org/repos/asf/maven-resolver/commit/17f804d7 (aka "option 2")? I'd completely leave it off to 1.x until the

[MNG-6167] Clean up dependency mess (reported by dependency:analyze)

Who seconds MNG-6167 for 3.5.1? All ITs pass locally and on Jenkins. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [ANN] First call to round up issues for 3.5.1

Am 2017-06-04 um 20:55 schrieb Karl Heinz Marbaise: Hi, I would like to suggest to introduce: MNG-6206 MNG-6207 to be part of Maven 3.5.1... Currently for MNG-6206 we have a pull request which solves the issue also the IT's are Ok for this. I will check also for MNG-6207.. If there are no

Re: Code review. Please approve new branches.

Am 2017-06-03 um 10:56 schrieb Tibor Digana: I have added a new branch with small change only, SUREFIRE-1380. https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=shortlog;h=refs/heads/SUREFIRE-1380 I am not happy with this: you mix two different taks in one issue, refactoring and

Re: Code review. Please approve new branches.

the motivation. On Sat, Jun 3, 2017 at 12:31 PM, Tibor Digana <tibor.dig...@googlemail.com> wrote: The changes in SUREFIRE-1376 are done. On Sat, Jun 3, 2017 at 11:52 AM, Michael Osipov <micha...@apache.org> wrote: Am 2017-06-03 um 10:56 schrieb Tibor Digana: I have added a new branc

Re: Code review. Please approve new branches.

Looks good now. Am 2017-06-03 um 12:31 schrieb Tibor Digana: The changes in SUREFIRE-1376 are done. On Sat, Jun 3, 2017 at 11:52 AM, Michael Osipov <micha...@apache.org> wrote: Am 2017-06-03 um 10:56 schrieb Tibor Digana: I have added a new branch with small change only, SUREFIR

Re: Code review. Please approve new branches.

Am 2017-06-03 um 09:03 schrieb Tibor Digana: Hi all, We have a patch received from users group. I have improved it a bit, added Javadoc and pushed the code to branch [1]. Jira issue related [2]. [1]:

Re: Code review. Please approve new branches.

=maven-surefire.git;a=shortlog;h=refs/heads/SUREFIRE-1380_2 Looks both fine now to me. On Sat, Jun 3, 2017 at 12:54 PM, Michael Osipov <micha...@apache.org> wrote: Am 2017-06-03 um 12:36 schrieb Tibor Digana: Michael, I will split SUREFIRE-1380 in two tickets on tomorrow evening. A

Re: [MNG-6164] Collections inconsistently immutable

Am 2017-05-28 um 20:55 schrieb Hervé BOUTEMY: Le dimanche 28 mai 2017, 19:50:03 CEST Michael Osipov a écrit : How many cases are changed? In which areas of Maven API? That is the information I need to vote for this change, knowing the effective impact it will have As far as I can see

Re: Migration of remaining plugins to Git

Am 2017-06-18 um 15:45 schrieb Paul Hammant: In order to be able to build a composite 'trunk' for all components of maven (that are org.apache.*) can we move the remaining things left in Subversion to Git, and mirror them to Github? `git submodule` (etc) would be how we'd recreate a developer

Re: New Branch (report real sys props of forked JVM) SUREFIRE-1360

o problem. I am glad that somebody helps me like you do. On Sun, Apr 23, 2017 at 10:36 AM, Michael Osipov <micha...@apache.org> wrote: Am 2017-04-22 um 11:31 schrieb Tibor Digana: Hi, I would like to push SUREFIRE-1364 and then fix jira issue SUREFIRE-1360 which should help the us

Re: Releases for Maven Dependency Plugin / Maven Deploy Plugin

Am 2017-05-07 um 15:55 schrieb Karl Heinz Marbaise: Hi to all, after maven-artifact-transfer 0.9.1 is done I will go forward to make a release of: maven-dependency-plugin 3.0.1 which contains a Java 8 fix and afterwards I will go further to release There are some shared components which

Re: Maven 3.5.1 - MNG-6205: upgrade JAnsi to 1.16

Am 2017-05-07 um 16:04 schrieb Hervé BOUTEMY: Hi, I'd like to merge this MNG-6205 branch to master, which fixes multiple issues: - MNG-6205: encoding issues - MNG-6186: removal of HawtJNI native librarires integration workaround - MNG-6218: MinGW bash not recognized Looks good to me.

Re: [VOTE] Release Apache Maven Shared Component: Maven Dependency Tree version 3.0.1

Am 2017-05-07 um 20:29 schrieb Karl Heinz Marbaise: Hi, We solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12333851 There are still a couple of issues left in JIRA:

Re: Releases for Maven Dependency Plugin / Maven Deploy Plugin

Am 2017-05-07 um 17:34 schrieb Karl Heinz Marbaise: Hi Michael, On 07/05/17 17:23, Michael Osipov wrote: Am 2017-05-07 um 15:55 schrieb Karl Heinz Marbaise: Hi to all, after maven-artifact-transfer 0.9.1 is done I will go forward to make a release of: maven-dependency-plugin 3.0.1 which

Re: Re: Heads up, Plexus IO/Archiver is going Java 7

For example, maven-jar-plugin has plexus-archiver as a dependency. m-jar-p > v3.0.2 requires Java 6. Is a bump to v3.1.0 enough for going to Java 7? > > /Anders > > On Thu, May 4, 2017 at 10:39 PM, Michael Osipov <micha...@apache.org> wrote: > > > Hi folks, > >

Re: Re: Re: Heads up, Plexus IO/Archiver is going Java 7

va 6. Is a bump to v3.1.0 enough for going to Java 7? > > > > /Anders > > > > On Thu, May 4, 2017 at 10:39 PM, Michael Osipov <micha...@apache.org> wrote: > > > > > Hi folks, > > > > > > five months ago I asked about Java 7 upgrade

Re: [ANN] First call to round up issues for 3.5.1

We should consider this batch https://github.com/ChristianSchulte/maven/commit/3494c28426b8dd5711b730d622ba98d603caeda6#commitcomment-22009084 if we want to address the issue we talked about on IRC. Michael Am 2017-05-05 um 21:04 schrieb Robert Scholte: I gave my spin for the

Re: [ANN] First call to round up issues for 3.5.1

Am 2017-05-05 um 19:23 schrieb Stephen Connolly: Progress seems to be being made... I'm willing to let current progress continue for the next 1-2 weeks before starting a whip-round to drive towards a release... anyone want me to accelerate? On Tue 25 Apr 2017 at 21:43, Stephen Connolly < No

Re: [ANN] First call to round up issues for 3.5.1

, Michael Osipov <micha...@apache.org> wrote: We should consider this batch https://github.com/ChristianSchulte/maven/commit/3494c28426b8dd5711b730d622ba98d603caeda6#commitcomment-22009084 if we want to address the issue we talked about on IRC. Michael Am 2017-05-05 um 21:04 schrieb Robert Schol

Re: Heads up, Plexus IO/Archiver is going Java 7

Am 2017-05-05 um 10:44 schrieb Anders Hammar: On Fri, May 5, 2017 at 10:22 AM, Michael Osipov <1983-01...@gmx.net> wrote: This will also ultimately mean that these plugins will run with Maven 3.3 only if someone still uses an older version and Java 6 to build their projects. If someone

Heads up, Plexus IO/Archiver is going Java 7

Hi folks, five months ago I asked about Java 7 upgrade of Plexus Archiver [1] and received no reaction. I will move to a new major and integrate Plamen's changes. Additionally, he was so kind to work on Plexus IO too and remove all pre Java 7 code [2]. I will raise major too and merge his

[MNG-6164] Collections inconsistently immutable

Who seconds MNG-6164 for 3.5.1? This is a non-functional consistency fix. All ITs pass. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

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

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

Re: [VOTE] Release Apache Maven 3.5.1

Am 2017-09-15 um 00:50 schrieb Petr Široký: I was able to easily fix our plugin by e.g. replacing "Thread.currentThread().getContextClassLoader()" with "this.getClass().getClassLoader()" (in the Mojo class) to get the plugin classloader. I don't know though if the

Re: Users can assign Fix Version/s in Jira

Am 2017-09-08 um 00:42 schrieb Tibor Digana: I found out that users create an issue in Jira and *assign version* [1]. I remember this did not happen in old Jira. So I decide to report a ticket in INFRA. Do you have the same experiences? What's your opinion about it? [1]:

Re: [RESULT] Re: Please retweet and vote

Am 2017-09-10 um 19:07 schrieb Stephen Connolly: Hervé and I discussed on irc earlier today. My suggestion - I was going to write up tomorrow - is that we drop 7 for 3.6.x We should focus 3.6.x on making the codebase Java 8 (lambdas, replace FileStream with the non-file handle leak

Re: Tests for MNG-6275 fail on Java 1.7.0_151-b01

:\Entwicklung\Programme\apache-maven-3.5.0 Java version: 1.7.0_154, vendor: Azul Systems, Inc. Java home: C:\Program Files\Zulu\zulu-7\jre Default locale: de_DE, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Re: Tests for MNG-6275 fail on Java 1.7.0_151-b01

and test again. I am pretty sure that it will fail too. On Sun, Sep 10, 2017 at 11:17 PM, Michael Osipov <micha...@apache.org> wrote: Am 2017-09-10 um 23:15 schrieb Tibor Digana: This one 1.7.0_80 which is 7u80: http://www.oracle.com/technetwork/java/javase/downloads/ java-archive-dow

Tests for MNG-6275 fail on Java 1.7.0_151-b01

Folks, tried running master on Maven home: /usr/local/share/java/maven Java version: 1.7.0_151, vendor: Oracle Corporation Java home: /usr/local/openjdk7/jre Default locale: de_DE, platform encoding: UTF-8 OS name: "freebsd", version: "11.1-release-p1", arch: "i386", family: "unix" and I get

Re: Tests for MNG-6275 fail on Java 1.7.0_151-b01

Am 2017-09-10 um 23:07 schrieb Tibor Digana: Michael, now try with Oracle Java 7. Last public version or up-to-date paid version? On Sun, Sep 10, 2017 at 11:02 PM, Michael Osipov <micha...@apache.org> wrote: Am 2017-09-10 um 22:27 schrieb Stephen Connolly: Well I ran the r

Re: Tests for MNG-6275 fail on Java 1.7.0_151-b01

. Michael On Sun, Sep 10, 2017 at 11:12 PM, Michael Osipov <mosi...@gmx.de> wrote: Am 2017-09-10 um 23:07 schrieb Tibor Digana: Michael, now try with Oracle Java 7. Last public version or up-to-date paid version? On Sun, Sep 10, 2017 at 11:02 PM, Michael Osipov <micha...@a

Re: [VOTE] Release Apache Doxia Sitetools version 1.7.5

Am 2017-09-26 um 20:51 schrieb Robert Scholte: Hi, We solved 5 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12338982=Text There are still a couple of issues left in JIRA:

Re: Allow custom updatePolicy

> I just wanted to get thoughts on a possible new feature. Right now, my > company has thousands of Maven modules that are all on snapshots with an > updatePolicy of "always" (basically everyone gets the latest build of > everything, kind of like a poor man's monorepo). Why "always" then and not

Re: Maven resolver branch consolidation

Why -1 on the Ant tasks? Am 2017-11-15 um 00:50 schrieb Hervé BOUTEMY: I answered on the mailing list and on the 2 Jira issues In summary, +1 to merge demos, -1 to merge ant-tasks Regards, Hervé Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a écrit : Any feedback or should I just go

Re: beam leaving maven, anything doable?

Am 2017-11-27 um 20:24 schrieb Romain Manni-Bucau: Hi guys, anything doable on maven side (either tuning or code changes) to be as good as gradle on beam project. The project is goind to leave maven as build tool ([1]) and I think it is very bad for 1. the community and 2. ASF as an ecosystem.

Re: beam leaving maven, anything doable?

drawback of maven it seems. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-11-27 20:47 GMT+01:00 Michael Osipov <micha...@apache.org>: Am 2017-11-27 um 20:24 schrieb Romain Manni-Bucau: Hi guys, anything doable on maven side (either tuning or code c

Re: Maven resolver branch consolidation

Am 2017-11-15 um 23:05 schrieb Hervé BOUTEMY: it seems I have not been clear: I'll try to explain better 1. maven-resolver-ant-tasks depends on maven-resolver-provider (from Maven core) 2. maven-resolver-provider (then Maven core) depends on maven-resolver if we put maven-resolver-ant-tasks in

Re: Maven 4.0.0

Am 2017-11-04 um 13:20 schrieb Stephen Connolly: The past two days, Hervé, Robert and I have been discussing our next steps. I think we have a semi-consensus which I want to bring back to the list: We keep 3.5.x as a stable branch with critical bug fixes only We switch master to 4.0.0 and

Re: Maven Docker Images

Am 2017-10-22 um 04:24 schrieb Manfred Moser: Following up on that remark and my earlier remark that we should NOT make this official .. here are my remarks: - so far the only binaries we assemble and call official are the tar.gz and zip archives (and even that is a gray line since official

Re: Re: [VOTE] Release Apache Maven Doxia version 1.8

+1 > Gesendet: Donnerstag, 21. Dezember 2017 um 09:30 Uhr > Von: "Hervé BOUTEMY" > An: "Maven Developers List" > Betreff: Re: [VOTE] Release Apache Maven Doxia version 1.8 > > one vote still missing... > > Regards, > > Hervé > > Le dimanche 17

Re: Second MNG-6403

the branch. Kind regards Karl Heinz Marbaise On 06/05/18 21:15, Michael Osipov wrote: Am 2018-05-06 um 21:08 schrieb Karl Heinz Marbaise: Hi, I second MNG-6403 for 3.5.4 we should write a test for this to be sure this does not happen again... Do you have anything specific in mind? I ha

Re: Second MNG-6403

Am 2018-05-06 um 21:08 schrieb Karl Heinz Marbaise: Hi, I second MNG-6403 for 3.5.4 we should write a test for this to be sure this does not happen again... Do you have anything specific in mind? I have updated the branch and added a test to ArtifactUtilsTest. Is that sufficient? Michael

Re: Second MNG-6386

Am 2018-05-05 um 13:23 schrieb Stephen Connolly: On Sat 5 May 2018 at 09:13, Michael Osipov <micha...@apache.org> wrote: Am 2018-05-05 um 09:15 schrieb Stephen Connolly: On Thu 3 May 2018 at 22:10, Michael Osipov <micha...@apache.org> wrote: Am 2018-05-02 um 10:41 schrieb Robert

Re: Second MNG-6386

Am 2018-05-05 um 09:15 schrieb Stephen Connolly: On Thu 3 May 2018 at 22:10, Michael Osipov <micha...@apache.org> wrote: Am 2018-05-02 um 10:41 schrieb Robert Scholte: I don't see a new test[1][2], only rewrites to confirm there's no regression. I understand the issue, but we jus

Re: Second MNG-5756

.0_162\jre Default locale: de_DE, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" Seems a bit long, but consistent on one line, just saying "Java location". On Mon, 07 May 2018 22:30:51 +0200, M

Re: Second MNG-6403

would think we should add a test that proves that the given pattern is NOT a SNAPSHOT version... Something like this: assertEquals( false, ArtifactUtils.isSnapshot( "1.2.3-20090413X094722-2")); WDYT ? Kind regards Karl Heinz Marbaise On 06/05/18 21:15, Michael Osipov wrote: Am

Re: Second MNG-5756

"JRE installation:"? I know it is long, but unambigious. It is not really about dropping this information, but merely displaying which JVM this Maven instance is running. Is the proposal acceptable with "installation"? Michael On Sun, 06 May 2018 00:11:36 +0200, Mi

Re: Second MNG-5756

Am 2018-05-07 um 23:27 schrieb Robert Scholte: On Mon, 07 May 2018 23:14:18 +0200, Michael Osipov <micha...@apache.org> wrote: Am 2018-05-07 um 22:40 schrieb Robert Scholte: That's indeed better. Maybe a comment that when Maven requires Java9 it could be reverted to "Java Hom

Second MNG-5756

Hi folks, who seconds MNG-5756 for 3.5.4? Several folks complain that "mvn -v" does not correspond to the reality, therefore two PRs have been created. I have just changed the output to "JRE used:" instead of "Java home:". Michael

Second MNG-6403

Hi folks, who seconds MNG-6403 for 3.5.4? A simple fix where we forgot to escape a period in a regex pattern. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail:

Re: Maven Doxia and minimum Java versions

Am 2018-05-19 um 09:08 schrieb Sylwester Lachiewicz: Hi, i checked doxia-sitetools code and looks it will be possible to replace httpunit with JSoup. We already use Jsoup in other places and only require Java 7. This sounds really promising. I love JSoup, used it already several times. How

Re: Build failed in Jenkins: Maven TLP » maven » master #14

Am 2018-05-19 um 11:41 schrieb Hervé Boutemy: Maven master branch build is failing on ASF Jenkins for one week looks related to TLS 1.2 only support on https://www.apache.org/, when the build is currently done with JDK 7u80 which has TLS 1.2 disabled by default I tried to enable TLS 1.2 adding

Re: Build failed in Jenkins: Maven TLP » maven » master #14

Am 2018-05-20 um 22:28 schrieb Sylwester Lachiewicz: Hi, Difference between repo1.maven.org and maven.apache.org is that out site accepts only tlsv1.2 ( https://www.ssllabs.com/ssltest/analyze.html?d=maven.apache.org) where Central now accepts tls 1.0, 1.1, 1.2

Re: [ANN] First call for 3.5.4 release

Am 2018-05-19 um 23:41 schrieb Stephen Connolly: MNG-6401 if somebody merges before wagon, +1 I have pushed two branches for it now. It passes all ITs locally. Jenkins fails for the TLS issue. Are we good to merge this one? On 19 May 2018 at 17:43, Robert Scholte

<    2   3   4   5   6   7   8   9   10   11   >