Re: Maven 3.6.1 release date

2019-04-01 Thread Dan Tran 
MNG-6605 indeed is a good one to have

On Mon, Apr 1, 2019 at 12:08 AM Karl Heinz Marbaise 
wrote:

> Hi Michael,
>
> On 01.04.19 08:54, Michael Osipov wrote:
> > Am 2019-03-31 um 21:36 schrieb Karl Heinz Marbaise:
> >> Hi,
> >>
> >> I would like to collect the issues which should be part of  Maven 3.6.1:
> >
> > MNG-6605 will go into. Non-intrusive, not active by default.
>
> I've seen that...that's good idea...
>
>
> >
> >> On 31.03.19 21:27, Karl Heinz Marbaise wrote:
> >>> Hi Michael,
> >>>
> >>> would it be helpful if I start the release tomorrow ?
> >>>
> >>> Cause I can see the list of issues assigned to Maven 3.6.1 is solved
> the
> >>> status looks Ok to me.
> >>>
> >>> Kind Regards
> >>> Karl Heinz Marbaise
> >>>
> >>> On 31.03.19 21:10, Mickael Istria wrote:
>  Hi,
>  What's the status of the release? Is its backlog «closed» now? When
>  is it
>  supposed to be shipped?
>  I'd like to make sure Eclipse m2e can upgrade before next released
>  as the
>  was already dalyed once.
>  Cheers,
> 
>  On Saturday, March 23, 2019, Hervé BOUTEMY 
>  wrote:
> 
> > there is only one task to do: transform the great minimal testcase
> > provided in
> > https://issues.apache.org/jira/browse/MNG-6506 to an IT, to not just
> > upgrade
> > blindly a dependency but keep track of what it solves
> >
> > Regards,
> >
> > Hervé
> >
> > Le vendredi 22 mars 2019, 11:45:19 CET Roman Grigoriadi a écrit :
> >> What is the issue with including MNG-6543 and MNG-6506?
> >> plexus-classworlds 2.6.0 seems to have a fix for both of them, are
> >> there
> >> any integration failures?
> >>
> >> Roman
> >>
> >> On Fri, Mar 22, 2019 at 9:32 AM Karl Heinz Marbaise
> >> 
> >>
> >> wrote:
> >>> Hi,
> >>>
> >>> On 22.03.19 09:25, Michael Osipov wrote:
>  Am 2019-03-22 um 08:37 schrieb Mickael Istria:
> > Hi,
> >
> > On Sat, Mar 9, 2019 at 6:34 PM Hervé BOUTEMY
> >  >>
> >
> > wrote:
> >> We're working on it, it should happen quite soon, but no date is
> >> really
> >> guaranteed: as you can see from Jira issues to be resolved [1],
> > we're
> >> near...
> >
> > At this point, since there are some blockers issues that have
> been
> > fixed
> > and community is in need of the new release, shouldn't we avoid
> > adding
> > enhancements in 3.6.1 backlog, focus on important remaining
> > bugs and
> > try to
> > ship it ASAP?
> > It seems to me that the scope of 3.6.1 is always growing, at the
> > risk
> > of
> > never releasing a lot of value that was already produced...
> 
>  I agree, I'd move out MNG-6506 and MNG-6543 and continue with the
>  relase.
> 
>  @Karl, can you make MNG-6538 happen?
> >>>
> >>> I will in the evening...already assigned the ticket...
> >>>
> >>
> >> -
> >> 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
>
>

[VOTE] Release Maven Resolver Ant Tasks version 1.2.0

2019-04-01 Thread Michael Osipov 

Hi,

We solved 11 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12345231

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22ant%20tasks%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1495/
https://repository.apache.org/content/repositories/maven-1495/org/apache/maven/resolver/maven-resolver-ant-tasks/1.2.0/maven-resolver-ant-tasks-1.2.0-source-release.zip

Source release checksum(s):
maven-resolver-ant-tasks-1.2.0-source-release.zip
sha512: 
46f58229848118fc8a3664f9ac41a1356d9f2b0e50f7259e3bd13dce030422d0dd8040300872cf598f862fcdd6a6fce7f1064ad62dcae656b030d5404be80568


Staging site:
https://maven.apache.org/resolver-archives/resolver-ant-tasks-LATEST/

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

Vote open for 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: Surefire maintenance release

2019-04-01 Thread Enrico Olivelli 
Il sab 30 mar 2019, 14:16 Enrico Olivelli  ha scritto:

> I have created a PR for your work Stephane
> https://github.com/apache/maven-surefire/pull/225
>
> I will do my best
> I am still new to the release procedure, never cut a release for surefire
> and we usually are only cutting releases from master.
>

We are experiencing integration tests failures I am checking with Chris.
Any help is appreciated

Enrico



>
> Enrico
>
>
>
> Il gio 28 mar 2019, 00:34 Olivier Lamy  ha scritto:
>
>> On Thu, 28 Mar 2019 at 03:14, Enrico Olivelli 
>> wrote:
>>
>> > Il mer 27 mar 2019, 18:10 Tibor Digana  ha
>> > scritto:
>> >
>> > > Enrico, what i maintenance release for you, 2.22.2-M1?
>> > >
>> >
>> > 2.22.2 without suffix
>> >
>>
>> +1
>> @Tibor if you are too busy maybe Enrico can cut the release if he has
>> time.
>>
>>
>> >
>> >
>> > Enrico
>> >
>> > >
>> > >
>> > >
>> > >
>> > > On Wed, Mar 27, 2019 at 6:07 PM Enrico Olivelli 
>> > > wrote:
>> > >
>> > > > Stephane
>> > > > thank you so much.
>> > > > I think we will be able to cut a maintenaince release soon with your
>> > > > branch.
>> > > >
>> > > > Maybe you can join us in chat with
>> https://s.apache.org/slack-invite
>> > > > #maven  channel
>> > > >
>> > > >
>> > > > Enrico
>> > > >
>> > > > Il giorno mer 27 mar 2019 alle ore 15:45 Tibor Digana
>> > > >  ha scritto:
>> > > > >
>> > > > > Stephane, What exists in our agreement are two issues
>> (SUREFIRE-1546
>> > > and
>> > > > > SUREFIRE-1614), you will have them but no multiple releases (not
>> > > > effective
>> > > > > in the perspectives of out spare time).
>> > > > > We need people like you who will support us in 3.0.0-M4. This is
>> the
>> > > main
>> > > > > goal.
>> > > > > The issues SUREFIRE-1546 and SUREFIRE-1614 will be delivered to
>> you,
>> > > but
>> > > > no
>> > > > > more and not less.
>> > > > > The thing is how you will participate by your hands in Java code.
>> The
>> > > > > result depends on you.
>> > > > > But again, this what we solve here is not important for ASF. It is
>> > > > > important for you and your agenda.
>> > > > > For the project is important the deal we made several years ago,
>> when
>> > > we
>> > > > > planned to provide Extensions API for the Users. To get there we
>> need
>> > > to
>> > > > > unfortunately rework internal code in Surefire project which takes
>> > > > really a
>> > > > > lots of time and spends private energy, and thus 2.22.2 is less
>> > > important
>> > > > > from this perspective. We have to support long standing vision but
>> > the
>> > > > > version 2.22.2 is something short lasting which you and some
>> Spring
>> > > guys
>> > > > > wanted due to they have a problem* with their own internal rules*
>> and
>> > > > > technically Spring project can solve this problem with 3.0.0-M3.
>> > > > Therefore
>> > > > > we are wasting the time if we write the code for you. Therefore
>> you
>> > > > should
>> > > > > provide pull request by yourself as this is OSS and we can make a
>> > code
>> > > > > review. But our effort would be really only short time relevant
>> if we
>> > > > > dedicate too much time in 2.22.2 with these two Jira issues. We
>> have
>> > > few
>> > > > > active Java developers and "stealing" them for your activity means
>> > that
>> > > > we
>> > > > > are not effective and slow. Therefore, Stephane pls prepare the
>> > commits
>> > > > on
>> > > > > your responsibility on GitHub in your pull request and we can
>> invest
>> > > the
>> > > > > time to check it including the build check and cutting the release
>> > > > version.
>> > > > >
>> > > > > T
>> > > > >
>> > > > >
>> > > > >
>> > > > > On Wed, Mar 27, 2019 at 8:11 AM Stephane Nicoll <
>> > > > stephane.nic...@gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > > > On Tue, Mar 26, 2019 at 12:26 PM Tibor Digana <
>> > > tibordig...@apache.org>
>> > > > > > wrote:
>> > > > > >
>> > > > > > > Stephane,
>> > > > > > >
>> > > > > > > >> I wanted to make sure that the JUnit5 story was functional
>> > > > > > >
>> > > > > > > I really don't like politics.
>> > > > > >
>> > > > > >
>> > > > > > What's that supposed to mean? If you want to quote something,
>> > please
>> > > > quote
>> > > > > > the full sentence. The full sentence is *"I wanted to make sure
>> > that
>> > > > the
>> > > > > > JUnit5 story was functional with the vintage engine and the
>> current
>> > > GA
>> > > > of
>> > > > > > surefire." *which I believe is an accurate description of the
>> > current
>> > > > > > situation.
>> > > > > >
>> > > > > >
>> > > > > > > Did you see SUREFIRE-1614?
>> > > > > >
>> > > > > >
>> > > > > > I did, that's the issue I backported. What are you talking
>> about?
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > > It really does not
>> > > > > > > break functionality (only affects logger) and SUREFIRE-1614 is
>> > not
>> > > > worth
>> > > > > > of
>> > > > > > > making release with single improvement. If you want to be
>> > > >

Re: Maven 3.6.1 release date

2019-04-01 Thread Karl Heinz Marbaise 

Hi Michael,

On 01.04.19 08:54, Michael Osipov wrote:

Am 2019-03-31 um 21:36 schrieb Karl Heinz Marbaise:

Hi,

I would like to collect the issues which should be part of  Maven 3.6.1:


MNG-6605 will go into. Non-intrusive, not active by default.


I've seen that...that's good idea...





On 31.03.19 21:27, Karl Heinz Marbaise wrote:

Hi Michael,

would it be helpful if I start the release tomorrow ?

Cause I can see the list of issues assigned to Maven 3.6.1 is solved the
status looks Ok to me.

Kind Regards
Karl Heinz Marbaise

On 31.03.19 21:10, Mickael Istria wrote:

Hi,
What's the status of the release? Is its backlog «closed» now? When
is it
supposed to be shipped?
I'd like to make sure Eclipse m2e can upgrade before next released
as the
was already dalyed once.
Cheers,

On Saturday, March 23, 2019, Hervé BOUTEMY 
wrote:


there is only one task to do: transform the great minimal testcase
provided in
https://issues.apache.org/jira/browse/MNG-6506 to an IT, to not just
upgrade
blindly a dependency but keep track of what it solves

Regards,

Hervé

Le vendredi 22 mars 2019, 11:45:19 CET Roman Grigoriadi a écrit :

What is the issue with including MNG-6543 and MNG-6506?
plexus-classworlds 2.6.0 seems to have a fix for both of them, are
there
any integration failures?

Roman

On Fri, Mar 22, 2019 at 9:32 AM Karl Heinz Marbaise


wrote:

Hi,

On 22.03.19 09:25, Michael Osipov wrote:

Am 2019-03-22 um 08:37 schrieb Mickael Istria:

Hi,

On Sat, Mar 9, 2019 at 6:34 PM Hervé BOUTEMY




wrote:

We're working on it, it should happen quite soon, but no date is
really
guaranteed: as you can see from Jira issues to be resolved [1],

we're

near...


At this point, since there are some blockers issues that have been
fixed
and community is in need of the new release, shouldn't we avoid

adding

enhancements in 3.6.1 backlog, focus on important remaining
bugs and
try to
ship it ASAP?
It seems to me that the scope of 3.6.1 is always growing, at the

risk

of
never releasing a lot of value that was already produced...


I agree, I'd move out MNG-6506 and MNG-6543 and continue with the
relase.

@Karl, can you make MNG-6538 happen?


I will in the evening...already assigned the ticket...



-
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: Maven 3.6.1 release date

2019-04-01 Thread Michael Osipov 

Am 2019-03-31 um 21:36 schrieb Karl Heinz Marbaise:

Hi,

I would like to collect the issues which should be part of  Maven 3.6.1:


MNG-6605 will go into. Non-intrusive, not active by default.


On 31.03.19 21:27, Karl Heinz Marbaise wrote:

Hi Michael,

would it be helpful if I start the release tomorrow ?

Cause I can see the list of issues assigned to Maven 3.6.1 is solved the
status looks Ok to me.

Kind Regards
Karl Heinz Marbaise

On 31.03.19 21:10, Mickael Istria wrote:

Hi,
What's the status of the release? Is its backlog «closed» now? When 
is it

supposed to be shipped?
I'd like to make sure Eclipse m2e can upgrade before next released as 
the

was already dalyed once.
Cheers,

On Saturday, March 23, 2019, Hervé BOUTEMY  
wrote:



there is only one task to do: transform the great minimal testcase
provided in
https://issues.apache.org/jira/browse/MNG-6506 to an IT, to not just
upgrade
blindly a dependency but keep track of what it solves

Regards,

Hervé

Le vendredi 22 mars 2019, 11:45:19 CET Roman Grigoriadi a écrit :

What is the issue with including MNG-6543 and MNG-6506?
plexus-classworlds 2.6.0 seems to have a fix for both of them, are
there
any integration failures?

Roman

On Fri, Mar 22, 2019 at 9:32 AM Karl Heinz Marbaise 



wrote:

Hi,

On 22.03.19 09:25, Michael Osipov wrote:

Am 2019-03-22 um 08:37 schrieb Mickael Istria:

Hi,

On Sat, Mar 9, 2019 at 6:34 PM Hervé BOUTEMY 



wrote:

We're working on it, it should happen quite soon, but no date is
really
guaranteed: as you can see from Jira issues to be resolved [1],

we're

near...


At this point, since there are some blockers issues that have been
fixed
and community is in need of the new release, shouldn't we avoid

adding
enhancements in 3.6.1 backlog, focus on important remaining bugs 
and

try to
ship it ASAP?
It seems to me that the scope of 3.6.1 is always growing, at the

risk

of
never releasing a lot of value that was already produced...


I agree, I'd move out MNG-6506 and MNG-6543 and continue with the
relase.

@Karl, can you make MNG-6538 happen?


I will in the evening...already assigned the ticket...



-
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: Maven 3.6.1 release date

2019-04-01 Thread Karl Heinz Marbaise 

Hi Sylwester,

On 01.04.19 08:50, Sylwester Lachiewicz wrote:

Hi Karl,
nothing super important from my side to add to 3.6.1 and I can wait. So +1
to do release

Could you create 3.6.2 Jira version so I will start planning issues for the
next version?


Done.




BR
Sylwester

niedz., 31 mar 2019 o 21:36 Karl Heinz Marbaise 
napisał(a):


Hi,

I would like to collect the issues which should be part of  Maven 3.6.1:

Hands up?

Kind regards
Karl Heinz Marbaise

On 31.03.19 21:27, Karl Heinz Marbaise wrote:

Hi Michael,

would it be helpful if I start the release tomorrow ?

Cause I can see the list of issues assigned to Maven 3.6.1 is solved the
status looks Ok to me.

Kind Regards
Karl Heinz Marbaise

On 31.03.19 21:10, Mickael Istria wrote:

Hi,
What's the status of the release? Is its backlog «closed» now? When is

it

supposed to be shipped?
I'd like to make sure Eclipse m2e can upgrade before next released as

the

was already dalyed once.
Cheers,

On Saturday, March 23, 2019, Hervé BOUTEMY 

wrote:



there is only one task to do: transform the great minimal testcase
provided in
https://issues.apache.org/jira/browse/MNG-6506 to an IT, to not just
upgrade
blindly a dependency but keep track of what it solves

Regards,

Hervé

Le vendredi 22 mars 2019, 11:45:19 CET Roman Grigoriadi a écrit :

What is the issue with including MNG-6543 and MNG-6506?
plexus-classworlds 2.6.0 seems to have a fix for both of them, are
there
any integration failures?

Roman

On Fri, Mar 22, 2019 at 9:32 AM Karl Heinz Marbaise <

khmarba...@gmx.de>


wrote:

Hi,

On 22.03.19 09:25, Michael Osipov wrote:

Am 2019-03-22 um 08:37 schrieb Mickael Istria:

Hi,

On Sat, Mar 9, 2019 at 6:34 PM Hervé BOUTEMY <

herve.bout...@free.fr




wrote:

We're working on it, it should happen quite soon, but no date is
really
guaranteed: as you can see from Jira issues to be resolved [1],

we're

near...


At this point, since there are some blockers issues that have been
fixed
and community is in need of the new release, shouldn't we avoid

adding

enhancements in 3.6.1 backlog, focus on important remaining bugs

and

try to
ship it ASAP?
It seems to me that the scope of 3.6.1 is always growing, at the

risk

of
never releasing a lot of value that was already produced...


I agree, I'd move out MNG-6506 and MNG-6543 and continue with the
relase.

@Karl, can you make MNG-6538 happen?


I will in the evening...already assigned the ticket...



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

Re: Maven 3.6.1 release date

2019-04-01 Thread Sylwester Lachiewicz 
Hi Karl,
nothing super important from my side to add to 3.6.1 and I can wait. So +1
to do release

Could you create 3.6.2 Jira version so I will start planning issues for the
next version?
BR
Sylwester

niedz., 31 mar 2019 o 21:36 Karl Heinz Marbaise 
napisał(a):

> Hi,
>
> I would like to collect the issues which should be part of  Maven 3.6.1:
>
> Hands up?
>
> Kind regards
> Karl Heinz Marbaise
>
> On 31.03.19 21:27, Karl Heinz Marbaise wrote:
> > Hi Michael,
> >
> > would it be helpful if I start the release tomorrow ?
> >
> > Cause I can see the list of issues assigned to Maven 3.6.1 is solved the
> > status looks Ok to me.
> >
> > Kind Regards
> > Karl Heinz Marbaise
> >
> > On 31.03.19 21:10, Mickael Istria wrote:
> >> Hi,
> >> What's the status of the release? Is its backlog «closed» now? When is
> it
> >> supposed to be shipped?
> >> I'd like to make sure Eclipse m2e can upgrade before next released as
> the
> >> was already dalyed once.
> >> Cheers,
> >>
> >> On Saturday, March 23, 2019, Hervé BOUTEMY 
> wrote:
> >>
> >>> there is only one task to do: transform the great minimal testcase
> >>> provided in
> >>> https://issues.apache.org/jira/browse/MNG-6506 to an IT, to not just
> >>> upgrade
> >>> blindly a dependency but keep track of what it solves
> >>>
> >>> Regards,
> >>>
> >>> Hervé
> >>>
> >>> Le vendredi 22 mars 2019, 11:45:19 CET Roman Grigoriadi a écrit :
>  What is the issue with including MNG-6543 and MNG-6506?
>  plexus-classworlds 2.6.0 seems to have a fix for both of them, are
>  there
>  any integration failures?
> 
>  Roman
> 
>  On Fri, Mar 22, 2019 at 9:32 AM Karl Heinz Marbaise <
> khmarba...@gmx.de>
> 
>  wrote:
> > Hi,
> >
> > On 22.03.19 09:25, Michael Osipov wrote:
> >> Am 2019-03-22 um 08:37 schrieb Mickael Istria:
> >>> Hi,
> >>>
> >>> On Sat, Mar 9, 2019 at 6:34 PM Hervé BOUTEMY <
> herve.bout...@free.fr
> 
> >>>
> >>> wrote:
>  We're working on it, it should happen quite soon, but no date is
>  really
>  guaranteed: as you can see from Jira issues to be resolved [1],
> >>> we're
>  near...
> >>>
> >>> At this point, since there are some blockers issues that have been
> >>> fixed
> >>> and community is in need of the new release, shouldn't we avoid
> >>> adding
> >>> enhancements in 3.6.1 backlog, focus on important remaining bugs
> and
> >>> try to
> >>> ship it ASAP?
> >>> It seems to me that the scope of 3.6.1 is always growing, at the
> >>> risk
> >>> of
> >>> never releasing a lot of value that was already produced...
> >>
> >> I agree, I'd move out MNG-6506 and MNG-6543 and continue with the
> >> relase.
> >>
> >> @Karl, can you make MNG-6538 happen?
> >
> > I will in the evening...already assigned the ticket...
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>