You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Lukasz Lenart <lu...@googlemail.com> on 2010/05/11 21:54:19 UTC
Fwd: [jira] Closed: (INFRA-2682) Nexus access for Struts
Hi,
So we are ready to use Nexus, but the question is how? Any help or tip
is appreciated!
Regards
--
Łukasz
http://www.lenart.org.pl/
Kapituła Javarsovia 2010
http://javarsovia.pl
---------- Forwarded message ----------
From: Brian Fox (JIRA) <ji...@apache.org>
Date: 2010/5/11
Subject: [jira] Closed: (INFRA-2682) Nexus access for Struts
To: lukasz.lenart@gmail.com
[ https://issues.apache.org/jira/browse/INFRA-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed INFRA-2682.
----------------------------
Resolution: Fixed
The repo is prepared and the artifacts migrated. Use the latest apache
pom and you should be good (you can remove the distributionManagement
sections for release and snapshots and just inherit from the parent)
> Nexus access for Struts
> -----------------------
>
> Key: INFRA-2682
> URL: https://issues.apache.org/jira/browse/INFRA-2682
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Lukasz Lenart
> Assignee: Brian Fox
>
> Please create Nexus setup for Struts project
> The Vote
> http://old.nabble.com/-VOTE--Move-future-struts-releases-to-apache%27s-Nexus-Pro-instance-td28015056.html
> The Source
> https://svn.apache.org/repos/asf/struts/
> Thanks in advance!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
Posted by Wendy Smoak <ws...@gmail.com>.
On Wed, May 26, 2010 at 3:00 AM, Lukasz Lenart
<lu...@googlemail.com> wrote:
> In apache parent pom is:
...
> <snapshotRepository>
> <id>apache.snapshots.https</id>
> <name>${distMgmtSnapshotsName}</name>
> <url>${distMgmtSnapshotsUrl}</url>
> </snapshotRepository>
> </distributionManagement>
>
> The only concern I have is that I don't know what are these two variables.
Haven't they written up something on how to use Nexus / the ASF parent
pom? You can ask on the repository@ mailing list, or drop by
#asfinfra when one of the repo admins is around if you need help.
I think what they're doing here is giving you the choice of where to
publish your snapshots, and you're intended to define those two
properties elsewhere in the pom.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
Posted by Lukasz Lenart <lu...@googlemail.com>.
Ok, I see your point, next time I will try to be more accurate with
the names, eg. release (in terms of ASF), publish archetype to staging
repo (in terms of Maven), should be sufficient.
Kind regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Kapituła Javarsovia 2010 http://javarsovia.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
Posted by Martin Cooper <ma...@apache.org>.
On Tue, May 25, 2010 at 1:51 PM, Wes Wannemacher <we...@wantii.com> wrote:
> On Tue, May 25, 2010 at 10:35 AM, Wendy Smoak <ws...@gmail.com> wrote:
>> On Tue, May 25, 2010 at 10:21 AM, Lukasz Lenart
>> <lu...@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.
That was basically my point. At the ASF, a release is a package made
available to the general public, and as such it can only be made after
a vote by the relevant PMC.
I understand that Maven uses the term 'release' to mean something
different, but that just means we need to qualify the term when we are
talking about a Maven procedure. When Lukasz said he had "made the
release", that, at the ASF, will normally be taken to mean an ASF
release, which requires a vote. Thus it was an incorrect statement.
For someone from another project, or the ASF board, who is not
familiar with Maven to drop in here and see that statement and see no
corresponding vote, well, that would be bad.
So when we mean the Maven thing that they happen to call a release,
let's just be explicit that we're talking about the Maven thing. And
if we use the term 'release' without qualification, let's use that to
refer only to what the ASF calls a release, with a corresponding vote.
--
Martin Cooper
> 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 repository@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-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
Posted by Lukasz Lenart <lu...@googlemail.com>.
Thanks Wendy and Wes!
In apache parent pom is:
<distributionManagement>
<!-- Site omitted - each project must provide their own -->
<repository>
<id>apache.releases.https</id>
<name>Apache Release Distribution Repository</name>
<url>https://repository.apache.org/service/local/staging/deploy/maven2</url>
</repository>
<snapshotRepository>
<id>apache.snapshots.https</id>
<name>${distMgmtSnapshotsName}</name>
<url>${distMgmtSnapshotsUrl}</url>
</snapshotRepository>
</distributionManagement>
The only concern I have is that I don't know what are these two variables.
Regards
--
Łukasz
mobile + 48 606 323 122 http://www.lenart.org.pl/
Kapituła Javarsovia 2010 http://javarsovia.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
Posted by Wes Wannemacher <we...@wantii.com>.
On Tue, May 25, 2010 at 10:35 AM, Wendy Smoak <ws...@gmail.com> wrote:
> On Tue, May 25, 2010 at 10:21 AM, Lukasz Lenart
> <lu...@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 repository@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-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
Posted by Wendy Smoak <ws...@gmail.com>.
On Tue, May 25, 2010 at 10:21 AM, Lukasz Lenart
<lu...@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-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
Posted by Lukasz Lenart <lu...@googlemail.com>.
2010/5/25 Martin Cooper <ma...@apache.org>:
> On Tue, May 25, 2010 at 4:47 AM, Lukasz Lenart
> <lu...@googlemail.com> wrote:
>> 2010/5/15 Martin Cooper <ma...@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-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
Posted by Martin Cooper <ma...@apache.org>.
On Tue, May 25, 2010 at 4:47 AM, Lukasz Lenart
<lu...@googlemail.com> wrote:
> 2010/5/15 Martin Cooper <ma...@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>
> <id>struts-staging</id>
> <name>Apache Struts Staging Repository</name>
> <url>scp://people.apache.org/www/people.apache.org/builds/struts/${project.version}/m2-staging-repository</url>
> </repository>
> <snapshotRepository>
> <uniqueVersion>true</uniqueVersion>
> <id>apache.snapshots</id>
> <name>Apache Development Snapshot Repository</name>
> <url>scp://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-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
Posted by Lukasz Lenart <lu...@googlemail.com>.
2010/5/15 Martin Cooper <ma...@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>
<id>struts-staging</id>
<name>Apache Struts Staging Repository</name>
<url>scp://people.apache.org/www/people.apache.org/builds/struts/${project.version}/m2-staging-repository</url>
</repository>
<snapshotRepository>
<uniqueVersion>true</uniqueVersion>
<id>apache.snapshots</id>
<name>Apache Development Snapshot Repository</name>
<url>scp://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-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
Posted by Martin Cooper <ma...@apache.org>.
On Wed, May 12, 2010 at 4:42 AM, Lukasz Lenart
<lu...@googlemail.com> wrote:
> 2010/5/12 Wes Wannemacher <we...@wantii.com>:
>> What I'll do (in the near-term) is try to configure hudson so that it
>> deploys snapshots to nexus and try to update confluence so that people
>> will know to point to add apache's nexus as a snapshot repo for
>> struts.
>
> As I understand I must upgrade that pom
> https://svn.apache.org/repos/asf/struts/maven/trunk/pom/pom.xml
>
> to use the latest apache.org parent pom. Do we need a release for that?
If it's a published artifact, it needs a release, so yes.
--
Martin Cooper
> Regards
> --
> Łukasz
> http://www.lenart.org.pl/
> Kapituła Javarsovia 2010
> http://javarsovia.pl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
Posted by Lukasz Lenart <lu...@googlemail.com>.
2010/5/12 Wes Wannemacher <we...@wantii.com>:
> What I'll do (in the near-term) is try to configure hudson so that it
> deploys snapshots to nexus and try to update confluence so that people
> will know to point to add apache's nexus as a snapshot repo for
> struts.
As I understand I must upgrade that pom
https://svn.apache.org/repos/asf/struts/maven/trunk/pom/pom.xml
to use the latest apache.org parent pom. Do we need a release for that?
Regards
--
Łukasz
http://www.lenart.org.pl/
Kapituła Javarsovia 2010
http://javarsovia.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [jira] Closed: (INFRA-2682) Nexus access for Struts
Posted by Wes Wannemacher <we...@wantii.com>.
I haven't taken a comprehensive look at this yet, but...
I was able to login here -
http://repository.apache.org
using my apache username and password.
So... I'm guessing that what we need to do is remove the custom
configuration from our poms for the deploy phase. Then, verify that we
are inheriting from the latest apache parent pom. Then, when we do
`mvn release:perform` it should deploy the jars to apache's nexus.
What I'll do (in the near-term) is try to configure hudson so that it
deploys snapshots to nexus and try to update confluence so that people
will know to point to add apache's nexus as a snapshot repo for
struts.
I'll post updates as I get stuff figured out.
Thanks for picking this up for me!
-Wes
On Tue, May 11, 2010 at 3:54 PM, Lukasz Lenart
<lu...@googlemail.com> wrote:
> Hi,
>
> So we are ready to use Nexus, but the question is how? Any help or tip
> is appreciated!
>
>
> Regards
> --
> Łukasz
> http://www.lenart.org.pl/
> Kapituła Javarsovia 2010
> http://javarsovia.pl
>
>
> ---------- Forwarded message ----------
> From: Brian Fox (JIRA) <ji...@apache.org>
> Date: 2010/5/11
> Subject: [jira] Closed: (INFRA-2682) Nexus access for Struts
> To: lukasz.lenart@gmail.com
>
>
>
> [ https://issues.apache.org/jira/browse/INFRA-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Brian Fox closed INFRA-2682.
> ----------------------------
>
> Resolution: Fixed
>
> The repo is prepared and the artifacts migrated. Use the latest apache
> pom and you should be good (you can remove the distributionManagement
> sections for release and snapshots and just inherit from the parent)
>
>> Nexus access for Struts
>> -----------------------
>>
>> Key: INFRA-2682
>> URL: https://issues.apache.org/jira/browse/INFRA-2682
>> Project: Infrastructure
>> Issue Type: Sub-task
>> Security Level: public(Regular issues)
>> Components: Nexus
>> Reporter: Lukasz Lenart
>> Assignee: Brian Fox
>>
>> Please create Nexus setup for Struts project
>> The Vote
>> http://old.nabble.com/-VOTE--Move-future-struts-releases-to-apache%27s-Nexus-Pro-instance-td28015056.html
>> The Source
>> https://svn.apache.org/repos/asf/struts/
>> Thanks in advance!
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Wes Wannemacher
Head Engineer, WanTii, Inc.
Need Training? Struts, Spring, Maven, Tomcat...
Ask me for a quote!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org