+1
already running beta-1 for a while now and everyone is asking me how to get a
colored build ;-)
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
+1
S.
On Tue, 4 Apr 2017 at 00:14, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hi,
>
> We solved 86 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12336084=Text
>
> In there are 324 issues left in JIRA for Maven core:
>
>
+1
On Tue, 04 Apr 2017 00:14:45 +0200, Stephen Connolly
wrote:
Hi,
We solved 86 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12336084=Text
In there are 324 issues left in JIRA for Maven core:
+1 ok for me too
2017-04-06 8:13 GMT+02:00 Chas Honton :
> +1
>
> Java 1.8.0_74
> Mac OS X 10.12.3
>
> Multi-module project with 562 goals (50 unique)
>
> Chas
>
> > On Apr 3, 2017, at 3:14 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
> >
> > Hi,
> >
> > We
+1
Java 1.8.0_74
Mac OS X 10.12.3
Multi-module project with 562 goals (50 unique)
Chas
> On Apr 3, 2017, at 3:14 PM, Stephen Connolly
> wrote:
>
> Hi,
>
> We solved 86 issues:
>
+1 non-binding after testing with a bunch of different projects on MacOS
10.11.6 (15G31)
Darwin Elliots-iMac.fios-router.home 15.6.0 Darwin Kernel Version 15.6.0:
Thu Jun 23 18:25:34 PDT 2016; root:xnu-3248.60.10~1/RELEASE_X86_64 x86_64
On Wed, Apr 5, 2017 at 7:51 PM, Stephen Connolly <
+1 after testing with a lot of different projects
On Thu 6 Apr 2017 at 00:01, Arnaud Héritier wrote:
> +1
>
> On Wed, Apr 5, 2017 at 8:42 AM, Olivier Lamy wrote:
>
> > +1
> >
> > On 4 April 2017 at 08:14, Stephen Connolly >
+1
On Wed, Apr 5, 2017 at 8:42 AM, Olivier Lamy wrote:
> +1
>
> On 4 April 2017 at 08:14, Stephen Connolly com>
> wrote:
>
> > Hi,
> >
> > We solved 86 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >
+1
On 4 April 2017 at 08:14, Stephen Connolly
wrote:
> Hi,
>
> We solved 86 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316922=12336084=Text
>
> In there are 324 issues left in JIRA for Maven core:
>
+1
Regards,
Hervé
Le mercredi 5 avril 2017, 05:17:23 CEST Raphael Ackermann a écrit :
> +1 (non binding). tested with company build.
> love the color support out of the box
I like such feedback :)
>
> On Tue, Apr 4, 2017 at 11:37 PM Tibor Digana wrote:
> > +1
+1 (non binding). tested with company build.
love the color support out of the box
On Tue, Apr 4, 2017 at 11:37 PM Tibor Digana wrote:
> +1 (binding)
>
> On Tue, Apr 4, 2017 at 12:14 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > Hi,
> >
> > We
+1 non binding, built my main app without drama, and the rest of my
personal projects are simpler
On 5 April 2017 at 09:37, Tibor Digana wrote:
> +1 (binding)
>
> On Tue, Apr 4, 2017 at 12:14 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > Hi,
> >
+1 (binding)
On Tue, Apr 4, 2017 at 12:14 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hi,
>
> We solved 86 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316922=12336084=Text
>
> In there are 324 issues left in JIRA for Maven core:
>
Hi,
+1 (binding)
Tested on a large OSGi build with 722 modules...without any issue.
Tested serveral projects of my own, some Maven extensions etc., Maven
itself, some Maven plugins and some codehaus projects etc.
Kind regards
Karl Heinz Marbaise
On 04/04/17 00:14, Stephen Connolly wrote:
+1
Looking forward to using it and spreading it to other users ;-)
Manfred
Stephen Connolly wrote on 2017-04-03 15:14:
> Hi,
>
> We solved 86 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12336084=Text
>
> In there are 324 issues left in JIRA for Maven
+1, non-binding
Tested on Windows 7 with IBM JDK 7.1. One minor regression found [1].
[1] https://issues.apache.org/jira/browse/MNG-6205
/Anders
On Tue, Apr 4, 2017 at 12:14 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hi,
>
> We solved 86 issues:
>
+1
--
Regards,
Igor
On Tue, Apr 4, 2017, at 10:21 AM, Petr Široký wrote:
> +1 (non-binding)
>
> Tested on several big projects, with dozens of different plugins. No
> issue
> found.
>
> On Tue, Apr 4, 2017 at 12:14 AM Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > Hi,
> >
+1 (non-binding)
Tested on several big projects, with dozens of different plugins. No issue
found.
On Tue, Apr 4, 2017 at 12:14 AM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hi,
>
> We solved 86 issues:
>
>
+1 (non-binding)
Tested with huge OSGi projects without problems
regards
Grzegorz Grzybek
2017-04-04 11:52 GMT+02:00 dejan2609 :
> *+1* (non binding).
>
> Tested Maven 3.5.0 on a large project with a bunch of plugins: all is
> green.
>
>
>
> --
> View this message in
*+1* (non binding).
Tested Maven 3.5.0 on a large project with a bunch of plugins: all is green.
--
View this message in context:
http://maven.40175.n5.nabble.com/VOTE-Release-Apache-Maven-3-5-0-tp5904383p5904485.html
Sent from the Maven Developers mailing list archive at Nabble.com.
Friendly reminder, all votes welcome.
Note: If this is the first time participating in a release vote for the
Apache Maven project, there are some legal requirements delegated on the
Maven project by the Apache Foundation board. One of those requirements is
that at least 3 +1 votes *by members of
+1 Non Binding.
Bring. It. On.
On 4 Apr 2017, at 10:14, Stephen Connolly wrote:
> Hi,
>
> We solved 86 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12336084=Text
--
Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
Analyzer...
stagingUrl: https://repository.apache.org/content/repositories/maven-1326
groupId: org.apache.maven
artifactId: apache-maven
version: 3.5.0
Source ZIP url exists.
Hi,
We solved 86 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12336084=Text
In there are 324 issues left in JIRA for Maven core:
Am 03/24/17 um 16:54 schrieb Karl Heinz Marbaise:
> Hi,
>
> On 24/03/17 02:17, Hervé BOUTEMY wrote:
>> we have absolutely no OSX user building Maven core ITs on his personal
>> computer?
>> seriously?
>> Or is there no core IT that shows the issue? then it has to be discovered by
>> hand?
>
> I
Not testing maven core ITs. Using multi-module project with 562 goal
invocations (50 unique goals) including three integration test suites run with
invoker plugin.
+1 tested on OS X 10.12.3, Java 1.8.0_074
++1: 3.5.0 warned about a dependent Pom problem which was not found with 3.3.9
Chas
Hi,
On 24/03/17 02:17, Hervé BOUTEMY wrote:
we have absolutely no OSX user building Maven core ITs on his personal
computer?
seriously?
Or is there no core IT that shows the issue? then it has to be discovered by
hand?
I can test today evening or tomorrow...on my Mac..
If this helps?
Kind
On 20 March 2017 at 18:18, Stephen Connolly wrote:
> Hi,
>
> We solved 15 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316922=12339665=Text
>
> There are still 10 issues left in JIRA for 3.5.0, but I do not think any
> of
+1
On Mon, 20 Mar 2017 19:18:06 +0100, Stephen Connolly
wrote:
Hi,
We solved 15 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12339665=Text
There are still 10 issues left in JIRA for 3.5.0, but I do not think any
of
we have absolutely no OSX user building Maven core ITs on his personal
computer?
seriously?
Or is there no core IT that shows the issue? then it has to be discovered by
hand?
Notice: to me, this does not mean we need a beta-2: 3.5.0 will have bugs, like
any past or future release
Regards,
+1
no issues found when building a lot of projects for myself
Regards,
Hervé
Le lundi 20 mars 2017, 18:18:06 CET Stephen Connolly a écrit :
> Hi,
>
> We solved 15 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922
> rsion=12339665=Text
>
> There are still 10
no, nothing so serious that we need a beta-2
we had no luck to hit 2 different bugs with 2 different versions of maven-
assembly-plugin, but each time, impact was limited (not ideal, but can live
with it).
I double checked, and don't hesitate everybody to do also, the current version
doees not
Anyone else have anything to report?
I think we have met the requirements to release (I'll check tomorrow)
But more feedback is always better
On Thu 23 Mar 2017 at 22:46, Olivier Lamy wrote:
> +1
>
> On 21 March 2017 at 05:18, Stephen Connolly <
>
+1
On 21 March 2017 at 05:18, Stephen Connolly wrote:
> Hi,
>
> We solved 15 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316922=12339665=Text
>
> There are still 10 issues left in JIRA for 3.5.0, but I do not think any
> of
Am 03/23/17 um 19:20 schrieb Christian Schulte:
> Am 03/23/17 um 10:08 schrieb Stephen Connolly:
>> Hervé do you think this ordering issue is serious enough to drop and run a
>> beta-2?
>>
>> IMHO no as it is just a beta and we can add it as a known issue in the
>> release notes.
>
> Unrelated to
Am 03/23/17 um 10:08 schrieb Stephen Connolly:
> Hervé do you think this ordering issue is serious enough to drop and run a
> beta-2?
>
> IMHO no as it is just a beta and we can add it as a known issue in the
> release notes.
Unrelated to this issue there has been another report regarding the
Hervé do you think this ordering issue is serious enough to drop and run a
beta-2?
IMHO no as it is just a beta and we can add it as a known issue in the
release notes.
On Thu 23 Mar 2017 at 04:15, Hervé BOUTEMY wrote:
> in short: issue MNG-6192 [1] created and fixed
>
>
Hello
+1
2017-03-23 5:14 GMT+01:00 Hervé BOUTEMY :
> in short: issue MNG-6192 [1] created and fixed
>
> Thanks for the report, both on what works and what does not work so well :)
>
> Regards,
>
> Hervé
>
> [1] https://issues.apache.org/jira/browse/MNG-6192
>
> Le
in short: issue MNG-6192 [1] created and fixed
Thanks for the report, both on what works and what does not work so well :)
Regards,
Hervé
[1] https://issues.apache.org/jira/browse/MNG-6192
Le mercredi 22 mars 2017, 05:55:36 CET dejan2609 a écrit :
> +1, it works on dozen of projects.
>
>
+1
On Wed, Mar 22, 2017 at 10:04 PM, Mark Derricutt wrote:
> On 21 Mar 2017, at 7:18, Stephen Connolly wrote:
>
> > Vote open for 72 hours.
>
> +1 non binding for me on my OSGi / tiles related builds.
>
>
> --
> Mark Derricutt
> http://www.theoryinpractice.net
>
On 21 Mar 2017, at 7:18, Stephen Connolly wrote:
> Vote open for 72 hours.
+1 non binding for me on my OSGi / tiles related builds.
--
Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
+1, it works on dozen of projects.
Minor issue is related to maven wrapper:
$ ./mvnw clean install
Downloading
https://repository.apache.org/content/repositories/maven-1325/org/apache/maven/apache-maven/3.5.0-beta-
1/apache-maven-3.5.0-beta-1-bin.zip
Hi,
tested with several project also a large OSGi build ...without any issue..
+1 from me.
Kind regards
Karl Heinz Marbaise
On 20/03/17 19:18, Stephen Connolly wrote:
Hi,
We solved 15 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12339665=Text
There are
+1
On 20 March 2017 at 18:18, Stephen Connolly wrote:
> Analyzer...
>
> stagingUrl: https://repository.apache.org/content/repositories/maven-1325
> groupId: org.apache.maven
> artifactId: apache-maven
> version: 3.5.0-beta-1
>
> Source ZIP url exists.
>
Hi,
We solved 15 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12339665=Text
There are still 10 issues left in JIRA for 3.5.0, but I do not think any
of those are blocking an beta release and perhaps could be descoped for
3.5.0:
Analyzer...
stagingUrl: https://repository.apache.org/content/repositories/maven-1325
groupId: org.apache.maven
artifactId: apache-maven
version: 3.5.0-beta-1
Source ZIP url exists.
Hi guys, I've been reminded of another issue that was supposed to go into
3.4.0 at the time but seem to have forgotten about it when the 3.4-3.5
scrubbing thing happened.
It's https://issues.apache.org/jira/browse/MNG-6025
Really minor thing that doesn't affect maven itself, but could help a lot
Yes +1 to improve withMaven with color support
2017-03-01 9:23 GMT+01:00 Arnaud Héritier :
> I'll do some tests later but yes the advice is often to not use the Maven
> Project type in Jenkins.
> Using the ansi color plugin allows to display colors. I'll probably use
> that
I'll do some tests later but yes the advice is often to not use the Maven
Project type in Jenkins.
Using the ansi color plugin allows to display colors. I'll probably use
that path and configure it by default for maven jobs and/or I'll set -B if
it's not already done ...
For freestyle jobs I'm
Yes Robert you have Right, Jenkins use -B by default
In this case I have :
- Maven Job
- Jenkins 2.19.4
Output command is :
<===[JENKINS REMOTING CAPACITY]===>channel started
Executing Maven: -B -f /data/blabla/pom.xml -s
/opt/apache-maven-3.5.0-alpha-1/conf/settings.xml -gs
bq. NOTE: in Jenkins by default the console output is ugly with maven
3.5.0-alpha-1 (see next). To fix this the Ansi Color Plugin is necessary !
this is weird. I would expect Jenksins to always run in batch-mode (-B),
which should disable Ansi.
Robert
On Mon, 27 Feb 2017 23:40:51 +0100,
On 23 February 2017 at 16:10, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hi,
>
> We solved 65 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316922=12339664=Text
>
> There are still a couple of issues left in JIRA for 3.5.0, but I do not
> think
hen.alan.conno...@gmail.com>>
> Date: Mon 27 Feb 2017 at 14:42
> Subject: Re: [VOTE] Release Apache Maven 3.5.0-alpha-1
> To: Maven Developers List <dev@maven.apache.org <mailto:dev@maven.apache.org>>
>
>
> Hervé, Robert you have commented but I do not see a vot
Hello,
+1 for me too
Tested on different projects with different kind of plugins, on MacOsX and
Linux, IDE, CLI and IT
If you want to see the details, I wrote a little post :
https://tcollignon.github.io/2017/02/27/Test-Maven-350-alpha-1.html
On 28 Feb 2017, at 7:11, Hervé BOUTEMY wrote:
> I already voted, but I'll redo:
>
> +1
+200 from me :)
--
Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt
signature.asc
tested on several projects
+1
On Mon, Feb 27, 2017 at 10:24 PM, Guillaume Boué wrote:
> +1 from me too
>
> Tested with some Tycho builds of Spring and it worked fine. Also tested on
> FreeBSD / Ubuntu / Windows without issues.
>
>
> Le 27/02/2017 à 19:11, Hervé BOUTEMY a
+1 from me too
Tested with some Tycho builds of Spring and it worked fine. Also tested
on FreeBSD / Ubuntu / Windows without issues.
Le 27/02/2017 à 19:11, Hervé BOUTEMY a écrit :
I already voted, but I'll redo:
+1
tested with many builds: it works as well as I expected (near a RC
+1
Really awesome stuff, everyone!
(I tested with a good range of projects, some of them having different
versions of some karaf-maven-plugins that tend to break with Maven updates
-- everything was smooth, though.)
2017-02-23 17:10 GMT+01:00 Stephen Connolly
+1
Did some very basic tests running CXF builds and it all seems to work OK. Not
very elaborate set of tests though.
Dan
> On Feb 27, 2017, at 9:42 AM, Stephen Connolly
> wrote:
>
> Hervé, Robert you have commented but I do not see a vote cast. I believe
I already voted, but I'll redo:
+1
tested with many builds: it works as well as I expected (near a RC confidence)
Let's fix the identified little glitches, and we'll have our 3.5.0 final :)
Regards,
Hervé
Le lundi 27 février 2017, 14:42:12 CET Stephen Connolly a écrit :
> Hervé, Robert you
alpha-quality, right? ;)
I haven't witnessed any regression, so +1
Robert
On Mon, 27 Feb 2017 15:42:12 +0100, Stephen Connolly
wrote:
Hervé, Robert you have commented but I do not see a vote cast. I believe
I
have 3 binding votes, but as one of those is
Hervé, Robert you have commented but I do not see a vote cast. I believe I
have 3 binding votes, but as one of those is mine I would be more
comfortable with some more
On 23 February 2017 at 16:10, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hi,
>
> We solved 65 issues:
>
@Stephen
The problem is no problem.
Sorry my bad during private method refactoring in an IT.
No issue.
On Sun, Feb 26, 2017 at 2:03 PM, stephenconnolly [via Maven] <
ml-node+s40175n5900267...@n5.nabble.com> wrote:
> We can investigate...
>
> Could also be an invoker issue as we are just
We can investigate...
Could also be an invoker issue as we are just effectively passing through
the parsed options
On Sun 26 Feb 2017 at 12:59, Tibor Digana
wrote:
> @Stephen
> I have an issue with system properties. Could it be caused by the Builder?
> There is no
@Stephen
I have an issue with system properties. Could it be caused by the Builder?
There is no space between *-Dtest=* and profile *-P*
clean -Dsurefire.version=2.19.2-SNAPSHOT *-Dtest=-P* surefire-junit47 test
Since this is JUnit 4.8 test only, this happened after I removed TestNG
useless
FYI, I published the reference documentation
http://maven.apache.org/ref/3-LATEST/
just did classical "mvn -Preporting site site:stage" followed by "mvn scm-
publish:publish-scm" as defined in documentation [1]
once the vote is validated, just follow the next steps to publish the
versioned
>> CLI would print a WARNING, because it shows some strange
situation that people didn't expect
Duplicates of sys props should be logged with Warning on console.
I totally agree with Herve.
Good catch, Herve!
On Sun, Feb 26, 2017 at 11:20 AM, Hervé BOUTEMY [via Maven] <
+1
tested with many builds: it works as well as I expected (near a RC confidence)
Let's fix the identified little glitches, and we'll have our 3.5.0 final :)
Regards,
Hervé
Le jeudi 23 février 2017, 16:10:18 CET Stephen Connolly a écrit :
> Hi,
>
> We solved 65 issues:
>
on this, I don't have exactly same opinion:
yes, Maven 3.5.0 should behave like Maven 3.3.9, then we should fix Maven as
much as possible and not force Surefire ITs to be changed
but if Surefire ITs define multiple times the same property on CLI, then use a
edge case, removing the demendency on
Am 02/25/17 um 17:25 schrieb Tibor Digana:
>>> There are two commits for MNG-6078 part of -alpha-1.
>
> This was caused by system property duplicates in surefire ITs.
> It is already fixed in a branch SUREFIRE_SYSPROP_DUPLICATES.
If something works with 3.3.9 but not 3.5.0, we need to fix it in
I think it might be better if we could release them into a different repo
so that the artifacts are available - just not synced to central.
Either that or we say screw it sync to central... al least if we make them
available via dist.
If we don't make available via dist, then yes we should just
I would say: all pre-final should be dropped, i.e. should not up in
Central.
However, we could make the distributions available for download.
If this is done via the staged repository or via our dist folder[1], I
don't mind; whatever fits best.
Robert
[1]
Hi,
the last two days I'm running the 3.5.0-alpha-1 here on my mac with
system installation and doing my work under usual user...not any problem
so far...
I have taken a look into the lib/ext folder where I can't find a file
similar to that which could only be there if the process has
We need to start thinking whether any of the issues so far are enough to
drop alpha-1 and run with alpha-2
IMHO we would gain more information from users if we release alpha-1 with
and ACK for the known issues and say that alpha-2 is 1-2 weeks away rather
than drop alpha-1 and wait that time for
Is it still non-critical if the user lacks write access to that directory?
On Sat, Feb 25, 2017 at 8:07 AM, Robert Scholte wrote:
> Hi,
>
> found a non-critical issue. It seems like with every Maven build, a new
> lib/ext/jansi-64-1-xxx.13 is generated.
> If
Am 2017-02-25 um 17:07 schrieb Robert Scholte:
Hi,
found a non-critical issue. It seems like with every Maven build, a new
lib/ext/jansi-64-1-xxx.13 is generated.
If this is a temp-file, I'd rather write it to the OS temp folder
instead of the Maven distribution.
This is horribly
The SNAPSHOT is therefore getting quite big 70 MB.
On Sat, Feb 25, 2017 at 5:07 PM, Robert Scholte
wrote:
> Hi,
>
> found a non-critical issue. It seems like with every Maven build, a new
> lib/ext/jansi-64-1-xxx.13 is generated.
> If this is a temp-file, I'd
>>There are two commits for MNG-6078 part of -alpha-1.
This was caused by system property duplicates in surefire ITs.
It is already fixed in a branch SUREFIRE_SYSPROP_DUPLICATES.
System props duplicates: -DreuseForks=false -DreuseForks=true
I am sure the ITs now pass because of Stepen's commit
Hi,
found a non-critical issue. It seems like with every Maven build, a new
lib/ext/jansi-64-1-xxx.13 is generated.
If this is a temp-file, I'd rather write it to the OS temp folder instead
of the Maven distribution.
Robert
On Thu, 23 Feb 2017 17:10:18 +0100, Stephen Connolly
Am 02/25/17 um 14:40 schrieb Tibor Digana:
> @Stephen
> @Michael-O
> What changed in Maven after Michael used his snapshot version of
> Maven-3.5.0-SNAPSHOT?
> Michael said that surefire failed with ForkModeIT and he tested Surefire's
> commits from HEAD to
@Stephen
@Michael-O
What changed in Maven after Michael used his snapshot version of
Maven-3.5.0-SNAPSHOT?
Michael said that surefire failed with ForkModeIT and he tested Surefire's
commits from HEAD to 502d18442113b4c6c72630dca5842e1eb287b8b0.
I followed more deeply in the commits of Surefire
We should also tip our hat to what happened to 3.4.x
On Sat 25 Feb 2017 at 11:41, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> I think we can do alpha release notes. It maybe on a sub page
>
> Thanks for picking this up (I was going to start it later today subject to
> family
I think we can do alpha release notes. It maybe on a sub page
Thanks for picking this up (I was going to start it later today subject to
family approval ;-) )
On Sat 25 Feb 2017 at 11:34, Karl Heinz Marbaise wrote:
> Hi,
>
> I have started to summarize the changes we had in
Hi,
I have started to summarize the changes we had in 3.5.0-alpha-1..
https://github.com/khmarbaise/maven-release-notes/blob/master/content/markdown/docs/3.5.0/release-notes.md
If there are any supplementals/changes/fixes etc. Please make an issue
or a pull request to it...or write here...
Am 02/24/17 um 21:03 schrieb Stephen Connolly:
> To reflect the practice we should use for these going forward
+1
I should have included -alpha-0 in those ranges right from the start.
Regards,
--
Christian
-
To unsubscribe,
To reflect the practice we should use for these going forward
On Fri 24 Feb 2017 at 19:54, Robert Scholte wrote:
> ... ,3.5.0-alpha-0)
>
> sure, effect is the same, but why not ",3.5.0-alpha-1)" to reflect an
> existing version
>
> Robert
>
> On Fri, 24 Feb 2017 20:51:18
... ,3.5.0-alpha-0)
sure, effect is the same, but why not ",3.5.0-alpha-1)" to reflect an
existing version
Robert
On Fri, 24 Feb 2017 20:51:18 +0100, Stephen Connolly
wrote:
c4cd8cf3b5e4c6d0a7f52a3d282229bda29b5f58 in maven-integration-testing
should
c4cd8cf3b5e4c6d0a7f52a3d282229bda29b5f58 in maven-integration-testing
should fix this issue
On 24 February 2017 at 19:39, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> 3.5.0 > 3.5.0-alpha-1
>
> On 24 February 2017 at 19:38, Guillaume Boué wrote:
>
>> I also ran
3.5.0 > 3.5.0-alpha-1
On 24 February 2017 at 19:38, Guillaume Boué wrote:
> I also ran the ITs on a Windows machine, hitting the same error in the
> tests as mentioned by Robert. Additionally, I had the following errors:
>
> Failed tests:
>
The version range may not work for 3.5.0-alpha-1 is all
On 24 February 2017 at 19:33, Christian Schulte wrote:
> Am 02/24/17 um 18:34 schrieb Robert Scholte:
> > When running the maven-its, I get this failing test. I think the cause is
> > an invalid version range, right?
>
>
I also ran the ITs on a Windows machine, hitting the same error in the
tests as mentioned by Robert. Additionally, I had the following errors:
Failed tests:
MavenITmng2199ParentVersionRangeTest>AbstractMavenIntegrationTestCase.runTest:244
Expected failure when with Maven version 3.5.0-alpha-1
Am 02/24/17 um 18:34 schrieb Robert Scholte:
> When running the maven-its, I get this failing test. I think the cause is
> an invalid version range, right?
Are you really running the IT master branch? There have been no commits
to maven master without a successful IT run before. I wonder how
When running the maven-its, I get this failing test. I think the cause is
an invalid version range, right?
Robert
Tests in error:
MavenITmng5805PkgTypeMojoConfiguration>AbstractMavenIntegrationTestCase.runTest:222->testPkgTypeMojoConfiguration:27
╗ Verification
On Thu, 23 Feb 2017
Hi,
On 24/02/17 15:59, Petr Široký wrote:
Hello,
I've tested the 3.5.0-alpha-1 with several quite large projects (hundreds
of modules in total) and everything looks good.
+1 non-binding (hopefully I understood correctly I can do that)
Petr
Thanks...appreciate your feedback...
And of
Hi,
highly appreciated to have some feedback from the community...
Thanks for that.
Karl Heinz Marbaise
On 24/02/17 08:58, Grzegorz Grzybek wrote:
Hello
I'm not sure if I can give any vote (even non-binding +1), but I
tested several large OSGi projects using 3.5.0-alpha-1 without
problems.
+1
I've been testing today with our projects and it all looks good.
2017-02-24 16:59 GMT+02:00 Petr Široký :
> Hello,
>
> I've tested the 3.5.0-alpha-1 with several quite large projects (hundreds
> of modules in total) and everything looks good.
>
> +1 non-binding
Hello,
I've tested the 3.5.0-alpha-1 with several quite large projects (hundreds
of modules in total) and everything looks good.
+1 non-binding (hopefully I understood correctly I can do that)
Petr
On Fri, Feb 24, 2017 at 11:13 AM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
https://issues.apache.org/jira/browse/MNG-6178 created
On 23 February 2017 at 21:56, Christian Schulte wrote:
> Can we have this patch included? I wanted to commit this to master
> yesterday when the build job succeeded. This is just pending the Jenkins
> update to get the job
While we have a legal requirement to get at least 3x+1 votes from PMC
members (which are know as binding votes), all votes are welcome.
The more reports we have from the community, the better!
On Fri 24 Feb 2017 at 07:58, Grzegorz Grzybek wrote:
> Hello
>
> I'm not sure
Hello
I'm not sure if I can give any vote (even non-binding +1), but I
tested several large OSGi projects using 3.5.0-alpha-1 without
problems.
regards
Grzegorz Grzybek
2017-02-23 23:44 GMT+01:00 Stephen Connolly :
> This is only an alpha, I'm not calling a halt
1 - 100 of 106 matches
Mail list logo