Re: $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS

This is the Jenkinsfile project... I'll get the config right yet! On Sun 1 Jan 2017 at 20:24, Apache Jenkins Server wrote: The Apache Jenkins build system has built $PROJECT_NAME (build #$BUILD_NUMBER) Status: $BUILD_STATUS Check console output at $BUILD_URL to

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

You should be able to edit. If not ping Hervé Yes there are changes between 3.2.x and 3.3.9, what we want from 3.5.0 is to make the only behaviour change be a no-op for switching aether for resolver... after that 3.5.1 can fix bugs On Sun 1 Jan 2017 at 22:52, Christian Schulte

Re: Build failed in Jenkins: core-it-maven-3-win #1433

Really no one knows why that IT has started to fail sporadically on Windows? Am 01/01/17 um 23:06 schrieb Apache Jenkins Server: > See > > Changes: > > [stephen.alan.connolly] hopefully the final Jenkinsfile fix > >

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

OK, thanks for confirming this. Le 01/01/2017 à 23:44, Christian Schulte a écrit : Am 01/01/17 um 18:44 schrieb Guillaume Boué: There is a commit about MRESOLVER-9 in tag 2.11 of Wagon:

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

Am 01/01/17 um 16:09 schrieb Stephen Connolly: > If you want to know the current status check > https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 Can I edit that page myself? User name is "schulte". Regarding the drop in replacement for 3.3.9: MNG-2199 was already working in Maven

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

Am 01/01/17 um 18:44 schrieb Guillaume Boué: > > There is a commit about MRESOLVER-9 in tag 2.11 of Wagon: > https://git1-us-west.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=f244ece2eee01500e4b1bc334b8dcd35b47f9422. > > I'm unsure whether it is safe to use this tag if MRESOLVER-9 doesn't

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

Le dimanche 1 janvier 2017, 18:44:52 CET Guillaume Boué a écrit : > This is the list of JIRA issues that targets colourised logging / are > related to it: > > MNG-3507 ANSI color logging for improved output visibility This is > the > root JIRA issue. +1 > MNG-3705 Expression:

Re: Using the Maven API outside of a plugin?

Hi, you may want to have look at Apache Taverna's plugin system which did something similar. War story below.. We initially (2007) used Maven dependencies directly by parsing pom.xml dependencies and using a set of repositories, but found this very fragile because of versioning mismatches when

Re: Using the Maven API outside of a plugin?

Someone pointed me once to https://github.com/nanosai/modrun which seems to match your requirements. I haven't tried it. Robert On Sun, 01 Jan 2017 19:00:28 +0100, wrote: On 2017-01-01T17:37:26 +0100 "Robert Scholte" wrote: Hi,

Re: Using the Maven API outside of a plugin?

On 2017-01-01T17:37:26 +0100 "Robert Scholte" wrote: > Hi, > > doing this outside the context of Maven is probably hard to do. What you > at least need is the maven-artifact-resolver[1] (that's the project where > the development of Eclipses Aether[2] continues),

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

This is the list of JIRA issues that targets colourised logging / are related to it: MNG-3507ANSI color logging for improved output visibility This is the root JIRA issue. MNG-3705Expression: ${executedProject} doesn't work in reports SVN revisions

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

Le 01/01/2017 à 01:55, Michael Osipov a écrit : I just went through the list my issues. Here is a safe list I would merge/cherry-pick into new master: FIX-3.5.0: MNG-5457, Note: this is dependant upon MRESOLVER-2 (commit

Re: GitHub pull requests without JIRA issue

on "since these pages are managed via cms.apache.org/" these pages are managed through svn, ie either edited locally or through CMS. CMS is necessary only to build and publish the generated content then for site, a PR is sufficient in general: will be integrated manually to svn Regards, Hervé

Re: Using the Maven API outside of a plugin?

Hi, doing this outside the context of Maven is probably hard to do. What you at least need is the maven-artifact-resolver[1] (that's the project where the development of Eclipses Aether[2] continues), though is has not been released yet, so right now using Aether would be an option.

Re: GitHub pull requests without JIRA issue

Hi Mirko, The JIRA for these pages is MNGSITE, but is often not required (tracking such changes don't really have value) A PR is hard, since these pages are managed via cms.apache.org/ These changes have a small workflow and and can be published within minutes. Robert On Sun, 01 Jan 2017

GitHub pull requests without JIRA issue

Hello PMCs et al, I commented on a PR on GitHub a while ago with a change to documentation of the Maven site plugin. This slipped through my fingers and now the reporter asked how to submit patches to the Apache Maven project. I guess this is documented here (

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

If you want to know the current status check https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 On 31 December 2016 at 20:10, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Here are the changes in current master since 3.3.9 (with some minor > changes omitted) > > Issue

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

On 1 January 2017 at 04:42, Christian Schulte wrote: > Am 12/31/16 um 21:10 schrieb Stephen Connolly: > > Here are the changes in current master since 3.3.9 (with some minor > changes > > omitted) > > > > Issue ID Target Version Summary > > ==

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

On 1 January 2017 at 00:55, Michael Osipov wrote: > I just went through the list my issues. Here is a safe list I would > merge/cherry-pick into new master: > > FIX-3.5.0: > MNG-5457, Should not affect behaviour: I'll second > MNG-5567, Affects behaviour, I

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

MNG-5962: I'll second that one MNG-5958: I think this one is debatable as it stops 3.5.0 from being a drop-in behaviour replacement of 3.3.9, but I don't feel strongly enough to push it to 3.5.1 MNG-6117: Ditto for 5958, you'll need somebody to second this one for 3.5.0. I'll second it for 3.5.1

Using the Maven API outside of a plugin?

Apologies if this isn't an appropriate subject for this list. I tried the user list and got no response. Perhaps it is more of a development question... Hello. I'm writing a small program to analyze the dependencies of Maven projects. There are numerous examples of how to do this from within a

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

Am 2017-01-01 um 10:26 schrieb Stephen Connolly: On 1 January 2017 at 00:55, Michael Osipov wrote: MNG-5963, MNG-6137 I couldn't find them in my list... note to self, double check... note to michael, can you confirm I distilled from your list, filtered git log and

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

Am 2017-01-01 um 04:51 schrieb Christian Schulte: Am 01/01/17 um 01:55 schrieb Michael Osipov: Undecided: MNG-5708: fixed by Christian's work Should not be done in that release. Let's ship all bugfixes affecting resolution together - not just one after the other. All or nothing. So nothing.

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

We need to get a release that is *the same as 3.3.9 only with aether swapped for resolver* first IMHO. That was the original plan... Then people started wanting to add bug fixes and lots of other stuff. The point of a reset is to return to the original plan. Bugs orthogonal to the

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

I thought you had said that it was a regression introduced in 3.0, so if prerequisites is 2.x then you should resolve the "fixed" way as that was the way of 2.x that you are *restoring* The only reason for the bug reproduction on [3.0,3.4) is because people developing against the 3.x versions

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

On 1 January 2017 at 00:55, Michael Osipov wrote: > MNG-5963, MNG-6137 I couldn't find them in my list... note to self, double check... note to michael, can you confirm Otherwise I have updated the wiki with your proposals (some of which were seconds and moved things

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

We cannot update the JIRA issues until after we do the reset On 1 January 2017 at 04:51, Christian Schulte wrote: > I think it would be easier if we just update the JIRA issues and set the > version the issue will be shipped in. We already have a 3.5.0 version > available. That

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

Am 01/01/17 um 08:23 schrieb Christian Schulte: > Am 01/01/17 um 08:18 schrieb Christian Schulte: >> Once more I asked someone to test a snapshot and provided a link to >> Jenkins. That's where all those commits come from. I hope I'll get >> feedback on this one and that could again lead to