Re: Roadmap to the next Maven release (Re: Improving Jenkins)

Am 12/23/16 um 10:33 schrieb Stephen Connolly: > Ok, so I think we need to change how we describe things a bit. > > Project resolution starts from a clean baseline. If you have a project with > zero dependencies (other than those implicit in being a java project say... > which means the JRE

[GitHub] maven-release pull request #10: makes the release:branch goal ask for branch...

GitHub user hgschmie opened a pull request: https://github.com/apache/maven-release/pull/10 makes the release:branch goal ask for branch name if not given Make branchName in the BranchReleaseMojo no longer required. Adds the InputVariablesPhase to the list of branch phases;

Next version for MPLUGIN in JIRA

Hi, For MPLUGIN, the only unreleased version in JIRA is currently 3.5.1, but the version in the POM themselves is 3.6-SNAPSHOT. Should the version in JIRA be changed, or can I update the POM versions? I'd lean on updating JIRA based on the current version history (and maybe even to 3.6.0 to

Re: The failing MNG-3599 tests

Well now after several repeats still no sign of the failure when running with -llr On Wed 11 Jan 2017 at 21:08, Christian Schulte wrote: > Am 01/11/17 um 17:53 schrieb Stephen Connolly: > > > Yes... oh and --legacy-local-repository fixed the tests: > > > >

[GitHub] maven-wagon pull request #30: [WAGON-458] FTPSClient for Wagon

Github user pono closed the pull request at: https://github.com/apache/maven-wagon/pull/30 --- 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

[GitHub] maven-wagon issue #22: Implementation for Secure FTP (FTPS protocol)

Github user michael-o commented on the issue: https://github.com/apache/maven-wagon/pull/22 #30 introduced an {{FTPSWagon}}. Is this PR obsolete? I know that FTPS != FTP with TLS, isn't it? --- If your project is set up for it, you can reply to this email and have your reply appear

[GitHub] maven-wagon issue #28: Add support for detecting and using of KiTTY's klink....

Github user michael-o commented on the issue: https://github.com/apache/maven-wagon/pull/28 Please create a JIRA issue for that an I will merge the 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

Re: The failing MNG-3599 tests

Am 01/11/17 um 17:53 schrieb Stephen Connolly: > Yes... oh and --legacy-local-repository fixed the tests: > https://builds.apache.org/job/maven-jenkinsfile/job/mng-3599/4/testReport/ Can you re-run the test on windows multiple times? The failure has not been reproducible so far. It succeeds a

Re: [IT MNG-5958]: Please review integration test for MNG-5958

Am 01/11/17 um 15:05 schrieb Anton Tanasenko: > I'll submit a PR in these couple of days, if it waits a little bit. No hurry here. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail:

Re: maven-integration-testing git commit: [MNG-3599] Need to use --legacy-local-repository on newer maven versions

The stability of tests is more important than anything else from my POV As far as we correctly track the issue we can temporarily add it On Wed, Jan 11, 2017 at 8:33 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Well it also only seems to be affecting the Windows builds,

Re: maven-integration-testing git commit: [MNG-3599] Need to use --legacy-local-repository on newer maven versions

Well it also only seems to be affecting the Windows builds, so my analysis may be partly incorrect But it does fix the test Unless I hear otherwise in the next couple of hours I'll merge and retrigger the current branches so we can get an all clear on them On Wed 11 Jan 2017 at 19:25, Robert

Re: maven-integration-testing git commit: [MNG-3599] Need to use --legacy-local-repository on newer maven versions

Yes, please make an issue for 3.5.1 "The issue is that wagon comes from a different repository URL and we are storing the proxy URL that the artifact came from IIUC" This looks odd to me. This would mean that if the enterprise/company repository get's a new URL, your local repo would

Re: maven-integration-testing git commit: [MNG-3599] Need to use --legacy-local-repository on newer maven versions

Robert, Jason, Hervé and Arnaud What do you think? Will we just commit this as is and create an issue to find a longer term fix for the issue? (I could add a FIXME to the test as a marker that we intend to fix the test more correctly at a future point in time) On Wed 11 Jan 2017 at 17:02,

Re: maven-integration-testing git commit: [MNG-3599] Need to use --legacy-local-repository on newer maven versions

I don't like this... but it fixes the test... unless anyone has a better proposal I will merge this to master On 11 January 2017 at 13:57, wrote: > Repository: maven-integration-testing > Updated Branches: > refs/heads/mng-3599 03c07e10b -> a27d19f88 > > > [MNG-3599] Need

Re: The failing MNG-3599 tests

By yes I mean that each tes run starts all the integration tests from a clean build but I do pre-populate the local repo with the webdav wagon: https://github.com/apache/maven-integration-testing/blob/mng-3599/core-it-suite/src/test/resources/bootstrap/group-7/pom.xml#L46 The issue is that that

Re: The failing MNG-3599 tests

Yes... oh and --legacy-local-repository fixed the tests: https://builds.apache.org/job/maven-jenkinsfile/job/mng-3599/4/testReport/ On 11 January 2017 at 15:23, Arnaud Héritier wrote: > Are we starting from an empty local repo each time ? > > On Wed, Jan 11, 2017 at 3:00

Re: The failing MNG-3599 tests

Are we starting from an empty local repo each time ? On Wed, Jan 11, 2017 at 3:00 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > https://builds.apache.org/job/maven-jenkinsfile/job/mng- > 3599/3/testReport/org.apache.maven.it/MavenITmng3599useHttpProxyForW >

Re: [IT MNG-5958]: Please review integration test for MNG-5958

I'll submit a PR in these couple of days, if it waits a little bit. 2017-01-11 0:54 GMT+02:00 Christian Schulte : > Am 01/10/17 um 09:30 schrieb Anton Tanasenko: > > 3.3.9 (in 5805) introduced an additional syntax for specifying lifecycle > > goals as > > '<..>< >

Re: The failing MNG-3599 tests

https://builds.apache.org/job/maven-jenkinsfile/job/mng-3599/3/testReport/org.apache.maven.it/MavenITmng3599useHttpProxyForWebDAVMk2Test/testitUseHttpProxyForWebDAV_4/ So why is this consistently failing on windows? I think it is that we are running without --legacy-local-repository so I have

SimpleLogger prints to the latest value of System.out

Hello all, In issue SLF4J-389 [1] user Igor Polevoy observed that once initialized, SimpleLogger always used the same reference to System.out (or System.err). He feels that this can interfere in test where System.out is modified in order to capture log output. Commit 69be5f7f [2] ensures

The failing MNG-3599 tests

After some analysis I think this is the Wagon upgrade to 2.10 in Maven 3.3.9 I have created a mng-3599 branch in maven-integration-tests with my proposed fix (namely deactivate the old test from 3.3.9 onwards and duplicate with a new test for 3.3.9 onwards I have committed a throw-away branch in