Re: svn commit: r1775971 - /maven/plugins/trunk/maven-pmd-plugin/pom.xml

Am 12/28/16 um 14:33 schrieb Robert Scholte: > ...implement MNG-5739. Exactly. In model version 5.0.0. Until then, project and plugin and extension resolution should behave the same. It makes no sense to have different resolution strategies no-one knows about. MNG-5739 is not about plugin runtime

Re: svn commit: r1775971 - /maven/plugins/trunk/maven-pmd-plugin/pom.xml

Am 12/28/16 um 14:33 schrieb Robert Scholte: > ...revert MNG-6135. Well. If I would be a jerk, I would come up and say: But this is how Maven 2 behaved and Maven 3 must behave the same way or I will vote -1 on the release. MNG-6135 has been requested by Igor Fedorenko. Ask him about it.

Re: svn commit: r1775971 - /maven/plugins/trunk/maven-pmd-plugin/pom.xml

Am 12/28/16 um 11:44 schrieb Robert Scholte: > So can we remove the commandline option? IMHO, yes. It's just one commit to revert on Maven master. I would still like to wait a bit on my last comment on MNG-6139.

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

Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/137 @jsdima I am interested in this problem because as you said the plugin hangs. Why the plugin hanged, do you have explanation? Did you run the build with your patch? It means `mvn -P

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

This got lost on the PMC list by mistake On Thu 29 Dec 2016 at 14:33, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > I don't think we need to vote each change, but I do think we need to look > at a more RTC like model for bigger impact changes. > > I think we can trust developer

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

Am 2016-12-29 um 20:41 schrieb Christian Schulte: Am 12/29/16 um 16:04 schrieb Michael Osipov: Am 2016-12-29 um 12:18 schrieb Stephen Connolly: On ASF infra, our master branch is supposed to be a protected branch and thus cannot be reset or force-pushed without an INFRA ticket. If we want to

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

Am 12/29/16 um 16:04 schrieb Michael Osipov: > Am 2016-12-29 um 12:18 schrieb Stephen Connolly: >> On ASF infra, our master branch is supposed to be a protected branch and >> thus cannot be reset or force-pushed without an INFRA ticket. >> >> If we want to reset our master branch in order to clean

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

Am 12/29/16 um 18:57 schrieb Hervé BOUTEMY: > perhaps maven-resolver will require same reset No need for this. Reverting MRESOLVER-8 and MRESOLVER-9 will be sufficient. Those are one-line style of commits. The rest of the commits do not change any behaviour.

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

Am 12/29/16 um 12:18 schrieb Stephen Connolly: > I propose that we reset master back > to 737de43e392fc15a0ce366db98d70aa18b3f6c03, with an analogous reset of > master for the integration tests, and then immediately commit a dummy > commit so that nobody accidentally does a fast-forward push. +1

Re: [VOTE] Releasing Wagon 2.11

Am 12/28/16 um 22:50 schrieb Robert Scholte: > "That's always been that way." > Well, apparently not. Maybe it was documented that way, but I expect that > users did their dependency management which felt natural and which worked. I created an issue in JIRA to track this:

Re: [VOTE] Releasing Wagon 2.11

I have a Toshiba SSHD (MQ02ABD100H). I think the issue is that the Java code should create a sparse file to have things faster. Using setLength on a random access file probably does it depending on the OS and type of drive, but it isn't creating one in my situation. When run on Ubuntu,

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

perhaps maven-resolver will require same reset and we'll need to define which convention to use on Jira when merging code: remove "Fix Version: 3.4.0" for example, to track what features have not been merged yet Regards, Hervé Le jeudi 29 décembre 2016, 11:18:59 CET Stephen Connolly a écrit

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

I'm not against putting Jenkins config is source control: this will improve tracability. But until now, the PMC chair is supposed to be able to give karma [1]: this should be faster and IMHO remains useful. If this does not work, an INFRA ticket should be opened Regards, Hervé [1]

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

Well Jenkins is my day job I have no issues seeking time to implement pipeline for Maven as that can be seen as benefiting the Jenkins OSS community as well as proving out pipeline for real world use cases. Note the above is all pure OSS work not the for-pay side of my employers house. So I am

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

Am 2016-12-29 um 12:18 schrieb Stephen Connolly: On ASF infra, our master branch is supposed to be a protected branch and thus cannot be reset or force-pushed without an INFRA ticket. If we want to reset our master branch in order to clean out the history of the many changes and reverts to and

Re: [VOTE] Releasing Wagon 2.11

Am 2016-12-29 um 12:24 schrieb Guillaume Boué: I ran them at least 10 times, and there was the timeout issue each time. Yes, the timeout is Surefire waiting for the forked VM. I applied the patch (I had done similar tries also) but I still have the issue on Windows 10. You'll find the logs

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

thanks Stephen for picking this up. SHA-1: 737de43e392fc15a0ce366db98d70aa18b3f6c03 * [maven-release-plugin] prepare for next development iteration Yes, this is the hash I would expect to revert to. Based on the date I would expect that maven-its should be reset to SHA-1:

Re: [VOTE] Releasing Wagon 2.11

I ran them at least 10 times, and there was the timeout issue each time. Yes, the timeout is Surefire waiting for the forked VM. I applied the patch (I had done similar tries also) but I still have the issue on Windows 10. You'll find the logs attached. It seems that the download is really

[DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

On ASF infra, our master branch is supposed to be a protected branch and thus cannot be reset or force-pushed without an INFRA ticket. If we want to reset our master branch in order to clean out the history of the many changes and reverts to and fro etc, we thus need an INFRA ticket raised.

[GitHub] maven-surefire pull request #138: SUREFIRE-1309: Clarifying use of regular e...

Github user sverhagen closed the pull request at: https://github.com/apache/maven-surefire/pull/138 --- 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

[GitHub] maven-surefire issue #138: SUREFIRE-1309: Clarifying use of regular expressi...

Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/138 @sverhagen Thx for contributing. This PR was merged. Pls close it. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If