Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
2010/5/15 Martin Cooper mart...@apache.org:
If it's a published artifact, it needs a release, so yes.
I made the release, but the artifact went to
/www/people.apache.org/builds/struts/6/m2-staging-repository/org/apache/struts/struts-master/6
As I understand, such section must be removed from struts-master.pom
to use new Nexus repo:
repository
idstruts-staging/id
nameApache Struts Staging Repository/name
urlscp://people.apache.org/www/people.apache.org/builds/struts/${project.version}/m2-staging-repository/url
/repository
snapshotRepository
uniqueVersiontrue/uniqueVersion
idapache.snapshots/id
nameApache Development Snapshot Repository/name
urlscp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository/url
/snapshotRepository
I will do the change and make a new release to test the whole process once again
Regards
--
Łukasz
http://www.lenart.org.pl/
Kapituła Javarsovia 2010
http://javarsovia.pl
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
On Tue, May 25, 2010 at 4:47 AM, Lukasz Lenart
lukasz.len...@googlemail.com wrote:
2010/5/15 Martin Cooper mart...@apache.org:
If it's a published artifact, it needs a release, so yes.
I made the release
I did not see a vote...
--
Martin Cooper
, but the artifact went to
/www/people.apache.org/builds/struts/6/m2-staging-repository/org/apache/struts/struts-master/6
As I understand, such section must be removed from struts-master.pom
to use new Nexus repo:
repository
idstruts-staging/id
nameApache Struts Staging Repository/name
urlscp://people.apache.org/www/people.apache.org/builds/struts/${project.version}/m2-staging-repository/url
/repository
snapshotRepository
uniqueVersiontrue/uniqueVersion
idapache.snapshots/id
nameApache Development Snapshot Repository/name
urlscp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository/url
/snapshotRepository
I will do the change and make a new release to test the whole process once
again
Regards
--
Łukasz
http://www.lenart.org.pl/
Kapituła Javarsovia 2010
http://javarsovia.pl
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
2010/5/25 Martin Cooper mart...@apache.org: On Tue, May 25, 2010 at 4:47 AM, Lukasz Lenart lukasz.len...@googlemail.com wrote: 2010/5/15 Martin Cooper mart...@apache.org: If it's a published artifact, it needs a release, so yes. I made the release I did not see a vote... It's is in staging repo but I want to use Nexus for that and waiting for clarification. As I understood I can removed it from the repo and do it again. If not I will call for a Vote. Regards -- Łukasz http://www.lenart.org.pl/ Kapituła Javarsovia 2010 http://javarsovia.pl - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
On Tue, May 25, 2010 at 10:21 AM, Lukasz Lenart lukasz.len...@googlemail.com wrote: It's is in staging repo but I want to use Nexus for that and waiting for clarification. As I understood I can removed it from the repo and do it again. If not I will call for a Vote. You're fine, just sort out how to stage it in the new repo and then call a vote to release the master pom. :) This is good practice learning to stage and promote a single artifact before you try it with the whole thing. -- Wendy - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: svn commit: r947374 - /struts/maven/trunk/build/KEYS
On Mon, May 24, 2010 at 3:04 AM, Lukasz Lenart lukasz.len...@googlemail.com wrote: 2010/5/23 Lukasz Lenart lukasz.len...@googlemail.com: 2010/5/23 Martin Cooper mart...@apache.org: If an existing key has ever been used to sign a release, it should not be removed from the KEYS file. It's still needed to verify those older releases. New keys should just be added without removing anything that was there before. I didn't know, I loose my old keys when my laptop was flooded :P I will merge with the previous version. One more question, I never used that key to sign anything (I tried, but a Vote was cancelled). In such case maybe it's better to clean up the KEYS file? I would say that whether the old key stays out depends on a few things... For one, you mentioned that you've never used that key to sign a release. If you can guarantee that, then I don't see the need to pull it back into the KEYS file (Martin, feel free to disagree, I'd back down pretty easy). The way I would guarantee is to scp all the releases from people.a.o (or wget from a mirror) and loop through them to make sure. Should be trivial, although it might kill your bandwidth ;). If you can't find anything that you've signed with the keys that no longer exist, I'd say leave it (for the sake of simplicity). But, I would also make a backup (I prefer to burn to a CD, then keep them somewhere safe) of your new private key. -Wes -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
On Tue, May 25, 2010 at 10:35 AM, Wendy Smoak wsm...@gmail.com wrote: On Tue, May 25, 2010 at 10:21 AM, Lukasz Lenart lukasz.len...@googlemail.com wrote: It's is in staging repo but I want to use Nexus for that and waiting for clarification. As I understood I can removed it from the repo and do it again. If not I will call for a Vote. You're fine, just sort out how to stage it in the new repo and then call a vote to release the master pom. :) This is good practice learning to stage and promote a single artifact before you try it with the whole thing. -- Wendy +1 This was my motivation for moving to nexus... Martin, sometimes I think we all get the verb release confused. On one hand, there is the logical act of releasing our artifacts to the public. On the other, there is the mechanical act of invoking maven's release plugin. What Lukasz is referring to is the mechanical act of invoking maven's release plugin. It will push the artifact to the nexus staging repository at which point, we can slurp it up and test it (hopefully by running some test apps). Then, give our vote. This is a bit tricky though because Lukasz is trying to commit changes that will result in making nexus integration possible. So, he'll probably have to change the pom, invoke the maven release plugin, and then check that nexus received the new artifact in our staging repository. I assume we'll see a small flurry of svn commits that look like traditional releases (svn branches, poms having -SNAPSHOT versions removed, etc.). But, nothing will end up on maven central or in people.a.o/dist until after we've voted on the quality. To answer Lukasz's question, I would assume that the section you mention does indeed at least need removed. I haven't looked at the apache parent that we're inheriting from in struts-master, or our nexus configuration, but IIRC, the reposit...@apache.org team indicated that inheriting from the parent is all that is necessary. I would assume though, that we (anyone who plans to perform a release) will need to setup our maven settings.xml file to include our LDAP apache username and password. I would imagine that Nexus is configured to only allow struts committers to push artifacts into the repository. (Wendy, correct me if I'm wrong, but) I think usually this is handled by having a server entry in your settings.xml file that matches up with the id / record in the pom. -Wes -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
