Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-18 Thread robert burrell donkin
(bit late on this thread) FWIW i'd say that the right approach would be to start by supporting BouncyCastles. i've noticed that most folks just want a simple set of instructions (something which is pretty difficult when dealing with code signing). it'd probably pay to go for a single, simple

Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-07 Thread Mark R. Diggory
I've been lurking on this discussion. +1 PGP Signing files needs to be just like the current md5 signing that maven supplies on artifacts. You should be able to supply signing Keys and get artifacts signed. I initially was working on libraries to do this in Ant/Maven using BouncyCastle. But

Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-07 Thread Martin Cooper
On Fri, 07 Jan 2005 12:47:06 -0500, Mark R. Diggory [EMAIL PROTECTED] wrote: I've been lurking on this discussion. +1 PGP Signing files needs to be just like the current md5 signing that maven supplies on artifacts. You should be able to supply signing Keys and get artifacts signed. The

Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-07 Thread Mark R. Diggory
Thats one of the major reasons I stalled in development of it. It's very platform/application specific in that case. Either force the Ant task to be using only BouncyCastle and have everyone import their keys into BouncyCastles config, or allow users to configure which application was doing

Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-06 Thread Phil Steitz
Brett Porter wrote: phil's a bit shy (honest ;) but he's chomping at the bit to create a release guide for mavenized ASF products based on the jakarta commons one. originally, he was talking about improving the JC release manager stuff. however, it sounds to me like it might be better hosted

RE: [Jakarta Commons Wiki] New: SigningReleases

2005-01-06 Thread Tim O'Brien
-Original Message- From: Phil Steitz [mailto:[EMAIL PROTECTED] 2) A real maven expert (Brett ;) could probably figure out how to automate almost everything in a way that could be reused across all maven-built projects. Including the signing, hashing and verification in the

Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-06 Thread Rory Winston
+1 Tim O'Brien wrote: -Original Message- From: Phil Steitz [mailto:[EMAIL PROTECTED] 2) A real maven expert (Brett ;) could probably figure out how to automate almost everything in a way that could be reused across all maven-built projects. Including the signing, hashing

Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-06 Thread robert burrell donkin
AIUI there some work underway on this over in mavenland. hopefully brett will jump now with a progress report and tasks which are still needed volunteers... - robert On 6 Jan 2005, at 20:53, Rory Winston wrote: +1 Tim O'Brien wrote: -Original Message- From: Phil Steitz [mailto:[EMAIL

Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-06 Thread Brett Porter
Hi Robert, As you wish :) A more complete release plugin is really still on the TODO list. What is there now is doing the job enough to get by, so I'd really like the next work to be done right, from the ground up. If you've got requirements, I'd be happy to keep them in mind. There's been an

Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-05 Thread robert burrell donkin
(i've been talking with the infrastructure crew recently and) the right place long term for this information is in the dev section of the foundation site. we're moving some stuff up from the jakarta site and there are plans to assemble some release management information. if you've got the

Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-05 Thread Brett Porter
Hey robert, Count me in. I've been wanting to push on this for a while, but now that I have rights to edit /dev/ I have no excuse :) Cheers, Brett Quoting robert burrell donkin [EMAIL PROTECTED]: (i've been talking with the infrastructure crew recently and) the right place long term for

Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-05 Thread robert burrell donkin
On 5 Jan 2005, at 22:35, Brett Porter wrote: Hey robert, Count me in. I've been wanting to push on this for a while, but now that I have rights to edit /dev/ I have no excuse :) top smart :) phil's a bit shy (honest ;) but he's chomping at the bit to create a release guide for mavenized ASF

Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-05 Thread Brett Porter
phil's a bit shy (honest ;) but he's chomping at the bit to create a release guide for mavenized ASF products based on the jakarta commons one. originally, he was talking about improving the JC release manager stuff. however, it sounds to me like it might be better hosted over in

[Jakarta Commons Wiki] New: SigningReleases

2005-01-04 Thread commons-dev
Date: 2005-01-04T15:38:37 Editor: DirkVerbeeck Wiki: Jakarta Commons Wiki Page: SigningReleases URL: http://wiki.apache.org/jakarta-commons/SigningReleases Copy from the old wiki http://wiki.apache.org/old/SigningReleases?action=raw New Page: = Signing a release version =

Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-04 Thread Martin Cooper
There's another copy of this page in the incubator wiki. It seems to me that it would be better to have one copy in the ASF-wide wiki, where all projects can refer to it, since otherwise, multiple copies are going to be out of sync. -- Martin Cooper On Tue, 04 Jan 2005 23:38:38 -,

Re: [Jakarta Commons Wiki] New: SigningReleases

2005-01-04 Thread Dirk Verbeeck
Agreed, this wiki page is referred from the commons release page: http://jakarta.apache.org/commons/releases/release.html This page needs an update once we switch to svn maybe then we can make them more generic. -- Dirk Martin Cooper wrote: There's another copy of this page in the incubator