Hi Michael,
It looks like the right people are involved in fixing this.
Please do document the results of this discussion in the "How To Make
An OpenJPA Release".
Craig
On Apr 8, 2007, at 6:56 PM, Michael Dick wrote:
Actually it looks like the link David sent us has the information. The
r
On Monday 09 April 2007 08:12, Marc Prud'hommeaux wrote:
> 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)
Craig,
The procedure you describe is exactly how all Maven plugin releases (and
Maven 2.0.5 and 2.0.6) now go through.
The release plugin is configured to activate a "release" profile that
does a few things:
1) Turns on the remote-resources plugin which injects the license/notice
files in
Actually it looks like the link David sent us has the information. The
release plugin provides a mechanism to deploy to a staging area.
The catch is that migrating from the staging area to a production
repository. A quick excerpt follows:
"Once the release is deemed fit for public consumption it
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
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
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 t
Thanks Carlos and Marc, I've removed the files now.
On 4/8/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:
Michael-
I'd just do:
rm -rvi /www/people.apache.org/repo/m2-incubating-repository/org/
apache/openjpa/*/0.9.7-incubating/
I had to do this a bunch of times with the 0.9.6-incubating
Michael-
I'd just do:
rm -rvi /www/people.apache.org/repo/m2-incubating-repository/org/
apache/openjpa/*/0.9.7-incubating/
I had to do this a bunch of times with the 0.9.6-incubating release,
and maven seemed to recover gracefully from a version listed in maven-
metadata.xml being deleted
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 th
there's no automatic way to do it. You may leave the xml files as is
until the release is approved.
On 4/8/07, Michael Dick <[EMAIL PROTECTED]> wrote:
What is the best way to recover from erroneously published binaries?
Per Craig's email I should have waited to deploy until after the release
pa
What is the best way to recover from erroneously published binaries?
Per Craig's email I should have waited to deploy until after the release
passed a vote on the open-jpa-dev mailing list. I took a look at the maven
repository and I noticed that some of the xml files were updated with the
new ve
Hi Craig,
I thought that deploying them before the vote was a little odd too. I was
planning on calling for the vote tomorrow (after Easter weekend). In the
mean time, I'll go ahead and remove the artifacts from people.apache.org.
On 4/8/07, Craig L Russell <[EMAIL PROTECTED]> wrote:
Hi Mike,
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
I see that I've already commented on this thread without replying. ;-) To
continue, a Mentor is a member of the Incubator PMC "who will guide the
Candidate through the Incubation Process." Key point being an Incubator PMC
Member. If I recall correctly, the reason for the "at least one" clause w
On 4/7/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Hi Robert, Thanks for taking the time to look at our precious :).
Answers inline.
On 4/7/07, robert burrell donkin <[EMAIL PROTECTED]> wrote:
> On 3/30/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> minor issues
> ---
>
16 matches
Mail list logo
