date:20170104


Am 2017-01-05 um 01:01 schrieb Dan Tran:

Hi,

before the canceled wagon-1.11 the suite was about 6minutes, now it is 9
min on my virtualbox centos 7,  jdk 7

Is it  a concern?


Can you actually tell which test exactly runs longer?

I have added to two tests a sleep for 2000 ms to avoid race conditions. 
This can sum up on your machine.



PS the good thing the huge http test no longer timeout on my box


It neither does now on Jenkins with Windows. This is likely due to the 
reduced buffer size. Switched from Jetty's DefaultServlet to a anonymous 
inner class with a smaller buffer.


Michael

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

Re: Cannot edit or comment on Wiki pages

Am 01/04/17 um 08:44 schrieb Hervé BOUTEMY:
> Hi,
> 
> I don't know how it was done (a good number of years ago) for me to have edit 
> karma, but I have.
> I looked for INFRA documentation on the topic, and found related procedure I 
> didn't know [1]
> 
> I don't know who is the "Space Admin" for Maven Wiki, but we'll need to 
> figure 
> out and add this point in our new committer process: looks like new 
> committers 
> don't get access to the necessary toolset currently to work efficiently 
> within 
> the team...
> 
> BTW, is the Jenkins admin question fixed also?
> 
> Since if I contact INFRA on the Wiki topic, I'll see the Jenkins topic also.

Jenkins permissions are ok.

Regards,
-- 
Christian


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

Re: Flakey Integration Test in post-reset-master

Maybe just test if things change when running those ITs multiple times
with Maven 3.0.5 instead of 3.3.9.

Am 01/05/17 um 02:37 schrieb Christian Schulte:
> Am 01/04/17 um 20:16 schrieb Stephen Connolly:
>> https://builds.apache.org/view/Maven/job/maven-jenkinsfile/job/post-reset-master/6/testReport/junit/org.apache.maven.it/MavenITmng3599useHttpProxyForWebDAVTest/testitUseHttpProxyForWebDAV_2/
>>
>> Seems to fail at random on Windows...
>>
> 
> It may be a classpath ordering issue. It's only happening on Windows.
> Maybe on Linux the file name order is preserved whereas on Windows it's
> random. The last comment in here
> 
> 
> 
> links to
> 
> 
> 
> "Ordering of extension class path is indeterministic"
> 
> If you take a look at the changes done to fix it, you'll notice that
> there are changes in the core having to do with extension classpath
> construction (maybe due to the addition of support for extenion.xml
> files). So maybe the extension class path again is indeterministic due
> to those changes and there really is an issue in the core.
> 
> Regards,
> 


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

Re: Flakey Integration Test in post-reset-master

Am 01/04/17 um 20:16 schrieb Stephen Connolly:
> https://builds.apache.org/view/Maven/job/maven-jenkinsfile/job/post-reset-master/6/testReport/junit/org.apache.maven.it/MavenITmng3599useHttpProxyForWebDAVTest/testitUseHttpProxyForWebDAV_2/
> 
> Seems to fail at random on Windows...
> 

It may be a classpath ordering issue. It's only happening on Windows.
Maybe on Linux the file name order is preserved whereas on Windows it's
random. The last comment in here



links to



"Ordering of extension class path is indeterministic"

If you take a look at the changes done to fix it, you'll notice that
there are changes in the core having to do with extension classpath
construction (maybe due to the addition of support for extenion.xml
files). So maybe the extension class path again is indeterministic due
to those changes and there really is an issue in the core.

Regards,
-- 
Christian


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

[Wagon] http-provider suite is longer by 3 minutes

2017-01-04 Thread Dan Tran

Hi,

before the canceled wagon-1.11 the suite was about 6minutes, now it is 9
min on my virtualbox centos 7,  jdk 7

Is it  a concern?

Thanks

-Dan

PS the good thing the huge http test no longer timeout on my box

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

2017-01-04 Thread Guillaume Boué

+1 (committer)

Le 04/01/2017 à 13:16, Stephen Connolly a écrit :

Hi,

We have collectively managed to mess up our ability to follow the original
release plan for 3.4.0 which was originally supposed to consist of an
effective no-op change of Eclipse's Aether for the code after migration to
Apache's Maven Resolver plus some other orthogonal changes around logging
colourization and launcher script bug fixes.

Given that some developer private builds of the current master branch have
been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have been
closed with a fixed version of 3.4.0.

For us to release a 3.4.0 with those fixes reverted, could cause confusion
with our user community.

Additionally the informal practice of keeping existing integration tests as
RTC has not been followed, leading to some people to question whether the
integration tests remain valid.

For all the above reasons it is proposed to do *all* the following as an
whole:

1. In git://git.apache.org/maven.git we will rename the current master
branch to `pre-reset-master` and recreate `master`
as bce33aa2662a51d18cb00347cf2fb174dc195fb1 (
https://github.com/apache/maven/commit/bce33aa2662a51d18cb00347cf2fb174dc195fb1
)

2. In git://git.apache.org/maven-integration-testing.git we will rename the
current master branch to `pre-reset-master` and recreate `master`
as f31241ad6cb6474e559289f1bd7110ea5d5a4fba (
https://github.com/apache/maven-integration-testing/commit/f31241ad6cb6474e559289f1bd7110ea5d5a4fba
)

3. In git://git.apache.org/maven-resolver.git we will rename the current
master branch to `pre-reset-master` and recreate `master`
as b74f7a1e8837875b4780199f644119f55d22465d (
https://github.com/apache/maven-resolver/commit/b74f7a1e8837875b4780199f644119f55d22465d),
i.e. the 1.0.x branch

We will then proceed to have (ideally) the original committers cherry-pick
(and tidy up an squash... if the original committers are not able to assist
then squashing may not be practicable) those changes that have been agreed
for 3.5.0 as summarized on the
https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 wiki page
(authorative source of the decisions summarized in the wiki page is the
mail thread:
https://mail-archives.apache.org/mod_mbox/maven-dev/201612.mbox/%3CCA%2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw%40mail.gmail.com%3E
).

As this involves a --force push on the `master` branch, we want to get the
approval of the committers before continuing.

The vote will be open for at least 72 hours.

The vote will be decided by a simple majority of valid votes cast. There is
no veto.

The vote is open to all committers.

In addition, for the vote to be valid, there must be at least 3x+1 votes
from PMC members

[ ] +1: Yes
[ ] 0:
[ ] -1: No

-Stephen

---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel
antivirus Avast.
https://www.avast.com/antivirus

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

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

+1 (committer)

Am 01/04/17 um 13:16 schrieb Stephen Connolly:
> Hi,
> 
> We have collectively managed to mess up our ability to follow the original
> release plan for 3.4.0 which was originally supposed to consist of an
> effective no-op change of Eclipse's Aether for the code after migration to
> Apache's Maven Resolver plus some other orthogonal changes around logging
> colourization and launcher script bug fixes.
> 
> Given that some developer private builds of the current master branch have
> been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have been
> closed with a fixed version of 3.4.0.
> 
> For us to release a 3.4.0 with those fixes reverted, could cause confusion
> with our user community.
> 
> Additionally the informal practice of keeping existing integration tests as
> RTC has not been followed, leading to some people to question whether the
> integration tests remain valid.
> 
> For all the above reasons it is proposed to do *all* the following as an
> whole:
> 
> 1. In git://git.apache.org/maven.git we will rename the current master
> branch to `pre-reset-master` and recreate `master`
> as bce33aa2662a51d18cb00347cf2fb174dc195fb1 (
> https://github.com/apache/maven/commit/bce33aa2662a51d18cb00347cf2fb174dc195fb1
> )
> 
> 2. In git://git.apache.org/maven-integration-testing.git we will rename the
> current master branch to `pre-reset-master` and recreate `master`
> as f31241ad6cb6474e559289f1bd7110ea5d5a4fba (
> https://github.com/apache/maven-integration-testing/commit/f31241ad6cb6474e559289f1bd7110ea5d5a4fba
> )
> 
> 3. In git://git.apache.org/maven-resolver.git we will rename the current
> master branch to `pre-reset-master` and recreate `master`
> as b74f7a1e8837875b4780199f644119f55d22465d (
> https://github.com/apache/maven-resolver/commit/b74f7a1e8837875b4780199f644119f55d22465d),
> i.e. the 1.0.x branch
> 
> We will then proceed to have (ideally) the original committers cherry-pick
> (and tidy up an squash... if the original committers are not able to assist
> then squashing may not be practicable) those changes that have been agreed
> for 3.5.0 as summarized on the
> https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 wiki page
> (authorative source of the decisions summarized in the wiki page is the
> mail thread:
> https://mail-archives.apache.org/mod_mbox/maven-dev/201612.mbox/%3CCA%2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw%40mail.gmail.com%3E
>  ).
> 
> As this involves a --force push on the `master` branch, we want to get the
> approval of the committers before continuing.
> 
> The vote will be open for at least 72 hours.
> 
> The vote will be decided by a simple majority of valid votes cast. There is
> no veto.
> 
> The vote is open to all committers.
> 
> In addition, for the vote to be valid, there must be at least 3x+1 votes
> from PMC members
> 
> [ ] +1: Yes
> [ ] 0:
> [ ] -1: No
> 
> -Stephen
> 


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

[DISCUSS] [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

This would be better on the discuss thread, but here is my answer anyway:

Well we want to bring most of that history back in for 3.5.1+ so, no that
wouldn't work AIUI.

Part of the issue is the to and fro with things like the bump of
modelVersion to 4.1.0 and then the revert, etc.

Plus if the commits are in history how can mortal git users determine what
is included.

On Wed 4 Jan 2017 at 21:12, Mark Derricutt  wrote:

>
>
> On 5 Jan 2017, at 1:16, Stephen Connolly wrote:
>
>
>
>
>
>
> As this involves a --force push on the `master` branch, we want to get the
>
>
> approval of the committers before continuing.
>
>
>
>
>
>
>
>
>
>
> You *could* branch at the point you want to reset to, then use an
> ours/theirs merge strategy which creates a merge commit that ONLY takes one
> side. Effectively resetting, keeping the fact we did this reversal, and
> doesn't force everyone to re-clone.
>
>
>
>
> From https://git-scm.com/docs/merge-strategies:
>
>
>
>
> *ours:* This resolves any number of heads, but the resulting tree of the
> merge is always that of the current branch head, effectively ignoring all
> changes from all other branches. It is meant to be used to supersede old
> development history of side branches. Note that this is different from the
> -Xours option to the 'recursive' merge strategy.
>
>
>
>
> Would something like this be better than force pushing?
>
>
>
>
> --
>
>
> Mark Derricutt
>
>
> http://www.theoryinpractice.net
>
>
> http://www.chaliceofblood.net
>
>
> http://plus.google.com/+MarkDerricutt
>
>
> http://twitter.com/talios
>
>
> http://facebook.com/mderricutt
>
>
> --
Sent from my phone

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

2017-01-04 Thread Mark Derricutt

On 5 Jan 2017, at 1:16, Stephen Connolly wrote:

> As this involves a --force push on the `master` branch, we want to get the
> approval of the committers before continuing.

You _could_ branch at the point you want to reset to, then use an ours/theirs 
merge strategy which creates a merge commit that ONLY takes one side.  
Effectively resetting, keeping the fact we did this reversal, and doesn't force 
everyone to re-clone.

From https://git-scm.com/docs/merge-strategies:

**ours:** This resolves any number of heads, but the resulting tree of the 
merge is always that of the current branch head, effectively ignoring all 
changes from all other branches. It is meant to be used to supersede old 
development history of side branches. Note that this is different from the 
-Xours option to the 'recursive' merge strategy.

Would something like this be better than force pushing?

-- 
Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt

signature.asc
Description: OpenPGP digital signature

Re: Flakey Integration Test in post-reset-master

We don't delete them. We can mark them as skipped using the range
facilities of the integration tests

Integration tests should be mostly append only.

There are some rare cases were an existing test needs modification. Those
should be handled as RTC

There are more cases where we may decide to change the specification of
Maven which means that existing tests are not valid for newer versions of
Maven... again they should be handled as RTC

Adding new tests should be CTR

That is my opinion. Jason and Robert also mostly agree with this
principle... so while not put to a vote of committers (which is what would
be required to make it policy - doesn't affect board delegated
responsibilities so no need for PMC quorum) it is probably good enough to
serve as a convention to follow

- Stephen
On Wed 4 Jan 2017 at 20:42, Michael Osipov  wrote:

> Sounds reasonable. This applies to a lot of tests. There are also a
>
> bunch of tests which apply to Maven 2.x only. I see no reason to keep
>
> them around.
>
>
>
> Michael
>
>
>
> Am 2017-01-04 um 21:26 schrieb Stephen Connolly:
>
> > Then we should use ranges to disable for newer Maven and create a new
> test
>
> > with a range enabling for the new mavens
>
> >
>
> > On Wed 4 Jan 2017 at 19:46, Michael Osipov  wrote:
>
> >
>
> >> Am 2017-01-04 um 20:27 schrieb Stephen Connolly:
>
> >>
>
> >>> perhaps, but we need to be careful about changing ITs
>
> >>
>
> >>
>
> >>
>
> >> This being true, but having tests rely on a very old extension version
>
> >>
>
> >> does not reflect reality. Consider that the Wagon version in Maven is
>
> >>
>
> >> 2.10 but the extension in  2.0. Looks awkward to me.
>
> >>
>
> >>
>
> >>
>
> >>> On 4 January 2017 at 19:22, Michael Osipov 
> wrote:
>
> >>
>
> >>>
>
> >>
>
>  Am 2017-01-04 um 20:16 schrieb Stephen Connolly:
>
> >>
>
> 
>
> >>
>
> > https://builds.apache.org/view/Maven/job/maven-jenkinsfile/
>
> >>
>
> > job/post-reset-master/6/testReport/junit/org.apache.
>
> >>
>
> > maven.it/MavenITmng3599useHttpProxyForWebDAVTest/testitUseHt
>
> >>
>
> > tpProxyForWebDAV_2/
>
> >>
>
> >
>
> >>
>
> 
>
> >>
>
>  I have seen this somewhere else already...the Wagon version in this IT
>
> >> is
>
> >>
>
>  soo old: 2.0. We should retry this IT with a new Wagon version.
>
> >>
>
> 
>
> >>
>
> 
>
> >>
>
> 
>
> >>
>
>  -
>
> >>
>
>  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
>
> >>
>
> >>
>
> >>
>
> >> --
>
> > Sent from my phone
>
> >
>
>
>
>
>
> -
>
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
>
> --
Sent from my phone

Re: Flakey Integration Test in post-reset-master

Sounds reasonable. This applies to a lot of tests. There are also a 
bunch of tests which apply to Maven 2.x only. I see no reason to keep 
them around.


Michael

Am 2017-01-04 um 21:26 schrieb Stephen Connolly:

Then we should use ranges to disable for newer Maven and create a new test
with a range enabling for the new mavens

On Wed 4 Jan 2017 at 19:46, Michael Osipov  wrote:


Am 2017-01-04 um 20:27 schrieb Stephen Connolly:


perhaps, but we need to be careful about changing ITs




This being true, but having tests rely on a very old extension version

does not reflect reality. Consider that the Wagon version in Maven is

2.10 but the extension in  2.0. Looks awkward to me.




On 4 January 2017 at 19:22, Michael Osipov  wrote:







Am 2017-01-04 um 20:16 schrieb Stephen Connolly:







https://builds.apache.org/view/Maven/job/maven-jenkinsfile/



job/post-reset-master/6/testReport/junit/org.apache.



maven.it/MavenITmng3599useHttpProxyForWebDAVTest/testitUseHt



tpProxyForWebDAV_2/











I have seen this somewhere else already...the Wagon version in this IT

is


soo old: 2.0. We should retry this IT with a new Wagon version.















-



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



--

Sent from my phone




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

Re: Flakey Integration Test in post-reset-master

Then we should use ranges to disable for newer Maven and create a new test
with a range enabling for the new mavens

On Wed 4 Jan 2017 at 19:46, Michael Osipov  wrote:

> Am 2017-01-04 um 20:27 schrieb Stephen Connolly:
>
> > perhaps, but we need to be careful about changing ITs
>
>
>
> This being true, but having tests rely on a very old extension version
>
> does not reflect reality. Consider that the Wagon version in Maven is
>
> 2.10 but the extension in  2.0. Looks awkward to me.
>
>
>
> > On 4 January 2017 at 19:22, Michael Osipov  wrote:
>
> >
>
> >> Am 2017-01-04 um 20:16 schrieb Stephen Connolly:
>
> >>
>
> >>> https://builds.apache.org/view/Maven/job/maven-jenkinsfile/
>
> >>> job/post-reset-master/6/testReport/junit/org.apache.
>
> >>> maven.it/MavenITmng3599useHttpProxyForWebDAVTest/testitUseHt
>
> >>> tpProxyForWebDAV_2/
>
> >>>
>
> >>
>
> >> I have seen this somewhere else already...the Wagon version in this IT
> is
>
> >> soo old: 2.0. We should retry this IT with a new Wagon version.
>
> >>
>
> >>
>
> >>
>
> >> -
>
> >> 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
>
>
>
> --
Sent from my phone

[GitHub] maven-wagon issue #18: Implemented mkdirs method to use the webdav MKCOL HTT...

2017-01-04 Thread michael-o

Github user michael-o commented on the issue:

https://github.com/apache/maven-wagon/pull/18
  
One could also consider merging both and differentiate only by the URL, if 
this is possible.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] maven-wagon issue #18: Implemented mkdirs method to use the webdav MKCOL HTT...

2017-01-04 Thread michael-o

Github user michael-o commented on the issue:

https://github.com/apache/maven-wagon/pull/18
  
Is this a complete replacement for Jackrabbit for the Wagon provider?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: Flakey Integration Test in post-reset-master


Am 2017-01-04 um 20:27 schrieb Stephen Connolly:

perhaps, but we need to be careful about changing ITs


This being true, but having tests rely on a very old extension version 
does not reflect reality. Consider that the Wagon version in Maven is 
2.10 but the extension in  2.0. Looks awkward to me.



On 4 January 2017 at 19:22, Michael Osipov  wrote:


Am 2017-01-04 um 20:16 schrieb Stephen Connolly:


https://builds.apache.org/view/Maven/job/maven-jenkinsfile/
job/post-reset-master/6/testReport/junit/org.apache.
maven.it/MavenITmng3599useHttpProxyForWebDAVTest/testitUseHt
tpProxyForWebDAV_2/



I have seen this somewhere else already...the Wagon version in this IT is
soo old: 2.0. We should retry this IT with a new Wagon version.



-
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: Flakey Integration Test in post-reset-master

perhaps, but we need to be careful about changing ITs

On 4 January 2017 at 19:22, Michael Osipov  wrote:

> Am 2017-01-04 um 20:16 schrieb Stephen Connolly:
>
>> https://builds.apache.org/view/Maven/job/maven-jenkinsfile/
>> job/post-reset-master/6/testReport/junit/org.apache.
>> maven.it/MavenITmng3599useHttpProxyForWebDAVTest/testitUseHt
>> tpProxyForWebDAV_2/
>>
>
> I have seen this somewhere else already...the Wagon version in this IT is
> soo old: 2.0. We should retry this IT with a new Wagon version.
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Flakey Integration Test in post-reset-master


Am 2017-01-04 um 20:16 schrieb Stephen Connolly:

https://builds.apache.org/view/Maven/job/maven-jenkinsfile/job/post-reset-master/6/testReport/junit/org.apache.maven.it/MavenITmng3599useHttpProxyForWebDAVTest/testitUseHttpProxyForWebDAV_2/


I have seen this somewhere else already...the Wagon version in this IT 
is soo old: 2.0. We should retry this IT with a new Wagon version.




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

Flakey Integration Test in post-reset-master

https://builds.apache.org/view/Maven/job/maven-jenkinsfile/job/post-reset-master/6/testReport/junit/org.apache.maven.it/MavenITmng3599useHttpProxyForWebDAVTest/testitUseHttpProxyForWebDAV_2/

Seems to fail at random on Windows...

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

+1 (PMC & committer)

Am 2017-01-04 um 13:16 schrieb Stephen Connolly:

Hi,

Given that some developer private builds of the current master branch have
been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have been
closed with a fixed version of 3.4.0.

For us to release a 3.4.0 with those fixes reverted, could cause confusion
with our user community.

Additionally the informal practice of keeping existing integration tests as
RTC has not been followed, leading to some people to question whether the
integration tests remain valid.

For all the above reasons it is proposed to do *all* the following as an
whole:

As this involves a --force push on the `master` branch, we want to get the
approval of the committers before continuing.

The vote will be open for at least 72 hours.

The vote will be decided by a simple majority of valid votes cast. There is
no veto.

The vote is open to all committers.

In addition, for the vote to be valid, there must be at least 3x+1 votes
from PMC members

[ ] +1: Yes
[ ] 0:
[ ] -1: No

-Stephen

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

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)


Am 2017-01-04 um 10:06 schrieb Stephen Connolly:

On 31 December 2016 at 20:10, Stephen Connolly
I have updated the tracking of these issues previously without a JIRA:

MNG-   WONTFIX  Removing redundant test


This is part of MNG-5977


MNG-   WONTFIX  updated code to match API change after
Michael's feedback
MNG-   WONTFIX  updated code to match MessageBuilder API
change


Both commits are part of Hervé's work on MNG-3507 and alike.

Michael





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

Re: [VOTE] Releasing Wagon 2.11 - Cancel

I am fine with that. Though, I have changed tests to 2.12. This might 
justify 2.12, but I am open to either one.


Michael

Am 2017-01-04 um 10:36 schrieb Dan Tran:

I would vote for 2.11.1 same practice at maven core


-Dan

On Wed, Jan 4, 2017 at 1:22 AM, Michael Osipov <1983-01...@gmx.net> wrote:


If so, I would drop 2.11 altogether and go with 2.12.


Gesendet: Mittwoch, 04. Januar 2017 um 08:47 Uhr
Von: "Hervé BOUTEMY" 
An: "Maven Developers List" 
Betreff: Re: [VOTE] Releasing Wagon 2.11 - Cancel

on git, AFAIK, going to 2.11.1 seems the best practice (removing tag in

origin

repo is not reliable given people who have copied it won't have it

removed

automatically)

Regards,

Hervé

Le mardi 3 janvier 2017, 18:59:15 CET Dan Tran a écrit :

I reverted the poms back to 2.11-SNAPSHOT not keep the tag for now

since

some ppl may object removing remote history.

so we can keep the tag and move to 2.11.1-SNAPSHOT or remove

wagon-2.11 tag

and move on

-Dan

On Tue, Jan 3, 2017 at 6:08 PM, Dan Tran  wrote:

yes I can.  so it is ok to remove the tag?

-D

On Tue, Jan 3, 2017 at 2:01 PM, Michael Osipov 

wrote:

Am 2016-12-28 um 19:46 schrieb Dan Tran:

Hi

I am going to cancel this vote due to inconsistent test failure at
wagon-http provider on huge download test.


Can you please rollback release commits in the repo?

Michael

On Wed, Dec 28, 2016 at 7:08 AM, Michael Osipov 

wrote:

Am 2016-12-28 um 06:05 schrieb Dan Tran:

i still see the same timeout error on the jetty8 branch. No issue

at



master

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
(default-test) on project wagon-http: There was a timeout or

other

error in the fork -> [Help
1]org.apache.maven.lifecycle.LifecycleExecutionException:

Failed to

execute goal org.apache.maven.plugins:maven
-surefire-plugin:2.18.1:test
(default-test) on project wagon-http: There was a timeout or

other

error in the fork

at org.apache.maven.lifecycle.int

ernal.MojoExecutor.execute(Moj
oExecutor.java:212)


I have now extended tests to other Linux distros:

Fedora 25, 64 bit:
OpenJDK 8 Update 111: pass

CentOS 7, 64 bit:
OpenJDK 8 Update 111: pass
OpenJDK 7 Update 121: pass*

*This is actually your combo which works for me, but not for

you...


Additionally, I added this version to Maven 3.4.0-SNAPSHOT and

ran ITs

on
Windows 10, Fedora 25 and FreeBSD 10.3-RELEASE. All passed.



Michael



-

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




-
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








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

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

2017-01-04 Thread Manfred Moser

+1 (committer)

Stephen Connolly wrote on 2017-01-04 04:16:

> Hi,
> 
> We have collectively managed to mess up our ability to follow the original
> release plan for 3.4.0 which was originally supposed to consist of an
> effective no-op change of Eclipse's Aether for the code after migration to
> Apache's Maven Resolver plus some other orthogonal changes around logging
> colourization and launcher script bug fixes.
> 
> Given that some developer private builds of the current master branch have
> been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have been
> closed with a fixed version of 3.4.0.
> 
> For us to release a 3.4.0 with those fixes reverted, could cause confusion
> with our user community.
> 
> Additionally the informal practice of keeping existing integration tests as
> RTC has not been followed, leading to some people to question whether the
> integration tests remain valid.
> 
> For all the above reasons it is proposed to do *all* the following as an
> whole:
> 
> 1. In git://git.apache.org/maven.git we will rename the current master
> branch to `pre-reset-master` and recreate `master`
> as bce33aa2662a51d18cb00347cf2fb174dc195fb1 (
> https://github.com/apache/maven/commit/bce33aa2662a51d18cb00347cf2fb174dc195fb1
> )
> 
> 2. In git://git.apache.org/maven-integration-testing.git we will rename the
> current master branch to `pre-reset-master` and recreate `master`
> as f31241ad6cb6474e559289f1bd7110ea5d5a4fba (
> https://github.com/apache/maven-integration-testing/commit/f31241ad6cb6474e559289f1bd7110ea5d5a4fba
> )
> 
> 3. In git://git.apache.org/maven-resolver.git we will rename the current
> master branch to `pre-reset-master` and recreate `master`
> as b74f7a1e8837875b4780199f644119f55d22465d (
> https://github.com/apache/maven-resolver/commit/b74f7a1e8837875b4780199f644119f55d22465d),
> i.e. the 1.0.x branch
> 
> We will then proceed to have (ideally) the original committers cherry-pick
> (and tidy up an squash... if the original committers are not able to assist
> then squashing may not be practicable) those changes that have been agreed
> for 3.5.0 as summarized on the
> https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 wiki page
> (authorative source of the decisions summarized in the wiki page is the
> mail thread:
> https://mail-archives.apache.org/mod_mbox/maven-dev/201612.mbox/%3CCA%2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw%40mail.gmail.com%3E
> ).
> 
> As this involves a --force push on the `master` branch, we want to get the
> approval of the committers before continuing.
> 
> The vote will be open for at least 72 hours.
> 
> The vote will be decided by a simple majority of valid votes cast. There is
> no veto.
> 
> The vote is open to all committers.
> 
> In addition, for the vote to be valid, there must be at least 3x+1 votes
> from PMC members
> 
> [ ] +1: Yes
> [ ] 0:
> [ ] -1: No
> 
> -Stephen
> -- 
> Sent from my phone
> 


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

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

2017-01-04 Thread Benson Margulies

+1

On Jan 4, 2017 10:03 AM, "Robert Scholte"  wrote:

> +1
>
> On Wed, 04 Jan 2017 13:16:11 +0100, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> Hi,
>>
>> We have collectively managed to mess up our ability to follow the original
>> release plan for 3.4.0 which was originally supposed to consist of an
>> effective no-op change of Eclipse's Aether for the code after migration to
>> Apache's Maven Resolver plus some other orthogonal changes around logging
>> colourization and launcher script bug fixes.
>>
>> Given that some developer private builds of the current master branch have
>> been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have been
>> closed with a fixed version of 3.4.0.
>>
>> For us to release a 3.4.0 with those fixes reverted, could cause confusion
>> with our user community.
>>
>> Additionally the informal practice of keeping existing integration tests
>> as
>> RTC has not been followed, leading to some people to question whether the
>> integration tests remain valid.
>>
>> For all the above reasons it is proposed to do *all* the following as an
>> whole:
>>
>> 1. In git://git.apache.org/maven.git we will rename the current master
>> branch to `pre-reset-master` and recreate `master`
>> as bce33aa2662a51d18cb00347cf2fb174dc195fb1 (
>> https://github.com/apache/maven/commit/bce33aa2662a51d18cb00
>> 347cf2fb174dc195fb1
>> )
>>
>> 2. In git://git.apache.org/maven-integration-testing.git we will rename
>> the
>> current master branch to `pre-reset-master` and recreate `master`
>> as f31241ad6cb6474e559289f1bd7110ea5d5a4fba (
>> https://github.com/apache/maven-integration-testing/commit/f
>> 31241ad6cb6474e559289f1bd7110ea5d5a4fba
>> )
>>
>> 3. In git://git.apache.org/maven-resolver.git we will rename the current
>> master branch to `pre-reset-master` and recreate `master`
>> as b74f7a1e8837875b4780199f644119f55d22465d (
>> https://github.com/apache/maven-resolver/commit/b74f7a1e8837
>> 875b4780199f644119f55d22465d),
>> i.e. the 1.0.x branch
>>
>> We will then proceed to have (ideally) the original committers cherry-pick
>> (and tidy up an squash... if the original committers are not able to
>> assist
>> then squashing may not be practicable) those changes that have been agreed
>> for 3.5.0 as summarized on the
>> https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 wiki page
>> (authorative source of the decisions summarized in the wiki page is the
>> mail thread:
>> https://mail-archives.apache.org/mod_mbox/maven-dev/201612.m
>> box/%3CCA%2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw
>> %40mail.gmail.com%3E
>>  ).
>>
>> As this involves a --force push on the `master` branch, we want to get the
>> approval of the committers before continuing.
>>
>> The vote will be open for at least 72 hours.
>>
>> The vote will be decided by a simple majority of valid votes cast. There
>> is
>> no veto.
>>
>> The vote is open to all committers.
>>
>> In addition, for the vote to be valid, there must be at least 3x+1 votes
>> from PMC members
>>
>> [ ] +1: Yes
>> [ ] 0:
>> [ ] -1: No
>>
>> -Stephen
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

2017-01-04 Thread Robert Scholte

On Wed, 04 Jan 2017 13:16:11 +0100, Stephen Connolly
wrote:

Hi,

We have collectively managed to mess up our ability to follow the
original

release plan for 3.4.0 which was originally supposed to consist of an
effective no-op change of Eclipse's Aether for the code after migration
to

Apache's Maven Resolver plus some other orthogonal changes around logging
colourization and launcher script bug fixes.

Given that some developer private builds of the current master branch
have
been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have
been

closed with a fixed version of 3.4.0.

For us to release a 3.4.0 with those fixes reverted, could cause
confusion

with our user community.

Additionally the informal practice of keeping existing integration tests
as

RTC has not been followed, leading to some people to question whether the
integration tests remain valid.

For all the above reasons it is proposed to do *all* the following as an
whole:

2. In git://git.apache.org/maven-integration-testing.git we will rename
the

current master branch to `pre-reset-master` and recreate `master`
as f31241ad6cb6474e559289f1bd7110ea5d5a4fba (
https://github.com/apache/maven-integration-testing/commit/f31241ad6cb6474e559289f1bd7110ea5d5a4fba
)

for 3.5.0 as summarized on the
https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 wiki page
(authorative source of the decisions summarized in the wiki page is the
mail thread:
https://mail-archives.apache.org/mod_mbox/maven-dev/201612.mbox/%3CCA%2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw%40mail.gmail.com%3E
).

As this involves a --force push on the `master` branch, we want to get
the

approval of the committers before continuing.

The vote will be open for at least 72 hours.

The vote will be decided by a simple majority of valid votes cast. There
is

no veto.

The vote is open to all committers.

In addition, for the vote to be valid, there must be at least 3x+1 votes
from PMC members

[ ] +1: Yes
[ ] 0:
[ ] -1: No

-Stephen

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

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

2017-01-04 Thread Igor Fedorenko

+1

-- 
Regards,
Igor

On Wed, Jan 4, 2017, at 08:31 AM, Andreas Gudian wrote:
> +1
> 
> 
> Anders Hammar  schrieb am Mi. 4. Jan. 2017 um 13:22:
> 
> > +1
> >
> >
> >
> > /Anders
> >
> >
> >
> > On Wed, Jan 4, 2017 at 1:16 PM, Stephen Connolly <
> >
> > stephen.alan.conno...@gmail.com> wrote:
> >
> >
> >
> > > Hi,
> >
> > >
> >
> > > We have collectively managed to mess up our ability to follow the
> > original
> >
> > > release plan for 3.4.0 which was originally supposed to consist of an
> >
> > > effective no-op change of Eclipse's Aether for the code after migration
> > to
> >
> > > Apache's Maven Resolver plus some other orthogonal changes around logging
> >
> > > colourization and launcher script bug fixes.
> >
> > >
> >
> > > Given that some developer private builds of the current master branch
> > have
> >
> > > been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have
> > been
> >
> > > closed with a fixed version of 3.4.0.
> >
> > >
> >
> > > For us to release a 3.4.0 with those fixes reverted, could cause
> > confusion
> >
> > > with our user community.
> >
> > >
> >
> > > Additionally the informal practice of keeping existing integration tests
> > as
> >
> > > RTC has not been followed, leading to some people to question whether the
> >
> > > integration tests remain valid.
> >
> > >
> >
> > > For all the above reasons it is proposed to do *all* the following as an
> >
> > > whole:
> >
> > >
> >
> > > 1. In git://git.apache.org/maven.git we will rename the current master
> >
> > > branch to `pre-reset-master` and recreate `master`
> >
> > > as bce33aa2662a51d18cb00347cf2fb174dc195fb1 (
> >
> > > https://github.com/apache/maven/commit/bce33aa2662a51d18cb00347cf2fb1
> >
> > > 74dc195fb1
> >
> > > )
> >
> > >
> >
> > > 2. In git://git.apache.org/maven-integration-testing.git we will rename
> >
> > > the
> >
> > > current master branch to `pre-reset-master` and recreate `master`
> >
> > > as f31241ad6cb6474e559289f1bd7110ea5d5a4fba (
> >
> > > https://github.com/apache/maven-integration-testing/commit/
> >
> > > f31241ad6cb6474e559289f1bd7110ea5d5a4fba
> >
> > > )
> >
> > >
> >
> > > 3. In git://git.apache.org/maven-resolver.git we will rename the current
> >
> > > master branch to `pre-reset-master` and recreate `master`
> >
> > > as b74f7a1e8837875b4780199f644119f55d22465d (
> >
> > > https://github.com/apache/maven-resolver/commit/
> >
> > > b74f7a1e8837875b4780199f644119f55d22465d),
> >
> > > i.e. the 1.0.x branch
> >
> > >
> >
> > > We will then proceed to have (ideally) the original committers
> > cherry-pick
> >
> > > (and tidy up an squash... if the original committers are not able to
> > assist
> >
> > > then squashing may not be practicable) those changes that have been
> > agreed
> >
> > > for 3.5.0 as summarized on the
> >
> > > https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 wiki page
> >
> > > (authorative source of the decisions summarized in the wiki page is the
> >
> > > mail thread:
> >
> > > https://mail-archives.apache.org/mod_mbox/maven-dev/201612.mbox/%3CCA%
> >
> > > 2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw%40mail.gmail.com%3E
> >
> > >  ).
> >
> > >
> >
> > > As this involves a --force push on the `master` branch, we want to get
> > the
> >
> > > approval of the committers before continuing.
> >
> > >
> >
> > > The vote will be open for at least 72 hours.
> >
> > >
> >
> > > The vote will be decided by a simple majority of valid votes cast. There
> > is
> >
> > > no veto.
> >
> > >
> >
> > > The vote is open to all committers.
> >
> > >
> >
> > > In addition, for the vote to be valid, there must be at least 3x+1 votes
> >
> > > from PMC members
> >
> > >
> >
> > > [ ] +1: Yes
> >
> > > [ ] 0:
> >
> > > [ ] -1: No
> >
> > >
> >
> > > -Stephen
> >
> > > --
> >
> > > Sent from my phone
> >
> > >
> >
> >

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

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

2017-01-04 Thread Andreas Gudian

+1


Anders Hammar  schrieb am Mi. 4. Jan. 2017 um 13:22:

> +1
>
>
>
> /Anders
>
>
>
> On Wed, Jan 4, 2017 at 1:16 PM, Stephen Connolly <
>
> stephen.alan.conno...@gmail.com> wrote:
>
>
>
> > Hi,
>
> >
>
> > We have collectively managed to mess up our ability to follow the
> original
>
> > release plan for 3.4.0 which was originally supposed to consist of an
>
> > effective no-op change of Eclipse's Aether for the code after migration
> to
>
> > Apache's Maven Resolver plus some other orthogonal changes around logging
>
> > colourization and launcher script bug fixes.
>
> >
>
> > Given that some developer private builds of the current master branch
> have
>
> > been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have
> been
>
> > closed with a fixed version of 3.4.0.
>
> >
>
> > For us to release a 3.4.0 with those fixes reverted, could cause
> confusion
>
> > with our user community.
>
> >
>
> > Additionally the informal practice of keeping existing integration tests
> as
>
> > RTC has not been followed, leading to some people to question whether the
>
> > integration tests remain valid.
>
> >
>
> > For all the above reasons it is proposed to do *all* the following as an
>
> > whole:
>
> >
>
> > 1. In git://git.apache.org/maven.git we will rename the current master
>
> > branch to `pre-reset-master` and recreate `master`
>
> > as bce33aa2662a51d18cb00347cf2fb174dc195fb1 (
>
> > https://github.com/apache/maven/commit/bce33aa2662a51d18cb00347cf2fb1
>
> > 74dc195fb1
>
> > )
>
> >
>
> > 2. In git://git.apache.org/maven-integration-testing.git we will rename
>
> > the
>
> > current master branch to `pre-reset-master` and recreate `master`
>
> > as f31241ad6cb6474e559289f1bd7110ea5d5a4fba (
>
> > https://github.com/apache/maven-integration-testing/commit/
>
> > f31241ad6cb6474e559289f1bd7110ea5d5a4fba
>
> > )
>
> >
>
> > 3. In git://git.apache.org/maven-resolver.git we will rename the current
>
> > master branch to `pre-reset-master` and recreate `master`
>
> > as b74f7a1e8837875b4780199f644119f55d22465d (
>
> > https://github.com/apache/maven-resolver/commit/
>
> > b74f7a1e8837875b4780199f644119f55d22465d),
>
> > i.e. the 1.0.x branch
>
> >
>
> > We will then proceed to have (ideally) the original committers
> cherry-pick
>
> > (and tidy up an squash... if the original committers are not able to
> assist
>
> > then squashing may not be practicable) those changes that have been
> agreed
>
> > for 3.5.0 as summarized on the
>
> > https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 wiki page
>
> > (authorative source of the decisions summarized in the wiki page is the
>
> > mail thread:
>
> > https://mail-archives.apache.org/mod_mbox/maven-dev/201612.mbox/%3CCA%
>
> > 2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw%40mail.gmail.com%3E
>
> >  ).
>
> >
>
> > As this involves a --force push on the `master` branch, we want to get
> the
>
> > approval of the committers before continuing.
>
> >
>
> > The vote will be open for at least 72 hours.
>
> >
>
> > The vote will be decided by a simple majority of valid votes cast. There
> is
>
> > no veto.
>
> >
>
> > The vote is open to all committers.
>
> >
>
> > In addition, for the vote to be valid, there must be at least 3x+1 votes
>
> > from PMC members
>
> >
>
> > [ ] +1: Yes
>
> > [ ] 0:
>
> > [ ] -1: No
>
> >
>
> > -Stephen
>
> > --
>
> > Sent from my phone
>
> >
>
>

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

2017-01-04 Thread Anders Hammar

+1

/Anders

On Wed, Jan 4, 2017 at 1:16 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> Hi,
>
> We have collectively managed to mess up our ability to follow the original
> release plan for 3.4.0 which was originally supposed to consist of an
> effective no-op change of Eclipse's Aether for the code after migration to
> Apache's Maven Resolver plus some other orthogonal changes around logging
> colourization and launcher script bug fixes.
>
> Given that some developer private builds of the current master branch have
> been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have been
> closed with a fixed version of 3.4.0.
>
> For us to release a 3.4.0 with those fixes reverted, could cause confusion
> with our user community.
>
> Additionally the informal practice of keeping existing integration tests as
> RTC has not been followed, leading to some people to question whether the
> integration tests remain valid.
>
> For all the above reasons it is proposed to do *all* the following as an
> whole:
>
> 1. In git://git.apache.org/maven.git we will rename the current master
> branch to `pre-reset-master` and recreate `master`
> as bce33aa2662a51d18cb00347cf2fb174dc195fb1 (
> https://github.com/apache/maven/commit/bce33aa2662a51d18cb00347cf2fb1
> 74dc195fb1
> )
>
> 2. In git://git.apache.org/maven-integration-testing.git we will rename
> the
> current master branch to `pre-reset-master` and recreate `master`
> as f31241ad6cb6474e559289f1bd7110ea5d5a4fba (
> https://github.com/apache/maven-integration-testing/commit/
> f31241ad6cb6474e559289f1bd7110ea5d5a4fba
> )
>
> 3. In git://git.apache.org/maven-resolver.git we will rename the current
> master branch to `pre-reset-master` and recreate `master`
> as b74f7a1e8837875b4780199f644119f55d22465d (
> https://github.com/apache/maven-resolver/commit/
> b74f7a1e8837875b4780199f644119f55d22465d),
> i.e. the 1.0.x branch
>
> We will then proceed to have (ideally) the original committers cherry-pick
> (and tidy up an squash... if the original committers are not able to assist
> then squashing may not be practicable) those changes that have been agreed
> for 3.5.0 as summarized on the
> https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 wiki page
> (authorative source of the decisions summarized in the wiki page is the
> mail thread:
> https://mail-archives.apache.org/mod_mbox/maven-dev/201612.mbox/%3CCA%
> 2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw%40mail.gmail.com%3E
>  ).
>
> As this involves a --force push on the `master` branch, we want to get the
> approval of the committers before continuing.
>
> The vote will be open for at least 72 hours.
>
> The vote will be decided by a simple majority of valid votes cast. There is
> no veto.
>
> The vote is open to all committers.
>
> In addition, for the vote to be valid, there must be at least 3x+1 votes
> from PMC members
>
> [ ] +1: Yes
> [ ] 0:
> [ ] -1: No
>
> -Stephen
> --
> Sent from my phone
>

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

+1 (PMC & committer)

On Wed 4 Jan 2017 at 12:16, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> Hi,
>
> We have collectively managed to mess up our ability to follow the original
> release plan for 3.4.0 which was originally supposed to consist of an
> effective no-op change of Eclipse's Aether for the code after migration to
> Apache's Maven Resolver plus some other orthogonal changes around logging
> colourization and launcher script bug fixes.
>
> Given that some developer private builds of the current master branch have
> been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have been
> closed with a fixed version of 3.4.0.
>
> For us to release a 3.4.0 with those fixes reverted, could cause confusion
> with our user community.
>
> Additionally the informal practice of keeping existing integration tests
> as RTC has not been followed, leading to some people to question whether
> the integration tests remain valid.
>
> For all the above reasons it is proposed to do *all* the following as an
> whole:
>
> 1. In git://git.apache.org/maven.git we will rename the current master
> branch to `pre-reset-master` and recreate `master`
> as bce33aa2662a51d18cb00347cf2fb174dc195fb1 (
> https://github.com/apache/maven/commit/bce33aa2662a51d18cb00347cf2fb174dc195fb1
> )
>
> 2. In git://git.apache.org/maven-integration-testing.git we will rename
> the current master branch to `pre-reset-master` and recreate `master`
> as f31241ad6cb6474e559289f1bd7110ea5d5a4fba (
> https://github.com/apache/maven-integration-testing/commit/f31241ad6cb6474e559289f1bd7110ea5d5a4fba
> )
>
> 3. In git://git.apache.org/maven-resolver.git we will rename the current
> master branch to `pre-reset-master` and recreate `master`
> as b74f7a1e8837875b4780199f644119f55d22465d (
> https://github.com/apache/maven-resolver/commit/b74f7a1e8837875b4780199f644119f55d22465d),
> i.e. the 1.0.x branch
>
> We will then proceed to have (ideally) the original committers cherry-pick
> (and tidy up an squash... if the original committers are not able to assist
> then squashing may not be practicable) those changes that have been agreed
> for 3.5.0 as summarized on the
> https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 wiki page
> (authorative source of the decisions summarized in the wiki page is the
> mail thread:
> https://mail-archives.apache.org/mod_mbox/maven-dev/201612.mbox/%3CCA%2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw%40mail.gmail.com%3E
>  ).
>
> As this involves a --force push on the `master` branch, we want to get the
> approval of the committers before continuing.
>
> The vote will be open for at least 72 hours.
>
> The vote will be decided by a simple majority of valid votes cast. There
> is no veto.
>
> The vote is open to all committers.
>
> In addition, for the vote to be valid, there must be at least 3x+1 votes
> from PMC members
>
> [ ] +1: Yes
> [ ] 0:
> [ ] -1: No
>
> -Stephen
> --
> Sent from my phone
>
-- 
Sent from my phone

[VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

Hi,

Given that some developer private builds of the current master branch have
been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have been
closed with a fixed version of 3.4.0.

For us to release a 3.4.0 with those fixes reverted, could cause confusion
with our user community.

Additionally the informal practice of keeping existing integration tests as
RTC has not been followed, leading to some people to question whether the
integration tests remain valid.

For all the above reasons it is proposed to do *all* the following as an
whole:

As this involves a --force push on the `master` branch, we want to get the
approval of the committers before continuing.

The vote will be open for at least 72 hours.

The vote will be decided by a simple majority of valid votes cast. There is
no veto.

The vote is open to all committers.

In addition, for the vote to be valid, there must be at least 3x+1 votes
from PMC members

[ ] +1: Yes
[ ] 0:
[ ] -1: No

-Stephen
--
Sent from my phone

Re: Re: [VOTE] Releasing Wagon 2.11 - Cancel

2017-01-04 Thread Dan Tran

I would vote for 2.11.1 same practice at maven core


-Dan

On Wed, Jan 4, 2017 at 1:22 AM, Michael Osipov <1983-01...@gmx.net> wrote:

> If so, I would drop 2.11 altogether and go with 2.12.
>
> > Gesendet: Mittwoch, 04. Januar 2017 um 08:47 Uhr
> > Von: "Hervé BOUTEMY" 
> > An: "Maven Developers List" 
> > Betreff: Re: [VOTE] Releasing Wagon 2.11 - Cancel
> >
> > on git, AFAIK, going to 2.11.1 seems the best practice (removing tag in
> origin
> > repo is not reliable given people who have copied it won't have it
> removed
> > automatically)
> >
> > Regards,
> >
> > Hervé
> >
> > Le mardi 3 janvier 2017, 18:59:15 CET Dan Tran a écrit :
> > > I reverted the poms back to 2.11-SNAPSHOT not keep the tag for now
> since
> > > some ppl may object removing remote history.
> > >
> > > so we can keep the tag and move to 2.11.1-SNAPSHOT or remove
> wagon-2.11 tag
> > > and move on
> > >
> > > -Dan
> > >
> > > On Tue, Jan 3, 2017 at 6:08 PM, Dan Tran  wrote:
> > > > yes I can.  so it is ok to remove the tag?
> > > >
> > > > -D
> > > >
> > > > On Tue, Jan 3, 2017 at 2:01 PM, Michael Osipov 
> > > >
> > > > wrote:
> > > >> Am 2016-12-28 um 19:46 schrieb Dan Tran:
> > > >>> Hi
> > > >>>
> > > >>> I am going to cancel this vote due to inconsistent test failure at
> > > >>> wagon-http provider on huge download test.
> > > >>
> > > >> Can you please rollback release commits in the repo?
> > > >>
> > > >> Michael
> > > >>
> > > >> On Wed, Dec 28, 2016 at 7:08 AM, Michael Osipov 
> wrote:
> > > >>> Am 2016-12-28 um 06:05 schrieb Dan Tran:
> > >  i still see the same timeout error on the jetty8 branch. No issue
> at
> > > 
> > > > master
> > > >
> > > > [ERROR] Failed to execute goal
> > > > org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
> > > > (default-test) on project wagon-http: There was a timeout or
> other
> > > > error in the fork -> [Help
> > > > 1]org.apache.maven.lifecycle.LifecycleExecutionException:
> Failed to
> > > > execute goal org.apache.maven.plugins:maven
> > > > -surefire-plugin:2.18.1:test
> > > > (default-test) on project wagon-http: There was a timeout or
> other
> > > > error in the fork
> > > >
> > > > at org.apache.maven.lifecycle.int
> > > >
> > > > ernal.MojoExecutor.execute(Moj
> > > > oExecutor.java:212)
> > > 
> > >  I have now extended tests to other Linux distros:
> > > 
> > >  Fedora 25, 64 bit:
> > >  OpenJDK 8 Update 111: pass
> > > 
> > >  CentOS 7, 64 bit:
> > >  OpenJDK 8 Update 111: pass
> > >  OpenJDK 7 Update 121: pass*
> > > 
> > >  *This is actually your combo which works for me, but not for
> you...
> > > 
> > >  Additionally, I added this version to Maven 3.4.0-SNAPSHOT and
> ran ITs
> > >  on
> > >  Windows 10, Fedora 25 and FreeBSD 10.3-RELEASE. All passed.
> > > 
> > > 
> > > 
> > >  Michael
> > > 
> > >  
> -
> > >  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
> >
> >
> >
> > -
> > 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: Re: [VOTE] Releasing Wagon 2.11 - Cancel

If so, I would drop 2.11 altogether and go with 2.12.

> Gesendet: Mittwoch, 04. Januar 2017 um 08:47 Uhr
> Von: "Hervé BOUTEMY" 
> An: "Maven Developers List" 
> Betreff: Re: [VOTE] Releasing Wagon 2.11 - Cancel
>
> on git, AFAIK, going to 2.11.1 seems the best practice (removing tag in 
> origin 
> repo is not reliable given people who have copied it won't have it removed 
> automatically)
> 
> Regards,
> 
> Hervé
> 
> Le mardi 3 janvier 2017, 18:59:15 CET Dan Tran a écrit :
> > I reverted the poms back to 2.11-SNAPSHOT not keep the tag for now since
> > some ppl may object removing remote history.
> > 
> > so we can keep the tag and move to 2.11.1-SNAPSHOT or remove wagon-2.11 tag
> > and move on
> > 
> > -Dan
> > 
> > On Tue, Jan 3, 2017 at 6:08 PM, Dan Tran  wrote:
> > > yes I can.  so it is ok to remove the tag?
> > > 
> > > -D
> > > 
> > > On Tue, Jan 3, 2017 at 2:01 PM, Michael Osipov 
> > > 
> > > wrote:
> > >> Am 2016-12-28 um 19:46 schrieb Dan Tran:
> > >>> Hi
> > >>> 
> > >>> I am going to cancel this vote due to inconsistent test failure at
> > >>> wagon-http provider on huge download test.
> > >> 
> > >> Can you please rollback release commits in the repo?
> > >> 
> > >> Michael
> > >> 
> > >> On Wed, Dec 28, 2016 at 7:08 AM, Michael Osipov  wrote:
> > >>> Am 2016-12-28 um 06:05 schrieb Dan Tran:
> >  i still see the same timeout error on the jetty8 branch. No issue at
> >  
> > > master
> > > 
> > > [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
> > > (default-test) on project wagon-http: There was a timeout or other
> > > error in the fork -> [Help
> > > 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> > > execute goal org.apache.maven.plugins:maven
> > > -surefire-plugin:2.18.1:test
> > > (default-test) on project wagon-http: There was a timeout or other
> > > error in the fork
> > > 
> > > at org.apache.maven.lifecycle.int
> > > 
> > > ernal.MojoExecutor.execute(Moj
> > > oExecutor.java:212)
> >  
> >  I have now extended tests to other Linux distros:
> >  
> >  Fedora 25, 64 bit:
> >  OpenJDK 8 Update 111: pass
> >  
> >  CentOS 7, 64 bit:
> >  OpenJDK 8 Update 111: pass
> >  OpenJDK 7 Update 121: pass*
> >  
> >  *This is actually your combo which works for me, but not for you...
> >  
> >  Additionally, I added this version to Maven 3.4.0-SNAPSHOT and ran ITs
> >  on
> >  Windows 10, Fedora 25 and FreeBSD 10.3-RELEASE. All passed.
> >  
> >  
> >  
> >  Michael
> >  
> >  -
> >  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
> 
> 
> 
> -
> 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: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)