Hi Marc,

I'll plead ignorance on this. I'd like to have some feedback from the maven incubator experts here. I'm copying the maven user list in case they can shed some light.

Perhaps we need a new maven-incubator-release plugin that allows you to deploy to a ~mikedd repository that has no official standing and then copy the artifacts to the real repository after it's been approved by the incubator.

It's hard for me to imagine, though, that the maven release plugin doesn't accommodate the need to deploy all of the release artifacts to a staging location for testing by the community, prior to making it generally available on the mirrors.

It might be good for some of us openjpa folks to thoroughly examine the maven release plugin to see how they intended this to work...

Craig

On Apr 8, 2007, at 5:12 PM, Marc Prud'hommeaux wrote:

Craig-

I think that will generally work, but there is the issue of the "maven-metadata.xml" file in the parent directory (e.g., http:// people.apache.org/repo/m2-incubating-repository/org/apache/openjpa/ openjpa-project/maven-metadata.xml) that lists all of the releases. If you release to a different location and then manually move over the release subdirectories, the parent maven-metadata.xml won't automatically be updated. You could manually add the line to those files, but them the md5 and sha1 checksums would be wrong.

I don't actually know who or what uses the maven-metadata.xml file, but that was one of the things that gave me pause during the last release about deploying to one location and then manually moving the approved artifacts over to the official repository.





On Apr 8, 2007, at 5:03 PM, Craig L Russell wrote:

Other projects use the people.apache.org/~mikedd/xxx as the staging repository while working through the release issues and votes.

I think you just need to tell maven where your repository is. Once the vote to release passes the incubator IPMC, you can just move the release artifacts from the staging repo to the real repo with a simple unix move command.

Craig

On Apr 8, 2007, at 4:42 PM, Marc Prud'hommeaux wrote:

Craig-

Yeah, we ran into this issue with the last release, where we kept re-building release candidates that were all labeled "0.9.6- incubating" and were getting re-deployed to the official repository.

It would be easy enough to deploy to an alternate repository for release approval (I think you could just use the "- DaltDeploymentRepository" flag), but then it would be a bit of a pain to move all the artifacts over once the release is approved. However, I agree that we need to fix the current problem of candidates being deployed to the official location, and that's probably the only way to do it.

Also, FTR, we can sign the release by specifying the "sign- release" profile that manually runs GPG on the files (although we should move this to the official "maven-gpg-plugin" at some point).




On Apr 8, 2007, at 3:07 PM, Craig L Russell wrote:

Hi Mike,

Something is wrong with the openjpa release process. Artifacts should not be uploaded to the repository until they are voted out of the project. Until they are ready, you should stage the proposed release, sign it, and after you're sure it's ready to go, call for a review on the dev list, and then call for a vote on the incubator general alias and dev list.

You only need one checksum but need a gpg ascii armored signature. So you need the artifact and the artifact.asc (gpg signature) and artifact.md5 to be in the staging area. The sha1 is not needed.

This should be part of the release process that's documented...

Craig

Begin forwarded message:

From: Carlos Sanchez <[EMAIL PROTECTED]>
Date: April 8, 2007 12:40:01 PM PDT
To: [EMAIL PROTECTED]
Cc: repository@apache.org
Subject: Re: [repo] /www/people.apache.org/repo/m2-incubating- repository/
Reply-To: repository@apache.org

please add PGP signatures, it's apache policy to sign all releases

take a look at the latest maven parent pom on how to use the gpg
plugin for automatic signing

http://repo1.maven.org/maven2/org/apache/maven/maven-parent/5/ maven-parent-5.pom


On 8 Apr 2007 08:17:08 -0000, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Repository changed
==================

Repository: /www/people.apache.org/repo/m2-incubating-repository/

Added
-----
[mikedd] org/apache/openjpa/openjpa/0.9.7-incubating
[mikedd] org/apache/openjpa/openjpa/0.9.7-incubating/ openjpa-0.9.7-incubating.pom [mikedd] org/apache/openjpa/openjpa/0.9.7-incubating/ openjpa-0.9.7-incubating.pom.md5 [mikedd] org/apache/openjpa/openjpa/0.9.7-incubating/ openjpa-0.9.7-incubating.pom.sha1 [mikedd] org/apache/openjpa/openjpa/0.9.7-incubating/ openjpa-0.9.7-incubating-site.xml [mikedd] org/apache/openjpa/openjpa/0.9.7-incubating/ openjpa-0.9.7-incubating-site.xml.md5 [mikedd] org/apache/openjpa/openjpa/0.9.7-incubating/ openjpa-0.9.7-incubating-site.xml.sha1
[mikedd] org/apache/openjpa/openjpa-lib/0.9.7-incubating
[mikedd] org/apache/openjpa/openjpa-lib/0.9.7-incubating/ openjpa-lib-0.9.7-incubating.jar [mikedd] org/apache/openjpa/openjpa-lib/0.9.7-incubating/ openjpa-lib-0.9.7-incubating.jar.md5 [mikedd] org/apache/openjpa/openjpa-lib/0.9.7-incubating/ openjpa-lib-0.9.7-incubating.jar.sha1 [mikedd] org/apache/openjpa/openjpa-lib/0.9.7-incubating/ openjpa-lib-0.9.7-incubating.pom [mikedd] org/apache/openjpa/openjpa-lib/0.9.7-incubating/ openjpa-lib-0.9.7-incubating.pom.md5 [mikedd] org/apache/openjpa/openjpa-lib/0.9.7-incubating/ openjpa-lib-0.9.7-incubating.pom.sha1
[mikedd] org/apache/openjpa/openjpa-kernel/0.9.7-incubating
[mikedd] org/apache/openjpa/openjpa-kernel/0.9.7-incubating/ openjpa-kernel-0.9.7-incubating.jar [mikedd] org/apache/openjpa/openjpa-kernel/0.9.7-incubating/ openjpa-kernel-0.9.7-incubating.jar.md5 [mikedd] org/apache/openjpa/openjpa-kernel/0.9.7-incubating/ openjpa-kernel-0.9.7-incubating.jar.sha1 [mikedd] org/apache/openjpa/openjpa-kernel/0.9.7-incubating/ openjpa-kernel-0.9.7-incubating.pom [mikedd] org/apache/openjpa/openjpa-kernel/0.9.7-incubating/ openjpa-kernel-0.9.7-incubating.pom.md5 [mikedd] org/apache/openjpa/openjpa-kernel/0.9.7-incubating/ openjpa-kernel-0.9.7-incubating.pom.sha1
[mikedd] org/apache/openjpa/openjpa-jdbc/0.9.7-incubating
[mikedd] org/apache/openjpa/openjpa-jdbc/0.9.7-incubating/ openjpa-jdbc-0.9.7-incubating.jar [mikedd] org/apache/openjpa/openjpa-jdbc/0.9.7-incubating/ openjpa-jdbc-0.9.7-incubating.jar.md5 [mikedd] org/apache/openjpa/openjpa-jdbc/0.9.7-incubating/ openjpa-jdbc-0.9.7-incubating.jar.sha1 [mikedd] org/apache/openjpa/openjpa-jdbc/0.9.7-incubating/ openjpa-jdbc-0.9.7-incubating.pom [mikedd] org/apache/openjpa/openjpa-jdbc/0.9.7-incubating/ openjpa-jdbc-0.9.7-incubating.pom.md5 [mikedd] org/apache/openjpa/openjpa-jdbc/0.9.7-incubating/ openjpa-jdbc-0.9.7-incubating.pom.sha1
[mikedd] org/apache/openjpa/openjpa-xmlstore/0.9.7-incubating
[mikedd] org/apache/openjpa/openjpa-xmlstore/0.9.7-incubating/ openjpa-xmlstore-0.9.7-incubating.jar [mikedd] org/apache/openjpa/openjpa-xmlstore/0.9.7-incubating/ openjpa-xmlstore-0.9.7-incubating.jar.md5 [mikedd] org/apache/openjpa/openjpa-xmlstore/0.9.7-incubating/ openjpa-xmlstore-0.9.7-incubating.jar.sha1 [mikedd] org/apache/openjpa/openjpa-xmlstore/0.9.7-incubating/ openjpa-xmlstore-0.9.7-incubating.pom [mikedd] org/apache/openjpa/openjpa-xmlstore/0.9.7-incubating/ openjpa-xmlstore-0.9.7-incubating.pom.md5 [mikedd] org/apache/openjpa/openjpa-xmlstore/0.9.7-incubating/ openjpa-xmlstore-0.9.7-incubating.pom.sha1
[mikedd] org/apache/openjpa/openjpa-jdbc-5/0.9.7-incubating
[mikedd] org/apache/openjpa/openjpa-jdbc-5/0.9.7-incubating/ openjpa-jdbc-5-0.9.7-incubating.jar [mikedd] org/apache/openjpa/openjpa-jdbc-5/0.9.7-incubating/ openjpa-jdbc-5-0.9.7-incubating.jar.md5 [mikedd] org/apache/openjpa/openjpa-jdbc-5/0.9.7-incubating/ openjpa-jdbc-5-0.9.7-incubating.jar.sha1 [mikedd] org/apache/openjpa/openjpa-jdbc-5/0.9.7-incubating/ openjpa-jdbc-5-0.9.7-incubating.pom [mikedd] org/apache/openjpa/openjpa-jdbc-5/0.9.7-incubating/ openjpa-jdbc-5-0.9.7-incubating.pom.md5 [mikedd] org/apache/openjpa/openjpa-jdbc-5/0.9.7-incubating/ openjpa-jdbc-5-0.9.7-incubating.pom.sha1
[mikedd] org/apache/openjpa/openjpa-kernel-5/0.9.7-incubating
[mikedd] org/apache/openjpa/openjpa-kernel-5/0.9.7-incubating/ openjpa-kernel-5-0.9.7-incubating.jar [mikedd] org/apache/openjpa/openjpa-kernel-5/0.9.7-incubating/ openjpa-kernel-5-0.9.7-incubating.jar.md5 [mikedd] org/apache/openjpa/openjpa-kernel-5/0.9.7-incubating/ openjpa-kernel-5-0.9.7-incubating.jar.sha1 [mikedd] org/apache/openjpa/openjpa-kernel-5/0.9.7-incubating/ openjpa-kernel-5-0.9.7-incubating.pom [mikedd] org/apache/openjpa/openjpa-kernel-5/0.9.7-incubating/ openjpa-kernel-5-0.9.7-incubating.pom.md5 [mikedd] org/apache/openjpa/openjpa-kernel-5/0.9.7-incubating/ openjpa-kernel-5-0.9.7-incubating.pom.sha1
[mikedd] org/apache/openjpa/openjpa-persistence/0.9.7-incubating
[mikedd] org/apache/openjpa/openjpa-persistence/0.9.7- incubating/openjpa-persistence-0.9.7-incubating.jar [mikedd] org/apache/openjpa/openjpa-persistence/0.9.7- incubating/openjpa-persistence-0.9.7-incubating.jar.md5 [mikedd] org/apache/openjpa/openjpa-persistence/0.9.7- incubating/openjpa-persistence-0.9.7-incubating.jar.sha1 [mikedd] org/apache/openjpa/openjpa-persistence/0.9.7- incubating/openjpa-persistence-0.9.7-incubating.pom [mikedd] org/apache/openjpa/openjpa-persistence/0.9.7- incubating/openjpa-persistence-0.9.7-incubating.pom.md5 [mikedd] org/apache/openjpa/openjpa-persistence/0.9.7- incubating/openjpa-persistence-0.9.7-incubating.pom.sha1

Removed
-------



--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                            -- The Princess Bride

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/ products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!



Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/ jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!



Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to