Re: I think we are ready for 3.5.0-alpha-1

Am 02/12/17 um 00:59 schrieb Michael Osipov: > Am 2017-02-12 um 00:49 schrieb Christian Schulte: >> Am 02/11/17 um 23:03 schrieb Michael Osipov: >>> The lifecylce plugins have been moved to MNG-6169. MPLUGIN has been >>> retained with 3.3 because there were failures. One IT is failing, >>>

Re: I think we are ready for 3.5.0-alpha-1

Am 2017-02-11 um 18:23 schrieb Christian Schulte: Am 02/11/17 um 18:20 schrieb Michael Osipov: Am 2017-02-11 um 18:08 schrieb Christian Schulte: Am 02/08/17 um 21:14 schrieb Michael Osipov: Am 2017-02-08 um 21:01 schrieb Stephen Connolly: I think all the important stuff is merged. I'll take

Re: I think we are ready for 3.5.0-alpha-1

Am 2017-02-11 um 18:19 schrieb Christian Schulte: Am 02/08/17 um 21:14 schrieb Michael Osipov: Am 2017-02-08 um 21:01 schrieb Stephen Connolly: I think all the important stuff is merged. I'll take a final review through and then cut alpha-1 We can still add stuff if necessary for an alpha-2

Re: I think we are ready for 3.5.0-alpha-1

Am 02/11/17 um 23:03 schrieb Michael Osipov: > The lifecylce plugins have been moved to MNG-6169. MPLUGIN has been > retained with 3.3 because there were failures. One IT is failing, > MNG-5572. I am looking into the cause right now. Out of curiosity. @Michael: Do you have a FreeBSD box or

[GitHub] maven-surefire issue #142: SUREFIRE-1330: Import provider code donated by JU...

Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/142 @britter Sure I will do it, no problem. --- 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

Re: I think we are ready for 3.5.0-alpha-1

Am 02/11/17 um 23:03 schrieb Michael Osipov: > Am 2017-02-11 um 18:23 schrieb Christian Schulte: >> Am 02/11/17 um 18:20 schrieb Michael Osipov: >>> Am 2017-02-11 um 18:08 schrieb Christian Schulte: Am 02/08/17 um 21:14 schrieb Michael Osipov: > Am 2017-02-08 um 21:01 schrieb Stephen

Re: I think we are ready for 3.5.0-alpha-1

Am 2017-02-12 um 00:49 schrieb Christian Schulte: Am 02/11/17 um 23:03 schrieb Michael Osipov: The lifecylce plugins have been moved to MNG-6169. MPLUGIN has been retained with 3.3 because there were failures. One IT is failing, MNG-5572. I am looking into the cause right now. Out of

Re: I think we are ready for 3.5.0-alpha-1

What surefire tag exactly? On Sun, Feb 12, 2017 at 1:56 AM, Christian Schulte [via Maven] < ml-node+s40175n5898195...@n5.nabble.com> wrote: > Am 02/12/17 um 00:59 schrieb Michael Osipov: > > > Am 2017-02-12 um 00:49 schrieb Christian Schulte: > >> Am 02/11/17 um 23:03 schrieb Michael Osipov: >

Re: I think we are ready for 3.5.0-alpha-1

Am 2017-02-08 um 21:14 schrieb Michael Osipov: Am 2017-02-08 um 21:01 schrieb Stephen Connolly: I think all the important stuff is merged. I'll take a final review through and then cut alpha-1 We can still add stuff if necessary for an alpha-2 but I'd much prefer to focus that on shaking out

Re: I think we are ready for 3.5.0-alpha-1

Am 02/08/17 um 21:14 schrieb Michael Osipov: > Am 2017-02-08 um 21:01 schrieb Stephen Connolly: >> I think all the important stuff is merged. I'll take a final review through >> and then cut alpha-1 >> >> We can still add stuff if necessary for an alpha-2 but I'd much prefer to >> focus that on

Re: I think we are ready for 3.5.0-alpha-1

Am 02/08/17 um 21:14 schrieb Michael Osipov: > Am 2017-02-08 um 21:01 schrieb Stephen Connolly: >> I think all the important stuff is merged. I'll take a final review through >> and then cut alpha-1 >> >> We can still add stuff if necessary for an alpha-2 but I'd much prefer to >> focus that on

Re: Version ranges and snapshots

Hi, I opened https://issues.apache.org/jira/browse/MNGSITE-300 to improve the documentation of the version order. Cheers, Jon Jon On Mon, Mar 23, 2015 at 6:39 PM, Jon Harper wrote: > Hi Hervé, > thanks. I agree that the intro is now better, but I think we need to >

Re: I think we are ready for 3.5.0-alpha-1

Am 02/08/17 um 21:14 schrieb Michael Osipov: > Am 2017-02-08 um 21:01 schrieb Stephen Connolly: >> I think all the important stuff is merged. I'll take a final review through >> and then cut alpha-1 >> >> We can still add stuff if necessary for an alpha-2 but I'd much prefer to >> focus that on

Re: I think we are ready for 3.5.0-alpha-1

Am 2017-02-11 um 18:08 schrieb Christian Schulte: Am 02/08/17 um 21:14 schrieb Michael Osipov: Am 2017-02-08 um 21:01 schrieb Stephen Connolly: I think all the important stuff is merged. I'll take a final review through and then cut alpha-1 We can still add stuff if necessary for an alpha-2

Re: I think we are ready for 3.5.0-alpha-1

Am 2017-02-11 um 18:19 schrieb Christian Schulte: Am 02/08/17 um 21:14 schrieb Michael Osipov: Am 2017-02-08 um 21:01 schrieb Stephen Connolly: I think all the important stuff is merged. I'll take a final review through and then cut alpha-1 We can still add stuff if necessary for an alpha-2

Re: I think we are ready for 3.5.0-alpha-1

Am 2017-02-11 um 18:23 schrieb Christian Schulte: Am 02/11/17 um 18:20 schrieb Michael Osipov: Am 2017-02-11 um 18:08 schrieb Christian Schulte: Am 02/08/17 um 21:14 schrieb Michael Osipov: Am 2017-02-08 um 21:01 schrieb Stephen Connolly: I think all the important stuff is merged. I'll take

Re: I think we are ready for 3.5.0-alpha-1

Am 02/11/17 um 18:20 schrieb Michael Osipov: > Am 2017-02-11 um 18:08 schrieb Christian Schulte: >> Am 02/08/17 um 21:14 schrieb Michael Osipov: >>> Am 2017-02-08 um 21:01 schrieb Stephen Connolly: I think all the important stuff is merged. I'll take a final review through and then cut

Re: I think we are ready for 3.5.0-alpha-1

Am 2017-02-11 um 15:18 schrieb Robert Scholte: In both cases I'm missing a list of what's being updated (and maybe why...). I know there were a couple of plugins for which the latest is not the greatest due to some small regressions. So without these details I'd say no. I am preparing two

Re: I think we are ready for 3.5.0-alpha-1

The list of updates should be added to the release notes, I'd say use the matching JIRA issue. branch of MNG-5967 looks good to me. On Sat, 11 Feb 2017 15:30:46 +0100, Michael Osipov wrote: Am 2017-02-11 um 15:18 schrieb Robert Scholte: In both cases I'm missing a

Re: I think we are ready for 3.5.0-alpha-1

Am 2017-02-11 um 13:56 schrieb Stephen Connolly: MNG-5934 go for it how will thenother two affect the goal of being a drop in for 3.3.9 (if the pom I am building assumes version X is default and we are now version Y) or are these just updates to the Maven core classpath? Please see the

Re: I think we are ready for 3.5.0-alpha-1

Am 2017-02-11 um 15:33 schrieb Robert Scholte: The list of updates should be added to the release notes, I'd say use the matching JIRA issue. Do you want me to add these to the issue description itself? Unless I create a JIRA issue per dependency, they won't show up in the release notes. One

Re: I think we are ready for 3.5.0-alpha-1

On Sat, 11 Feb 2017 15:46:37 +0100, Michael Osipov wrote: Am 2017-02-11 um 15:33 schrieb Robert Scholte: The list of updates should be added to the release notes, I'd say use the matching JIRA issue. Do you want me to add these to the issue description itself? Unless

[GitHub] maven-surefire issue #142: SUREFIRE-1330: Import provider code donated by JU...

Github user britter commented on the issue: https://github.com/apache/maven-surefire/pull/142 @Tibor17 this PR is for 3.0-rc1 branch not for master. Can't we integrate it into 3.0-rc1 branch right away? --- If your project is set up for it, you can reply to this email and have your

Re: [VOTE] Release Apache Maven Archetype (Plugin) version 3.0.0

+1 On Wed, 08 Feb 2017 18:17:32 +0100, Robert Scholte wrote: Hi, We solved 27 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122=12330297=Text There are still a couple of issues left in JIRA:

Re: I think we are ready for 3.5.0-alpha-1

In both cases I'm missing a list of what's being updated (and maybe why...). I know there were a couple of plugins for which the latest is not the greatest due to some small regressions. So without these details I'd say no. Robert On Sat, 11 Feb 2017 12:06:34 +0100, Michael Osipov

[GitHub] maven-surefire issue #142: SUREFIRE-1330: Import provider code donated by JU...

Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/142 @britter LGTM We have to wait for release 2.19.2. After that I will squash previous changes into one and commit to master which will be 3.0 RC1. Meanwhile we can continue on

Re: I think we are ready for 3.5.0-alpha-1

MNG-5934 go for it how will thenother two affect the goal of being a drop in for 3.3.9 (if the pom I am building assumes version X is default and we are now version Y) or are these just updates to the Maven core classpath? On Sat 11 Feb 2017 at 11:06, Michael Osipov wrote: