+1
I'll look to cutting the release at the start of September, prepare
accordingly
On 4 August 2017 at 05:30, Robert Scholte wrote:
> On Fri, 23 Jun 2017 16:27:03 +0200, Robert Scholte
> wrote:
>
> Looking for someone who can second the following issues:
>>
> Second attempt:
>
>
>> MNG-6148: C
On Fri, 23 Jun 2017 16:27:03 +0200, Robert Scholte
wrote:
Looking for someone who can second the following issues:
Second attempt:
MNG-6148: Can't package and assemble with JDK9/Jigsaw
See
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=361b902d0c01d9a2b82d4b126ecd3a
I'm fine with that:
style.color=[auto*|always|never]
the original PR is still based on a CLI option which I don't like because
all other style options are already and only controlled by system
properties.
I have to create a new branch if we can agree on this.
Robert
On Fri, 23 Jun 2017 16:
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.
---
Looking for someone who can second the following issues:
MNG-6148: Can't package and assemble with JDK9/Jigsaw
MNG-6127: Fix plugin execution configuration interference
MNG-6220: Add CLI options to control color output
by introducing system property style.color=[auto*|enabled|disabled]
than
Hi Guillaume,
+1 from me...
for that fix..
Kind regards
Karl Heinz Marbaise
On 11/06/17 00:05, Guillaume Boué wrote:
Hi,
I'd like to propose MNG-6240 to be added in 3.5.1.
Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/e76e217a
IT:
http://git-wip-us.apache.org/repos/asf/maven-i
Hi,
I'd like to propose MNG-6240 to be added in 3.5.1.
Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/e76e217a
IT:
http://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/a162291e
Successful Jenkins build:
https://builds.apache.org/job/maven-3.x-jenkinsfile/job/MNG-6
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 o
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 objections I will integrate them after the have been
This specific issue seems quite isolated to me and is likely introduced
when switching from Sonetype Aether to Eclipse Aether, where (IIRC) the
boolean became a Boolean.
On Fri, 05 May 2017 22:18:11 +0200, Michael Osipov
wrote:
That wasn't actually my point. Christian wrote that to make
That wasn't actually my point. Christian wrote that to make the entire
chain consistent several issues have to be addressed.
Am 2017-05-05 um 21:54 schrieb Robert Scholte:
AFAIK you, me and Stephen already agreed that MNG-5935 should be part
of 3.5.1
On Fri, 05 May 2017 21:09:02 +0200, Michae
Hi,
On 05/05/17 21:54, Robert Scholte wrote:
AFAIK you, me and Stephen already agreed that MNG-5935 should be part
of 3.5.1
+1 From me as well for this.
Kind regards
Karl Heinz Marbaise
On Fri, 05 May 2017 21:09:02 +0200, Michael Osipov
wrote:
We should consider this batch
https://githu
AFAIK you, me and Stephen already agreed that MNG-5935 should be part of
3.5.1
On Fri, 05 May 2017 21:09:02 +0200, Michael Osipov
wrote:
We should consider this batch
https://github.com/ChristianSchulte/maven/commit/3494c28426b8dd5711b730d622ba98d603caeda6#commitcomment-22009084
if we
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 3.5.1-candidates
I gave my spin for the 3.5.1-candidates. I've mentioned the issues I'd
like to add, but most are still waiting to be seconded.
Robert
On Fri, 05 May 2017 19:23:41 +0200, Stephen Connolly
wrote:
Progress seems to be being made... I'm willing to let current progress
continue for the next 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 acc
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 <
stephen.alan.conno...@gmail.com> wrote:
> I'd like people
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 migr
I've marked MNG-6025 as 3.5.1-candidate. It has been fixed before and
looks like a nice improvement.
Robert
On Mon, 01 May 2017 22:23:35 +0200, Eric Lilja
wrote:
Is https://issues.apache.org/jira/browse/MNG-6025 being included in
3.5.1? I sure hope so!
- Eric L
On 2017-05-01 22:15, H
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 migrated to the maven codebase in
3.5.
Jon
On M
Is https://issues.apache.org/jira/browse/MNG-6025 being included in
3.5.1? I sure hope so!
- Eric L
On 2017-05-01 22:15, Hervé BOUTEMY wrote:
great!
I'll mark it for 3.5.1
Regards,
Hervé
Le lundi 1 mai 2017, 19:59:50 CEST Robert Scholte a écrit :
@Hervé, I want to second MNG-6223
Robert
great!
I'll mark it for 3.5.1
Regards,
Hervé
Le lundi 1 mai 2017, 19:59:50 CEST Robert Scholte a écrit :
> @Hervé, I want to second MNG-6223
>
> Robert
>
> On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly
>
> wrote:
> > I'd like people to take this next week to consider what issues we wa
@Hervé, I want to second MNG-6223
Robert
On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly
wrote:
I'd like people to take this next week to consider what issues we want to
pull in scope for 3.5.1.
If you are a committer, just add the issues to Fix Version of
3.5.1-candidate, ideally ad
> 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
> * [MNG-6186] - switch to improved HawtJNI
> Robert: Improvements have not been accepted yet, branch now has conflicts
Guillaume Nodet, from Fusesource, has just merged
I don't know when he's considering to do a release, but it might be quite soon
Regards,
Hervé
Le jeudi 27 avril 2017, 12:
Hi,
I would like to add the following issue:
MNG-6123 - detect self references in POM and fail fast
Karl Heinz: Currently having an implementation but currently conflicts
with some IT's cause they are using self referencing dependencies.
Moved it to "3.5.1-candidate"...
Kind regards
Karl He
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 Haw
Let me start going through the list of candidates:
Maven - Version 3.5.1-candidate
** Sub-task
* [MNG-6186] - switch to improved HawtJNI
Robert: Improvements have not been accepted yet, branch now has conflicts
** Bug
* [MNG-4347] - import-scoped dependencies of direct dependencies are
I'd like people to take this next week to consider what issues we want to
pull in scope for 3.5.1.
If you are a committer, just add the issues to Fix Version of
3.5.1-candidate, ideally adding a comment at the same time with your
reasoning.
If once we have a seconding committer, they can just com
29 matches
Mail list logo
