Amazing flute section ! ROFL :)
K
2015-11-02 23:46 GMT+01:00 Jason van Zyl :
> One more time
>
> https://www.youtube.com/watch?v=ry4ngf766N0
>
> > On Nov 2, 2015, at 7:26 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
> >
> > Well I was asked to remove the quick and dirty chec
My PR for “Adds version range result filter behaviour”
(https://github.com/apache/maven/pull/70) is ready for merging and needs a
willing committer to merge into master.
Please take a look and leave a comment if I could support the merging somehow.
mit freundlichen Grüßen
Uwe Barthel
--
bart..
> ok, then what could be done is only a check afterwards that the version
> chosen
> by the user is consistent with measures on code evolutions
So we are back on version policy I think.
Only check and stop the release based on the policy.
> another idea: perhaps we should have the API propose mu
+1
PMC quorum ok :)
Regards,
Hervé
Le samedi 31 octobre 2015 21:48:28 Karl Heinz Marbaise a écrit :
> Hi,
>
> JIRA Reference:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&ve
> rsion=12328931
>
> Changes since the last release:
> http://svn.apache.org/viewvc/mave
One more time
https://www.youtube.com/watch?v=ry4ngf766N0
> On Nov 2, 2015, at 7:26 AM, Stephen Connolly
> wrote:
>
> Well I was asked to remove the quick and dirty check of "is it a
> version range" which lead to:
>
> https://git1-us-west.apache.org/repos/asf?p=maven.git;a=blobdiff;f=maven-m
Hi,
here is my +1...
here is a need for at least one binding VOTE...
Kind regards
Karl Heinz Marbaise
On 10/31/15 9:48 PM, Karl Heinz Marbaise wrote:
Hi,
JIRA Reference:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12328931
Changes since the last release
+1
On Sat, Oct 31, 2015 at 4:48 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> JIRA Reference:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12328931
>
> Changes since the last release:
> http://svn.apache.org/viewvc/maven/shared/tags/maven-shared-components-22/pom
Well I was asked to remove the quick and dirty check of "is it a
version range" which lead to:
https://git1-us-west.apache.org/repos/asf?p=maven.git;a=blobdiff;f=maven-model-builder/src/main/java/org/apache/maven/model/building/DefaultModelBuilder.java;h=ab00fef6d533c03a8e7bafc714450a663f320518;hp
IIRC, somebody provided a patch to remove this if-statement. Not sure if it was
applied.
Robert
Verzonden vanaf Samsung Mobile.
Oorspronkelijk bericht Van: Stephen Connolly
Datum:02-11-2015 04:18
(GMT-08:00) Aan: Maven Developers List
Onderwerp: Re: [VOTE] Maven 3.3.8
h
https://git1-us-west.apache.org/repos/asf?p=maven.git;a=commit;h=19532849
is the fix
On 2 November 2015 at 12:05, Stephen Connolly
wrote:
> -1 technical
>
> mng5840ParentVersionRanges(ParentRangeRelativePathPointsToWrongVersion)OK
> (5.6 s)
> mng5840ParentVersionRanges(ParentRangeRelativePathPoin
-1 technical
mng5840ParentVersionRanges(ParentRangeRelativePathPointsToWrongVersion)OK
(5.6 s)
mng5840ParentVersionRanges(ParentRangeRelativePathPointsToCorrectVersion)OK
(0.4 s)
mng5840RelativePathReactorMatching(RelativePathPointsToWrongVersion)FAILURE
(0.4 s)
On 2 November 2015 at 11:48, Ste
Hmmm I may have to change my vote, looking like there is a regression
on the MNG-5840 fix from 3.3.6-SNAPSHOT
On 30 October 2015 at 17:38, Stephen Connolly
wrote:
> +1 technical - works on my critical big build
> +1 legal umbrella - on the diff of this since 3.3.7 (thankfully only 1
> commit to r
12 matches
Mail list logo