Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

Am 12/31/16 um 03:27 schrieb Christian Schulte: > Am 12/29/16 um 13:49 schrieb Robert Scholte: >> My worries are more about: how to manage which issues should be cherry >> picked and who decides that list. Otherwise we might end up in the same >> situation. E.g. do we have to do a vote on the

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

Am 12/31/16 um 03:27 schrieb Christian Schulte: > Am 12/29/16 um 13:49 schrieb Robert Scholte: >> My worries are more about: how to manage which issues should be cherry >> picked and who decides that list. Otherwise we might end up in the same >> situation. E.g. do we have to do a vote on the

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

Am 12/29/16 um 13:49 schrieb Robert Scholte: > My worries are more about: how to manage which issues should be cherry > picked and who decides that list. Otherwise we might end up in the same > situation. E.g. do we have to do a vote on the branch (which might cover > multiple issues but

[GitHub] maven-surefire issue #137: Fix SUREFIRE-1239

Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/137 @jsdima Thx for contributing. Pls close this PR. --- 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

Re: [VOTE] Releasing Wagon 2.11

I just pushed another commit to the branch with your changes. The job does not really work on Windows [1], it simply takes too long to complete on the Windows Server 2012. [1] https://builds.apache.org/job/maven-wagon-jetty8-windows/2/org.apache.maven.wagon$wagon-http/console Am 2016-12-29

Re: svn commit: r1776513 - in /maven/plugins/trunk/maven-dependency-plugin/src/it/projects: copy-from-remote-repository/verify.groovy unpack-from-remote-repository/verify.groovy

Am 12/30/16 um 19:05 schrieb Stephen Connolly: > Focus on the versions we have released. That IT also fails with Maven 3.3.9 due to the same reason. [ERROR] The following builds failed: [ERROR] * projects\basic-features\space & special char\pom.xml

Re: svn commit: r1776513 - in /maven/plugins/trunk/maven-dependency-plugin/src/it/projects: copy-from-remote-repository/verify.groovy unpack-from-remote-repository/verify.groovy

Am 12/30/16 um 22:06 schrieb Christian Schulte: > Am 12/30/16 um 19:05 schrieb Stephen Connolly: >> Given that I'm not seeing any objections yet to throwing out 3.4.x and >> redoing via cherry-pick as 3.5.x I think we should forget about any tests >> run with 3.4.0-SNAPSHOTs >> >> Focus on the

Re: svn commit: r1776513 - in /maven/plugins/trunk/maven-dependency-plugin/src/it/projects: copy-from-remote-repository/verify.groovy unpack-from-remote-repository/verify.groovy

Am 12/30/16 um 19:05 schrieb Stephen Connolly: > Given that I'm not seeing any objections yet to throwing out 3.4.x and > redoing via cherry-pick as 3.5.x I think we should forget about any tests > run with 3.4.0-SNAPSHOTs > > Focus on the versions we have released. The IT is running with

[GitHub] maven-surefire issue #137: Fix SUREFIRE-1239

Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/137 @jsdima Long time I was thinking about deleting the class `ThreadedStreamConsumer`. It looks like old mechanism where data was populated from multiple `ForkStarter`s but this is no

[GitHub] maven-surefire issue #137: Fix SUREFIRE-1239

Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/137 @jsdima The constructor of `BlockingQueue` takes capacity of 2xE09 which practically means no limitation. The only operation which can block is `queue.take()`. What call sequences

Re: svn commit: r1776513 - in /maven/plugins/trunk/maven-dependency-plugin/src/it/projects: copy-from-remote-repository/verify.groovy unpack-from-remote-repository/verify.groovy

Given that I'm not seeing any objections yet to throwing out 3.4.x and redoing via cherry-pick as 3.5.x I think we should forget about any tests run with 3.4.0-SNAPSHOTs Focus on the versions we have released. On Fri 30 Dec 2016 at 17:17, Guillaume Boué wrote: > > > Le

Re: svn commit: r1776513 - in /maven/plugins/trunk/maven-dependency-plugin/src/it/projects: copy-from-remote-repository/verify.groovy unpack-from-remote-repository/verify.groovy

Le 30/12/2016 à 17:21, Christian Schulte a écrit : Am 12/30/16 um 11:00 schrieb Guillaume Boué: Hi Christian, I remember adding those 2 ITs after raising a concern on dev (see attached mail). They were passing with 3.3.9 and latest 3.4.0 at that time. Is there an issue updating those tests

Re: svn commit: r1776513 - in /maven/plugins/trunk/maven-dependency-plugin/src/it/projects: copy-from-remote-repository/verify.groovy unpack-from-remote-repository/verify.groovy

I'm developing both on Windows and on a Ubuntu VM. The 2 ITs passed with the two systems with 3.0.5, 3.3.9 and 3.4.0 before the log format change in MNG-5457. I went ahead and committed an update to take account for that (the tests no longer rely on reading the logs). If you want to test unit

Re: svn commit: r1776513 - in /maven/plugins/trunk/maven-dependency-plugin/src/it/projects: copy-from-remote-repository/verify.groovy unpack-from-remote-repository/verify.groovy

Am 12/30/16 um 11:00 schrieb Guillaume Boué: > Hi Christian, > > I remember adding those 2 ITs after raising a concern on dev (see > attached mail). They were passing with 3.3.9 and latest 3.4.0 at that time. > > Is there an issue updating those tests with regard to MNG-5457? I > noticed this

Re: [VOTE] Releasing Wagon 2.11

I have tested that code and read a bit about sparse files. Tests first: I had on average 65 s on Windows 10, it is down now to 50 to 55 seconds. The huge problem is that we cannot use @BeforeClass to create the file once because JUnit pre-annotations does not support hat. To the sparse stuff:

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

Am 12/30/16 um 09:01 schrieb Robert Scholte: > On Thu, 29 Dec 2016 18:57:56 +0100, Hervé BOUTEMY > wrote: > >> perhaps maven-resolver will require same reset > > +1 > > IMO we forgot to do a release with the original Aether code with the new > GAVs. > Keep in mind

Re: svn commit: r1776513 - in /maven/plugins/trunk/maven-dependency-plugin/src/it/projects: copy-from-remote-repository/verify.groovy unpack-from-remote-repository/verify.groovy

Am 12/30/16 um 15:47 schrieb Christian Schulte: > Am 12/30/16 um 11:00 schrieb Guillaume Boué: >> Is there an issue updating those tests with regard to MNG-5457? > > I do not have a Windows box. Issue was due to the ITs failing on > Windows. I verified the scripts compile with groovy locally.

Re: svn commit: r1776513 - in /maven/plugins/trunk/maven-dependency-plugin/src/it/projects: copy-from-remote-repository/verify.groovy unpack-from-remote-repository/verify.groovy

Am 12/30/16 um 11:00 schrieb Guillaume Boué: > Is there an issue updating those tests with regard to MNG-5457? I do not have a Windows box. Issue was due to the ITs failing on Windows. I verified the scripts compile with groovy locally. Currently there still seems to be an issue with the Windows

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

What hash do we want to reset resolved to? (We will be *renaming* master in all cases so that the history is available... just not on master) On Fri 30 Dec 2016 at 08:02, Robert Scholte wrote: > On Thu, 29 Dec 2016 18:57:56 +0100, Hervé BOUTEMY > >

[GitHub] maven-surefire issue #137: Fix SUREFIRE-1239

Github user jsdima commented on the issue: https://github.com/apache/maven-surefire/pull/137 @Tibor17 >I am interested in this problem because as you said the plugin hangs. Why the plugin hanged, do you have explanation? It depends on a size of `private final

Re: svn commit: r1776513 - in /maven/plugins/trunk/maven-dependency-plugin/src/it/projects: copy-from-remote-repository/verify.groovy unpack-from-remote-repository/verify.groovy

Hi Christian, I remember adding those 2 ITs after raising a concern on dev (see attached mail). They were passing with 3.3.9 and latest 3.4.0 at that time. Is there an issue updating those tests with regard to MNG-5457? I noticed this is the 5th commit changing it (which I think is a lot),

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

On Thu, 29 Dec 2016 18:57:56 +0100, Hervé BOUTEMY wrote: perhaps maven-resolver will require same reset +1 IMO we forgot to do a release with the original Aether code with the new GAVs. Robert and we'll need to define which convention to use on Jira when