scm 1.3 release
Hi, I'd like to release scm 1.3. No objections or work in progress in scm ? Thanks, -- Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: scm 1.3 release
Oliver, I have several bugfixes for maven-cvs-provider. How soon do you want to release 1.3? Andrei Solntsev, Software Developer, HireRight Estonia -Original Message- From: Olivier Lamy [mailto:ol...@apache.org] Sent: Saturday, November 28, 2009 12:57 PM To: Maven Developers List Subject: scm 1.3 release Hi, I'd like to release scm 1.3. No objections or work in progress in scm ? Thanks, -- Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: scm 1.3 release
As the last release was 28-Mar-2009, I don't wan't to delay this too much. 2/3 weeks. Is it enough for you to provide your patches ? Thanks, -- Olivier 2009/11/28 Andrei Solntsev asolnt...@hireright.ee: Oliver, I have several bugfixes for maven-cvs-provider. How soon do you want to release 1.3? Andrei Solntsev, Software Developer, HireRight Estonia -Original Message- From: Olivier Lamy [mailto:ol...@apache.org] Sent: Saturday, November 28, 2009 12:57 PM To: Maven Developers List Subject: scm 1.3 release Hi, I'd like to release scm 1.3. No objections or work in progress in scm ? Thanks, -- Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: voting was: [VOTE] Release Apache Maven 3.0-alpha-5
On Fri, Nov 27, 2009 at 3:42 PM, Brett Porter br...@apache.org wrote: Brian, I'm not sure if you were replying to me or others, but you quoted me and snipped my actual point: I'm fine with either more or less frequent releases... I'm not fine with circumventing review or pushing releases outside the ASF. I agree with everything you said below. I was saying we need to keep the 72h voting window because there are good reasons for it. It's not that everyone has to review - just that everyone has the opportunity to. We're in agreement, except the license allows 3rd parties to produce forks or binaries so I don't think we need to be concerned about that possibility. It's not clear to me what the implications for naming are but that's an entirely separate bike shed. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Release plugin documentation request
I find that the release plugin docs don't give me an adequate idea of what to expect to happen in svn when I run release:prepare release:rollback release:perform release:branch After some experimentation I think I know what happens for some of these: release:prepare makes 3 svn commits - update current project to release version - create tag (from what? I have no idea) - update current project to next development version release:rollback, in an indeterminate number of commits, undoes anything committed since release:prepare was run for the first time in this release attempt. In particular if you tried to commit build fixes that only became evident during release:prepare, they will get undone. release:perform makes no svn changes release:branch I have no idea about. I suspect it would take about 15 minutes for one of the authors to update the docs with some accurate info along these lines and I doubt I would be the only one appreciating the effort. thanks david jencks - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Release plugin documentation request
Hello David, Maybe you can find answers to at least some of questions in following articles: - http://www.vineetmanohar.com/2009/10/23/how-to-automate-project-versioning-and-release-with-maven/ - http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin Regards, Stevo. On Sat, Nov 28, 2009 at 11:20 PM, David Jencks david_jen...@yahoo.comwrote: I find that the release plugin docs don't give me an adequate idea of what to expect to happen in svn when I run release:prepare release:rollback release:perform release:branch After some experimentation I think I know what happens for some of these: release:prepare makes 3 svn commits - update current project to release version - create tag (from what? I have no idea) - update current project to next development version release:rollback, in an indeterminate number of commits, undoes anything committed since release:prepare was run for the first time in this release attempt. In particular if you tried to commit build fixes that only became evident during release:prepare, they will get undone. release:perform makes no svn changes release:branch I have no idea about. I suspect it would take about 15 minutes for one of the authors to update the docs with some accurate info along these lines and I doubt I would be the only one appreciating the effort. thanks david jencks - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Release plugin documentation request
Hi Stevo, Thanks but I think the existing release plugin documentation covers everything in those articles quite well. Neither one tells me what to expect to happen in svn when I run one of the goals. I guess -DdryRun=true is supposed to print the svn commands to be used on the console but they are in my experience very hard to find and I don't think this is applicable to anything but release:prepare. I'd also like to request that the meaning of release:clean be explained what exactly is changed? thanks david jencks On Nov 28, 2009, at 2:28 PM, Stevo Slavić wrote: Hello David, Maybe you can find answers to at least some of questions in following articles: - http://www.vineetmanohar.com/2009/10/23/how-to-automate-project-versioning-and-release-with-maven/ - http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin Regards, Stevo. On Sat, Nov 28, 2009 at 11:20 PM, David Jencks david_jen...@yahoo.comwrote: I find that the release plugin docs don't give me an adequate idea of what to expect to happen in svn when I run release:prepare release:rollback release:perform release:branch After some experimentation I think I know what happens for some of these: release:prepare makes 3 svn commits - update current project to release version - create tag (from what? I have no idea) - update current project to next development version release:rollback, in an indeterminate number of commits, undoes anything committed since release:prepare was run for the first time in this release attempt. In particular if you tried to commit build fixes that only became evident during release:prepare, they will get undone. release:perform makes no svn changes release:branch I have no idea about. I suspect it would take about 15 minutes for one of the authors to update the docs with some accurate info along these lines and I doubt I would be the only one appreciating the effort. thanks david jencks - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Does maven provide any support for re-signing artifacts with longer keys?
Apache has recently requested that all apache releases be signed with 4096 bit keys and SHA512, see http://www.apache.org/dev/openpgp.html I've released some artifacts using maven signed with an older 1024 bit key and most likely SHA1. Is there any maven support for re-signing these older artifacts with a new longer key? If not, does anyone have any advice for a non-maven way to do it? thanks david jencks
Re: Release plugin documentation request
Hi, inline you will find some added comments. 2009/11/28 David Jencks david_jen...@yahoo.com: I find that the release plugin docs don't give me an adequate idea of what to expect to happen in svn when I run release:prepare release:rollback release:perform release:branch After some experimentation I think I know what happens for some of these: release:prepare makes 3 svn commits - update current project to release version commit updated pom(s) - create tag (from what? I have no idea) startting with 2.0-beta-9 and the parameter remoteTagging the copy (at least for svn) is done remotely (svn cp http:// http:// ) using the revision from the previous commit. - update current project to next development version release:rollback, in an indeterminate number of commits, undoes anything committed since release:prepare was run for the first time in this release attempt. In particular if you tried to commit build fixes that only became evident during release:prepare, they will get undone. release:perform makes no svn changes release:branch I have no idea about. I suspect it would take about 15 minutes for one of the authors to update the docs with some accurate info along these lines and I doubt I would be the only one appreciating the effort. thanks david jencks - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: scm 1.3 release
Hi, Earlier this year I rewrote the accurev provider. http://jira.codehaus.org/browse/SCM-445 and would be keen to see that included. Original threads here. http://www.mail-archive.com/scm-...@maven.apache.org/msg01231.html Grant. On Sat, 28 Nov 2009 11:57:16 +0100, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release scm 1.3. No objections or work in progress in scm ? Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Does gpg plugin work properly with gpg 2.0.12, the use of which is specified by apache?
Not sure what is happening here, but I was able to use a new key (generated with gpg2) to sign a release recently using gpg. For me, gpg is 1.4.9 and gpg2 is 2.0.12 (different command line arguments) On 29/11/2009, at 9:41 AM, David Jencks wrote: Recently I followed the apache advice to update my code signing key to 4096 bits, see http://www.apache.org/dev/openpgp.html As part of that effort I installed MacGPG2-2.0.12 as the most likely version of gpg 2.0.12 for a mac. Although documentation seems a bit sparse I think I started the gpg agent as well. Running a release I see a message at every signing opportunity gpg: WARNING: --no-use-agent is an obsolete option - it has no effect You need a passphrase to unlock the secret key for user: David Jencks (CODE SIGNING KEY) djen...@apache.org 4096-bit RSA key, ID A2F9E313, created 2009-11-25 and every hour or so (??) a dialog box pops up for me to supply the passphrase (it was a long build). This never happened before I updated gpg, the passphrase in my settings.xml was used. We are using the apache 6 parent pom which specifies the 1.0-alpha-4 version of this plugin. Anyone have an idea what is going on? thanks david jencks - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
