[GitHub] maven-scm pull request: SCM-706 finer-grained handling of file ren...

Github user indrgun commented on the pull request: https://github.com/apache/maven-scm/pull/31#issuecomment-152661620 When can this PR be approved and merged? We have migrated from SVN to Git/Stash but we can't use release-with-pom anymore and the team is not happy. --- If your proj

Re: [VOTE] Maven 3.3.8

+1 On Fri, Oct 30, 2015 at 6:38 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> 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 review there ;-) > > -Stephen > > On 30 October 2015 at 17:01, Jason

Re: [VOTE] Maven 3.3.8

+1 beer, again On Fri, Oct 30, 2015 at 7:38 PM Igor Fedorenko wrote: > +1 > > -- > Regards, > Igor > > On Fri, Oct 30, 2015, at 12:58 PM, Jason van Zyl wrote: > > Hi, > > > > Time to release Maven 3.3.8! > > > > Here is a link to the issues resolved: > > > https://issues.apache.org/jira/secure/R

Re: [VOTE] Maven 3.3.8

+1 -- Regards, Igor On Fri, Oct 30, 2015, at 12:58 PM, Jason van Zyl wrote: > Hi, > > Time to release Maven 3.3.8! > > Here is a link to the issues resolved: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12333074 > > Staging repo: > https://repository.apa

Re: [VOTE] Maven 3.3.8

+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 review there ;-) -Stephen On 30 October 2015 at 17:01, Jason van Zyl wrote: > +1 > > Analyzing release validity... > > stagingUrl: https://repository.apache.org/content/

Re: [VOTE] Maven 3.3.8

+1 Analyzing release validity... stagingUrl: https://repository.apache.org/content/repositories/maven-1230 groupId: org.apache.maven artifactId: apache-maven version: 3.3.8 Source ZIP url exists. https://repository.apache.org/content/repositories/maven-1230/org/apache/maven/apache-maven/3.3.8/ap

[VOTE] Maven 3.3.8

Hi, Time to release Maven 3.3.8! Here is a link to the issues resolved: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12333074 Staging repo: https://repository.apache.org/content/repositories/maven-1230/ The distributable binaries and sources for testing can

Re: [VOTE] Maven 3.3.7

This vote is cancelled. > On Oct 30, 2015, at 9:15 AM, Stephen Connolly > wrote: > > Well I cannot build with 3.3.3 because it picks the wrong parent > projects from the reactor so I can only compare with a 3.3.6-SNAPSHOT > that I have been running for the past 4+ months while intermitently > p

Re: Maven Release Version Policy

Robert, Before the introduction of the plugable policy the release plugin would transform a version number like 1.8.0-1.7.1.0-alpha-1 to 1.8.0-1.7.1.0-alpha-2-SNAPSHOT whereas since sometime after m-r-p 2.2 it now does 1.8.0-1.7.1.0-alpha-1 to 1.8.0-2.7.1.0-alpha-1-SNAPSHOT which is a major pain i

Re: [VOTE] Maven 3.3.7

Well I cannot build with 3.3.3 because it picks the wrong parent projects from the reactor so I can only compare with a 3.3.6-SNAPSHOT that I have been running for the past 4+ months while intermitently pestering Jason to cut a release ;-) On 30 October 2015 at 14:09, Igor Fedorenko wrote: > Yes,

Re: Maven Release Version Policy

Here are some thoughts I had on semver: http://javaadventure.blogspot.ie/2014/09/version-numbers.html In any case this code is just to provide a strategy that people can choose to turn on. I am not saying that this strategy should be the default, only that it should be one of the *defaultS* that

Re: Maven Release Version Policy

Stephen, you are saying that the implementation of the default version policy has changed? That would be a bug. CloudBees implementation looks natural,although Aether is aware of more classifiers , not just alpha and beta. Robert Verzonden vanaf Samsung Mobile. Oorspronkelijk bericht

Early Access builds for JDK 8u72 b05 , JDK 9 b88 and JDK 9 with Project Jigsaw build b86 are available on java.net

Hi Robert & Kristian, Early Access build for JDK 8u72 b05 is available on java.net, summary of changes are listed here. Early Access build for JDK 9 b8

Re: Maven Release Version Policy

I would prefer to move toward standard semver and identify where we’re not strictly adhering. Is it strict semver? > On Oct 30, 2015, at 5:16 AM, Stephen Connolly > wrote: > > Hey, so... > > Do we want to accept this implementation I knocked together: > https://github.com/CloudBees-community/

Re: [VOTE] Maven 3.3.7

Yes, that commit fixed the problem and I am able to run our entire build successfully with the current master. Thank you for looking into this, Jason. Very unscientific, but I do see small-ish performance degradation compared to 3.3.3, the build too 25m50s with 3.3.3 and 26m35s with the current ma

Maven Release Version Policy

Hey, so... Do we want to accept this implementation I knocked together: https://github.com/CloudBees-community/cloudbees-maven-release-version-policy If not I'm fine leaving it where it is... but I can get it donated to the ASF if there is interest -Stephen -

[GitHub] maven-plugins pull request: MCHANGES-363: Add support for opened i...

GitHub user dadoonet opened a pull request: https://github.com/apache/maven-plugins/pull/67 MCHANGES-363: Add support for opened issues in announcement Mojo Generate announcement file including current opened issues. Really handy if you want to test your announcement chain withou

Re: [VOTE] Maven 3.3.7

I will respin it. It only takes me a few minutes now. > On Oct 30, 2015, at 12:24 AM, Hervé BOUTEMY wrote: > > grr, seems I'm the culprit of this regression :( > I saw the commit before the report on the ML... > > this doesn't change the question of tracking: do we cancel the 3.3.7 vote and >

Re: maven git commit: Fix for urls being empty in the POM and causing an out of bounds exception

I don’t think it’s necessary as Igor found it and hopefully I fixed it before any user will see it. But we can find the original JIRA issue with the commit and then add this commit there as the fix. Probably easiest to track it in one place from the source of the work. The two issues that I can

Re: [VOTE] Maven 3.3.7

grr, seems I'm the culprit of this regression :( I saw the commit before the report on the ML... this doesn't change the question of tracking: do we cancel the 3.3.7 vote and respin 3.3.8? or publish 3.3.7 with this known issue? Regards, Hervé Le jeudi 29 octobre 2015 20:21:45 Igor Fedorenko a

Re: maven git commit: Fix for urls being empty in the POM and causing an out of bounds exception

no Jira issue? this won't help track Maven core evolution, since I suppose it's a user visible failure can you please open a Jira issue, with a little stacktrace to find the issue when searching the web? And I don't know if we can rewrite the comment to point to this issue we need to continue