Cannot edit or comment on Wiki pages

Hi, user name is "schulte". I am not sure about this, but I think I do not have permission to do anything in the Wiki. I can read everything, but cannot edit things or comment on things. Regards, -- Christian - To unsubscribe,

Re: [VOTE] Releasing Wagon 2.11 - Cancel

Am 2017-01-04 um 03:59 schrieb Dan Tran: 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 I'd drop 2.11 altogether and re-run 2.11. I

Re: Cannot edit or comment on Wiki pages

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

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

Github user jsdima closed the pull request at: https://github.com/apache/maven-surefire/pull/137 --- 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 #137: Fix SUREFIRE-1239

Github user jsdima commented on the issue: https://github.com/apache/maven-surefire/pull/137 you are welcome --- 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

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

Just to confirm: I agree on the "Agreed changes" too I'd like to add for 3.5.0: By Stephen: MNG-5824 - Support MAVEN_ARGS environment variable as a way of supplying default command line arguments MNG-5836 - logging config is overwritten by $M2_HOME/lib/ext/*.jar MNG-5946 - Fix links etc. in

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

https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 is updated with these scope changes. We still have 24 JIRAs under consideration... plus we need to decide on the commits that do not have a JIRA On Tue, 3 Jan 2017 at 13:55 Robert Scholte wrote: > Just to

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

I believe we have consensus, here is the final call for anyone objecting to the plan to have their opinions considered. Here is the draft of the proposal for the vote: NOTE: THIS IS *NOT* THE VOTE -BEGIN DRAFT- Hi, We have collectively managed to mess up our ability to follow the

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

I am +100 on that. Thanks for taking the initiative to get things back on track. Manfred Stephen Connolly wrote on 2017-01-03 09:40: > I believe we have consensus, here is the final call for anyone objecting to > the plan to have their opinions considered. > > Here is the draft of the proposal

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

Seconded on both I'll update the wiki page tomorrow On Tue 3 Jan 2017 at 21:44, Michael Osipov wrote: > Am 2017-01-02 um 21:34 schrieb Stephen Connolly: > > > On 2 January 2017 at 20:15, Michael Osipov wrote: > > > > > MNG-6029, > > > > >

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

Am 2017-01-03 um 15:19 schrieb Stephen Connolly: https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 is updated with these scope changes. We still have 24 JIRAs under consideration... plus we need to decide on the commits that do not have a JIRA For my issue-less commits:

Re: [VOTE] Releasing Wagon 2.11 - Cancel

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:

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

Am 01/03/17 um 14:55 schrieb Robert Scholte: > Unscrubbed: > MNG-5670 - ConcurrentModificationException during > DefaultMaven.newRepositorySession This is related to MNG-6053 and MNG-6105. You can see that there is a commit @MNG-6105 touching 'MavenRepositorySystemUtils' as well. Should be

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

Am 2017-01-02 um 21:34 schrieb Stephen Connolly: On 2 January 2017 at 20:15, Michael Osipov wrote: MNG-6029, I'd second this for 3.5.1 I have concerns with introducing for 3.5.0 as it affects how the classpath gets built and could cause behaviour differences between

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

MNG- WONTFIX upgrade m-assembly-p to 3.0.0 Created MNG-6148 for this. There are more plugins effected by this, but I guess these were updated in the general "update plugins" ticket. IMO we should bind all plugin updates required for Java9 to this issue. For me M3.5.1 is good

Re: [VOTE] Releasing Wagon 2.11 - Cancel

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. >>

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

Re: [VOTE] Releasing Wagon 2.11 - Cancel

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.

Re: [VOTE] Releasing Wagon 2.11

I have made some concluding tests on my machine at work because my home machine is so fast that you don't see a difference if you change something. My tests are two-fold: improve HugeFileDownloadTest and manually reconstruct with pure Jetty and HttpClient (same versions). First of all sparse