[VOTE] Release Apache Maven GPG Plugin version 1.5

Hi, We solved 4 issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11431styleName=Htmlversion=17635 There are still a couple of issues left in JIRA:http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11431status=1 Staging repo:

Re: [VOTE] Release Apache Maven GPG Plugin version 1.5

+1 from me On 21 February 2014 14:13, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, We solved 4 issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11431styleName=Htmlversion=17635 There are still a couple of issues left in

[DISCUSS] Adopt a version policy and a support policy to go with it.

For discussion... and tearing into... and Chris shouting out that IBM supports Java 6 for yonks... https://cwiki.apache.org/confluence/display/MAVEN/Version+number+policy I think we need a version policy and the best way to get one is to put a draft together and let people edit it to something

Re: [DISCUSS] Adopt a version policy and a support policy to go with it.

I think this is reasonable. One observation. Maven does not have an API, plugins and projects can access pretty much anything from the core. Add to this three distinct user communities -- (end) users, plugin developers and embedders -- and I think pretty much any change will break somebody. This

Releasing the release plugin

I checked out the trunk and tried a simple 'mvn test', and I'm drowning in test failures. Anyone have a hint? --- Test set: org.apache.maven.shared.release.DefaultReleaseManagerTest

Re: [DISCUSS] Adopt a version policy and a support policy to go with it.

Le 21 févr. 2014 16:39, Igor Fedorenko i...@ifedorenko.com a écrit : I think this is reasonable. One observation. Maven does not have an API, plugins and projects can access pretty much anything from the core. Add to this three distinct user communities -- (end) users, plugin developers and

Re: [VOTE] Release Apache Maven GPG Plugin version 1.5

On Fri, 21 Feb 2014 14:13:14 + Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, +1 works fine to me. thanks, tony. We solved 4 issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11431styleName=Htmlversion=17635 There are still a couple of issues left in

Re: Releasing the release plugin

Hi Benson, is that with Maven 3.2.1? I'm having random test failures with 3.2.1 on some projects. Switching back to 3.1.1, everything's fine. Regards, Patrick. -- View this message in context: http://maven.40175.n5.nabble.com/Releasing-the-release-plugin-tp5785682p5785704.html Sent from

Re: Releasing the release plugin

I see some small difference between 2.4.2 and current trunk which could be part of the cause: - different parent pom - different version of surefire I'll investigate Robert Op Fri, 21 Feb 2014 16:56:06 +0100 schreef Benson Margulies bimargul...@gmail.com: I checked out the trunk and

Re: Releasing the release plugin

I see those errors as well. Also I have found that I cannot build maven-release using Java 5. Have tried on Win 7 and Ubuntu - same problem. After downgrading to maven-compiler-plugin:2.5.1 I was able to get the real error message (3.0 seems to swallow it):

Re: Releasing the release plugin

3.0.5 java 7 On February 21, 2014 1:44:06 PM EST, Patrick Decat pde...@gmail.com wrote: Hi Benson, is that with Maven 3.2.1? I'm having random test failures with 3.2.1 on some projects. Switching back to 3.1.1, everything's fine. Regards, Patrick. -- View this message in context:

Re: Releasing the release plugin

Ok, I found the cause and you're not gonna to like it. put scmVersion 1.9 back to 1.7 and see the magic. Seems like I missed something here, but why? Robert Op Fri, 21 Feb 2014 20:24:39 +0100 schreef Dennis Lundberg denn...@apache.org: I see those errors as well. Also I have found that I

Re: Releasing the release plugin

I just got an it failure email, apparently it has been in the tank for some time. What changed since the person who upgraded scm tested that change? On February 21, 2014 2:44:10 PM EST, Robert Scholte rfscho...@apache.org wrote: Ok, I found the cause and you're not gonna to like it. put

Re: Releasing the release plugin

The CI job on Jenkins actually failed right after the upgrade of SCM to 1.9. See job #226 at https://builds.apache.org/view/M-R/view/Maven/job/maven-release/ On Fri, Feb 21, 2014 at 9:29 PM, Benson Margulies bimargul...@gmail.com wrote: I just got an it failure email, apparently it has been in

Re: [RESULT] [VOTE] Release Maven 3.2.1

I'm spending some time trying to automate the last steps of the release so it's not so tedious for anyone else who tries to do it. Dealing with the site and putting binaries in SVN is not fun. On Feb 20, 2014, at 12:02 PM, Mark Derricutt m...@talios.com wrote: w00t ;-) Congrats on a fairly

A release of maven-checkstyle-plugin is coming shortly

Hi, If anyone wants to add something to the next release of the Checkstyle plugin, now would be a good time to do it, as I intend to make a release next week. If you need more time to squeeze something in, just let me know. -- Dennis Lundberg

Re: Releasing the release plugin

Hi Benson, is that with Maven 3.2.1? I'm having random test failures with 3.2.1 on some projects. Switching back to 3.1.1, everything's fine. Regards, Patrick. -- View this message in context: http://maven.40175.n5.nabble.com/Releasing-the-release-plugin-tp5785682p5785697.html Sent from the

Site plugin

Not sure who looks after the site plugin these days but I can't run the staging part to copy it over to the production site: In the release checkout I ran: mvn -Preporting site site:stage and got: https://gist.github.com/jvanzyl/9148731 I'll continue on with the rest of the work but I will