You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Michael O'Cleirigh <mi...@rivulet.ca> on 2010/06/16 01:56:00 UTC
[proposal] Use apache nexus repository for org.apache.wicket release
and snapshot artifacts.
Hello,
The wicketstuff.org site seems to have gone down over the weekend.
The main item for me is that the maven repository is also missing which
is breaking the wicketstuff-core trunk build (we depend on 1.4-SNAPSHOT).
Apache has a sonatype nexus instance that is available for projects to
use. As far as I can tell this is not being used by Apache Wicket right
now.
I propose that the current wicketstuff.org maven repository unavailable
issue be resolved by migrating the Apache Wicket artifact deployment
process from using the wicketstuff repository to the Apache Nexus maven
repository.
This page has the registration details:
http://www.apache.org/dev/repository-faq.html
It says to create a sub issue on this one:
https://issues.apache.org/jira/browse/INFRA-1896
The creation of the issue has to be done by a project committer.
If this migration is deemed acceptable I would be able to assist since
its similar to what we did for wicketstuff-core to be deployed into the
oss.sonatype.org repository.
Here is a summary of how we deploy wicketstuff-core into a nexus repository:
We use hudson to build and deploy the artifacts into the oss nexus
repository:
1. create profile that defines the repository url for snapshots
2. create <server> section in settings.xml with the username/password to
use when deploying
e.g. in wicketstuff core we use this profile:
<profile>
<id>oss.sonatype.org-snapshots</id>
<distributionManagement>
<snapshotRepository>
<id>sonatype-nexus-snapshots</id>
<name>Sonatype Nexus Snapshots</name>
<url>http://oss.sonatype.org/content/repositories/snapshots</url>
<uniqueVersion>false</uniqueVersion>
</snapshotRepository>
</distributionManagement>
</profile>
and then we specify a custom settings.xml file to the hudson job that
defines a server like this:
<?xml version="1.0"?>
<settings>
<servers>
<!-- todo replace this with the hudson-wicketstuff user -->
<server>
<id>sonatype-nexus-snapshots</id>
<username>username</username>
<password>somepassword</password>
</server>
</servers>
</settings>
Then we activate the profile in the goals and options section like this:
-P oss.sonatype.org-snapshots -fae deploy
Regards,
Mike
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by James Carman <ja...@carmanconsulting.com>.
Sorry, I saw the wicketstuff in the original email. Long day, man.
On Tue, Jun 15, 2010 at 8:42 PM, Jeremy Thomerson
<je...@wickettraining.com> wrote:
> On Tue, Jun 15, 2010 at 6:58 PM, James Carman <ja...@carmanconsulting.com>wrote:
>
>> I believe that repository is for software published by the ASF, but I
>> could be wrong.
>>
>>
> He wants us to deploy Wicket to it, so I think that fits the bill. :)
>
> I'm +1 for this. I'll do the committer part with the help of Michael.
> Let's see if anyone has an objection. Michael, could you open a JIRA for
> this and attach a patch for our pom? If nobody has an objection, I'll work
> on it later in the week.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by James Carman <ja...@carmanconsulting.com>.
We use Artifactory at work, too! :) But, Nexus wasn't around when I
installed it. Artifactory works okay, I guess, but it does have its
bugs of course.
On Wed, Jun 30, 2010 at 8:07 AM, nino martinez wael
<ni...@gmail.com> wrote:
> No problem, we use nexus our self's where I work.. It's just that
> Artifactory was WICKET powered :)
>
> 2010/6/24 James Carman <ja...@carmanconsulting.com>
>
>> And, a LOT of the maven-based projects are going that route. Nexus
>> even makes it easier to do releases "The Apache Way."
>>
>> On Thu, Jun 24, 2010 at 10:03 AM, Jeremy Thomerson
>> <je...@wickettraining.com> wrote:
>> > Because Nexus is hosted and supported by Apache.
>> >
>> > Jeremy Thomerson
>> > -- sent from my smartphone - please excuse formatting and spelling errors
>> >
>> > On Jun 24, 2010 10:01 AM, "nino martinez wael" <
>> nino.martinez.wael@gmail.com>
>> > wrote:
>> >
>> > I know this is sort of off topic, but why don't we use artifactory, it's
>> > opensource and based on wicket..
>> >
>> > 1=http://www.jfrog.org/products.php
>> >
>> > 2010/6/23 Michael O'Cleirigh <mi...@rivulet.ca>
>> >
>> >
>> >> Thanks Martijn and Jeremy for all your work on getting this to work.
>> >>
>> >> I have the 1.4.10-SNAPSH...
>> >
>>
>
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by nino martinez wael <ni...@gmail.com>.
No problem, we use nexus our self's where I work.. It's just that
Artifactory was WICKET powered :)
2010/6/24 James Carman <ja...@carmanconsulting.com>
> And, a LOT of the maven-based projects are going that route. Nexus
> even makes it easier to do releases "The Apache Way."
>
> On Thu, Jun 24, 2010 at 10:03 AM, Jeremy Thomerson
> <je...@wickettraining.com> wrote:
> > Because Nexus is hosted and supported by Apache.
> >
> > Jeremy Thomerson
> > -- sent from my smartphone - please excuse formatting and spelling errors
> >
> > On Jun 24, 2010 10:01 AM, "nino martinez wael" <
> nino.martinez.wael@gmail.com>
> > wrote:
> >
> > I know this is sort of off topic, but why don't we use artifactory, it's
> > opensource and based on wicket..
> >
> > 1=http://www.jfrog.org/products.php
> >
> > 2010/6/23 Michael O'Cleirigh <mi...@rivulet.ca>
> >
> >
> >> Thanks Martijn and Jeremy for all your work on getting this to work.
> >>
> >> I have the 1.4.10-SNAPSH...
> >
>
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by James Carman <ja...@carmanconsulting.com>.
And, a LOT of the maven-based projects are going that route. Nexus
even makes it easier to do releases "The Apache Way."
On Thu, Jun 24, 2010 at 10:03 AM, Jeremy Thomerson
<je...@wickettraining.com> wrote:
> Because Nexus is hosted and supported by Apache.
>
> Jeremy Thomerson
> -- sent from my smartphone - please excuse formatting and spelling errors
>
> On Jun 24, 2010 10:01 AM, "nino martinez wael" <ni...@gmail.com>
> wrote:
>
> I know this is sort of off topic, but why don't we use artifactory, it's
> opensource and based on wicket..
>
> 1=http://www.jfrog.org/products.php
>
> 2010/6/23 Michael O'Cleirigh <mi...@rivulet.ca>
>
>
>> Thanks Martijn and Jeremy for all your work on getting this to work.
>>
>> I have the 1.4.10-SNAPSH...
>
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Jeremy Thomerson <je...@wickettraining.com>.
Because Nexus is hosted and supported by Apache.
Jeremy Thomerson
-- sent from my smartphone - please excuse formatting and spelling errors
On Jun 24, 2010 10:01 AM, "nino martinez wael" <ni...@gmail.com>
wrote:
I know this is sort of off topic, but why don't we use artifactory, it's
opensource and based on wicket..
1=http://www.jfrog.org/products.php
2010/6/23 Michael O'Cleirigh <mi...@rivulet.ca>
> Thanks Martijn and Jeremy for all your work on getting this to work.
>
> I have the 1.4.10-SNAPSH...
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by nino martinez wael <ni...@gmail.com>.
I know this is sort of off topic, but why don't we use artifactory, it's
opensource and based on wicket..
1=http://www.jfrog.org/products.php
2010/6/23 Michael O'Cleirigh <mi...@rivulet.ca>
> Thanks Martijn and Jeremy for all your work on getting this to work.
>
> I have the 1.4.10-SNAPSHOT wicketstuff-core artifacts deploying again now
> that they can fetch the snapshots from
> https://repository.apache.org/content/repositories/snapshots.
>
> Martijn: your Apache Infrastructure ticket has been updated that the builds
> in 1.5.x were failing due to load on the build server. I checked the log
> for #111 and the profile is correct but the goal is still 'install' not
> 'deploy' which is needed to deploy the 1.5-SNAPSHOT artifacts.
>
> A committer can check their ability to deploy by seeing if they can log
> into the nexus interface at http://repository.apache.org then check for
> the 'Enterprise' left section and the 'Staging' link. There should be an
> org.apache.wicket row in the top table and nothing in the bottom table. The
> bottom table can be shown by selecting the org.apache.wicket row in the top
> table.
>
> You should be able to test the staging release process by downloading a
> working copy of trunk, changing the versions to remove the SNAPSHOT (mvn
> versions:set -DnewVersions=1.4.11) and then 'mvn -P apache-nexus-deploy
> clean deploy'
>
> Once deploy has been run you can reload the bottom table in the web
> interface and you should see a unique row for each computer (IP address)
> that has run a deploy. At this point you know it works and can just right
> click the staging row and click 'drop'.
>
> Thanks again,
>
> Mike
>
>
>
> Fixed for 1.4.x, 1.5.x seems to have a hudson error (getting http 500
>> errors)
>>
>> Martijn
>>
>> On Mon, Jun 21, 2010 at 12:13 AM, Michael O'Cleirigh
>> <mi...@rivulet.ca> wrote:
>>
>>
>>> On 20/06/2010 2:12 PM, Jeremy Thomerson wrote:
>>>
>>>
>>>> On Sun, Jun 20, 2010 at 1:01 PM, Martijn Dashorst<
>>>> martijn.dashorst@gmail.com> wrote:
>>>>
>>>>
>>>>
>>>>
>>>>> I've setup the hudson stuff, but I haven't seen an example build that
>>>>> deploys snapshots to nexus.
>>>>>
>>>>> Martijn
>>>>>
>>>>>
>>>>>
>>>> I just committed the pom changes from Michael. I think all you'll need
>>>> to
>>>> do in Hudson (for trunk) is change the build profile to use
>>>> "apache-nexus-deploy" instead of whatever it's currently using. Then we
>>>> can
>>>> duplicate for 1.4.x.
>>>>
>>>>
>>>>
>>> You will need to modify the Goals and options text field of the Hudson
>>> Job
>>> to something like this:
>>> -Papache-nexus-deploy clean deploy
>>>
>>> I looked at build #6 of the 1.4.x branch and the maven command being
>>> executed is:
>>>
>>> Executing Maven: -B -f /home/hudson/hudson-slave/workspace/Apache Wicket
>>> 1.4.x/wicket-1.4.x/pom.xml
>>> -Dmaven.repo.local=/home/hudson/hudson-slave/workspace/Apache Wicket
>>> 1.4.x/.repository clean install
>>>
>>> So the key changes will be to active the new profile and to run the
>>> deploy
>>> goal instead of install.
>>>
>>> When it is working you should see entries like this in the build log:
>>>
>>> [INFO] [deploy:deploy]
>>> [INFO] Retrieving previous build number from apache.snapshots.https
>>> [INFO] repository metadata for: 'snapshot
>>> org.apache.wicket:wicket-parent:1.5-SNAPSHOT' could not be found on
>>> repository: apache.snapshots.https, so will be created
>>> Uploading:
>>>
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/wicket/wicket-parent/1.5-SNAPSHOT/wicket-parent-1.5-20100617.013747-1.pom
>>> 26K uploaded
>>> [INFO] -------------
>>>
>>>
>>> Regards,
>>>
>>> Mike
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Michael O'Cleirigh <mi...@rivulet.ca>.
Thanks Martijn and Jeremy for all your work on getting this to work.
I have the 1.4.10-SNAPSHOT wicketstuff-core artifacts deploying again
now that they can fetch the snapshots from
https://repository.apache.org/content/repositories/snapshots.
Martijn: your Apache Infrastructure ticket has been updated that the
builds in 1.5.x were failing due to load on the build server. I checked
the log for #111 and the profile is correct but the goal is still
'install' not 'deploy' which is needed to deploy the 1.5-SNAPSHOT artifacts.
A committer can check their ability to deploy by seeing if they can log
into the nexus interface at http://repository.apache.org then check for
the 'Enterprise' left section and the 'Staging' link. There should be
an org.apache.wicket row in the top table and nothing in the bottom
table. The bottom table can be shown by selecting the org.apache.wicket
row in the top table.
You should be able to test the staging release process by downloading a
working copy of trunk, changing the versions to remove the SNAPSHOT (mvn
versions:set -DnewVersions=1.4.11) and then 'mvn -P apache-nexus-deploy
clean deploy'
Once deploy has been run you can reload the bottom table in the web
interface and you should see a unique row for each computer (IP address)
that has run a deploy. At this point you know it works and can just
right click the staging row and click 'drop'.
Thanks again,
Mike
> Fixed for 1.4.x, 1.5.x seems to have a hudson error (getting http 500 errors)
>
> Martijn
>
> On Mon, Jun 21, 2010 at 12:13 AM, Michael O'Cleirigh
> <mi...@rivulet.ca> wrote:
>
>> On 20/06/2010 2:12 PM, Jeremy Thomerson wrote:
>>
>>> On Sun, Jun 20, 2010 at 1:01 PM, Martijn Dashorst<
>>> martijn.dashorst@gmail.com> wrote:
>>>
>>>
>>>
>>>> I've setup the hudson stuff, but I haven't seen an example build that
>>>> deploys snapshots to nexus.
>>>>
>>>> Martijn
>>>>
>>>>
>>> I just committed the pom changes from Michael. I think all you'll need to
>>> do in Hudson (for trunk) is change the build profile to use
>>> "apache-nexus-deploy" instead of whatever it's currently using. Then we
>>> can
>>> duplicate for 1.4.x.
>>>
>>>
>> You will need to modify the Goals and options text field of the Hudson Job
>> to something like this:
>> -Papache-nexus-deploy clean deploy
>>
>> I looked at build #6 of the 1.4.x branch and the maven command being
>> executed is:
>>
>> Executing Maven: -B -f /home/hudson/hudson-slave/workspace/Apache Wicket
>> 1.4.x/wicket-1.4.x/pom.xml
>> -Dmaven.repo.local=/home/hudson/hudson-slave/workspace/Apache Wicket
>> 1.4.x/.repository clean install
>>
>> So the key changes will be to active the new profile and to run the deploy
>> goal instead of install.
>>
>> When it is working you should see entries like this in the build log:
>>
>> [INFO] [deploy:deploy]
>> [INFO] Retrieving previous build number from apache.snapshots.https
>> [INFO] repository metadata for: 'snapshot
>> org.apache.wicket:wicket-parent:1.5-SNAPSHOT' could not be found on
>> repository: apache.snapshots.https, so will be created
>> Uploading:
>> https://repository.apache.org/content/repositories/snapshots/org/apache/wicket/wicket-parent/1.5-SNAPSHOT/wicket-parent-1.5-20100617.013747-1.pom
>> 26K uploaded
>> [INFO] -------------
>>
>>
>> Regards,
>>
>> Mike
>>
>>
>>
>>
>>
>
>
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Martijn Dashorst <ma...@gmail.com>.
Fixed for 1.4.x, 1.5.x seems to have a hudson error (getting http 500 errors)
Martijn
On Mon, Jun 21, 2010 at 12:13 AM, Michael O'Cleirigh
<mi...@rivulet.ca> wrote:
> On 20/06/2010 2:12 PM, Jeremy Thomerson wrote:
>>
>> On Sun, Jun 20, 2010 at 1:01 PM, Martijn Dashorst<
>> martijn.dashorst@gmail.com> wrote:
>>
>>
>>>
>>> I've setup the hudson stuff, but I haven't seen an example build that
>>> deploys snapshots to nexus.
>>>
>>> Martijn
>>>
>>
>> I just committed the pom changes from Michael. I think all you'll need to
>> do in Hudson (for trunk) is change the build profile to use
>> "apache-nexus-deploy" instead of whatever it's currently using. Then we
>> can
>> duplicate for 1.4.x.
>>
>
> You will need to modify the Goals and options text field of the Hudson Job
> to something like this:
> -Papache-nexus-deploy clean deploy
>
> I looked at build #6 of the 1.4.x branch and the maven command being
> executed is:
>
> Executing Maven: -B -f /home/hudson/hudson-slave/workspace/Apache Wicket
> 1.4.x/wicket-1.4.x/pom.xml
> -Dmaven.repo.local=/home/hudson/hudson-slave/workspace/Apache Wicket
> 1.4.x/.repository clean install
>
> So the key changes will be to active the new profile and to run the deploy
> goal instead of install.
>
> When it is working you should see entries like this in the build log:
>
> [INFO] [deploy:deploy]
> [INFO] Retrieving previous build number from apache.snapshots.https
> [INFO] repository metadata for: 'snapshot
> org.apache.wicket:wicket-parent:1.5-SNAPSHOT' could not be found on
> repository: apache.snapshots.https, so will be created
> Uploading:
> https://repository.apache.org/content/repositories/snapshots/org/apache/wicket/wicket-parent/1.5-SNAPSHOT/wicket-parent-1.5-20100617.013747-1.pom
> 26K uploaded
> [INFO] -------------
>
>
> Regards,
>
> Mike
>
>
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Michael O'Cleirigh <mi...@rivulet.ca>.
On 20/06/2010 2:12 PM, Jeremy Thomerson wrote:
> On Sun, Jun 20, 2010 at 1:01 PM, Martijn Dashorst<
> martijn.dashorst@gmail.com> wrote:
>
>
>> I've setup the hudson stuff, but I haven't seen an example build that
>> deploys snapshots to nexus.
>>
>> Martijn
>>
> I just committed the pom changes from Michael. I think all you'll need to
> do in Hudson (for trunk) is change the build profile to use
> "apache-nexus-deploy" instead of whatever it's currently using. Then we can
> duplicate for 1.4.x.
>
You will need to modify the Goals and options text field of the Hudson
Job to something like this:
-Papache-nexus-deploy clean deploy
I looked at build #6 of the 1.4.x branch and the maven command being
executed is:
Executing Maven: -B -f /home/hudson/hudson-slave/workspace/Apache
Wicket 1.4.x/wicket-1.4.x/pom.xml
-Dmaven.repo.local=/home/hudson/hudson-slave/workspace/Apache Wicket
1.4.x/.repository clean install
So the key changes will be to active the new profile and to run the
deploy goal instead of install.
When it is working you should see entries like this in the build log:
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from apache.snapshots.https
[INFO] repository metadata for: 'snapshot
org.apache.wicket:wicket-parent:1.5-SNAPSHOT' could not be found on
repository: apache.snapshots.https, so will be created
Uploading:
https://repository.apache.org/content/repositories/snapshots/org/apache/wicket/wicket-parent/1.5-SNAPSHOT/wicket-parent-1.5-20100617.013747-1.pom
26K uploaded
[INFO] -------------
Regards,
Mike
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Jeremy Thomerson <je...@wickettraining.com>.
On Sun, Jun 20, 2010 at 1:01 PM, Martijn Dashorst <
martijn.dashorst@gmail.com> wrote:
> I've setup the hudson stuff, but I haven't seen an example build that
> deploys snapshots to nexus.
>
> Martijn
>
> On Sun, Jun 20, 2010 at 7:36 PM, Jeremy Thomerson
> <je...@wickettraining.com> wrote:
> > On Sat, Jun 19, 2010 at 10:15 AM, Michael O'Cleirigh <
> > michael.ocleirigh@rivulet.ca> wrote:
> >
> >> Hi Jeremy,
> >>
> >>
> >> > On Wed, Jun 16, 2010 at 9:28 PM, Jeremy Thomerson wrote:
> >> >
> >> > Created https://issues.apache.org/jira/browse/INFRA-2805
> >>
> >> The apache infrastructure ticket you registered has been fixed. My
> reading
> >> of the ticket response is that simply activating the
> 'apache-nexus-deploy'
> >> profile in the Hudson job will cause the snapshot artifacts to be
> deployed
> >> into the apache nexus maven repository.
> >>
> >>
> > I noticed this also. I'm not sure who set up our Hudson access with ASF
> > infra..... perhaps someone can chime in. I also think Hudson is only
> > building trunk right now, but we'll need to set up 1.4.x branch builds.
> >
> > --
> > Jeremy Thomerson
> > http://www.wickettraining.com
> >
>
>
I just committed the pom changes from Michael. I think all you'll need to
do in Hudson (for trunk) is change the build profile to use
"apache-nexus-deploy" instead of whatever it's currently using. Then we can
duplicate for 1.4.x.
--
Jeremy Thomerson
http://www.wickettraining.com
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Martijn Dashorst <ma...@gmail.com>.
I've setup the hudson stuff, but I haven't seen an example build that
deploys snapshots to nexus.
Martijn
On Sun, Jun 20, 2010 at 7:36 PM, Jeremy Thomerson
<je...@wickettraining.com> wrote:
> On Sat, Jun 19, 2010 at 10:15 AM, Michael O'Cleirigh <
> michael.ocleirigh@rivulet.ca> wrote:
>
>> Hi Jeremy,
>>
>>
>> > On Wed, Jun 16, 2010 at 9:28 PM, Jeremy Thomerson wrote:
>> >
>> > Created https://issues.apache.org/jira/browse/INFRA-2805
>>
>> The apache infrastructure ticket you registered has been fixed. My reading
>> of the ticket response is that simply activating the 'apache-nexus-deploy'
>> profile in the Hudson job will cause the snapshot artifacts to be deployed
>> into the apache nexus maven repository.
>>
>>
> I noticed this also. I'm not sure who set up our Hudson access with ASF
> infra..... perhaps someone can chime in. I also think Hudson is only
> building trunk right now, but we'll need to set up 1.4.x branch builds.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Jeremy Thomerson <je...@wickettraining.com>.
On Sat, Jun 19, 2010 at 10:15 AM, Michael O'Cleirigh <
michael.ocleirigh@rivulet.ca> wrote:
> Hi Jeremy,
>
>
> > On Wed, Jun 16, 2010 at 9:28 PM, Jeremy Thomerson wrote:
> >
> > Created https://issues.apache.org/jira/browse/INFRA-2805
>
> The apache infrastructure ticket you registered has been fixed. My reading
> of the ticket response is that simply activating the 'apache-nexus-deploy'
> profile in the Hudson job will cause the snapshot artifacts to be deployed
> into the apache nexus maven repository.
>
>
I noticed this also. I'm not sure who set up our Hudson access with ASF
infra..... perhaps someone can chime in. I also think Hudson is only
building trunk right now, but we'll need to set up 1.4.x branch builds.
--
Jeremy Thomerson
http://www.wickettraining.com
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Michael O'Cleirigh <mi...@rivulet.ca>.
Hi Jeremy,
> On Wed, Jun 16, 2010 at 9:28 PM, Jeremy Thomerson wrote:
>
> Created https://issues.apache.org/jira/browse/INFRA-2805
The apache infrastructure ticket you registered has been fixed. My
reading of the ticket response is that simply activating the
'apache-nexus-deploy' profile in the Hudson job will cause the snapshot
artifacts to be deployed into the apache nexus maven repository.
Let me know if there is anything else I can do,
Regards,
Mike
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Jeremy Thomerson <je...@wickettraining.com>.
On Wed, Jun 16, 2010 at 9:28 PM, Jeremy Thomerson <jeremy@wickettraining.com
> wrote:
>
> On Wed, Jun 16, 2010 at 9:14 PM, Michael O'Cleirigh <
> michael.ocleirigh@rivulet.ca> wrote:
>
>> Hello,
>>
>> I've attached the patches for the 1.4.x pom.xml and the trunk 1.5 pom.xml
>> to the issue: (https://issues.apache.org/jira/browse/WICKET-2918)
>>
>> I added the apache parent pom and then created a copy of the bamboo
>> profile minus the dependencyManagement section to let the definition
>> contained in the apache parent pom to be used.
>>
>> I'm not totally clear at this point how the access credentials will work
>> but I think it should be the existing committer username/password
>>
>> Essentially one username/password will have to be placed into a
>> settings.xml file that can be located relative to the workspace directory
>> within the hudson job that builds each version.
>>
>> With the oss.sonatype.org repository I created a set of CI credentials
>> that were then granted permission to deploy a specific groupID
>> (org.wicketstuff) then I used a custom settings.xml file with those
>> credentials to line up with the <id/>tag of the snapshot repository which
>> allowed hudson to deploy the snapshots. In my hudson instance I needed to
>> use shell access to place the settings.xml file in the right location.
>>
>> The release repository is configured to use staging so when a release is
>> cut the deploy will upload into a temporary space within nexus.
>>
>> The nexus username/password is used to authenticate and 'close' (a right
>> click menu option) the repository which makes the uploaded artifacts
>> available for download by those knowing the link. If the vote to release is
>> passed there is an option to 'promote' (another right click menu item) the
>> staged release which will then within an hour sync it up with the central
>> repository.
>> I think testing the nexus release mechanism should be doable before the
>> next release because it can be staged and if successful it can be dropped.
>>
>
> Great! Thanks for all the help. I'll get a ticket going with infra asap.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
Created https://issues.apache.org/jira/browse/INFRA-2805
--
Jeremy Thomerson
http://www.wickettraining.com
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Jeremy Thomerson <je...@wickettraining.com>.
On Wed, Jun 16, 2010 at 9:14 PM, Michael O'Cleirigh <
michael.ocleirigh@rivulet.ca> wrote:
> Hello,
>
> I've attached the patches for the 1.4.x pom.xml and the trunk 1.5 pom.xml
> to the issue: (https://issues.apache.org/jira/browse/WICKET-2918)
>
> I added the apache parent pom and then created a copy of the bamboo profile
> minus the dependencyManagement section to let the definition contained in
> the apache parent pom to be used.
>
> I'm not totally clear at this point how the access credentials will work
> but I think it should be the existing committer username/password
>
> Essentially one username/password will have to be placed into a
> settings.xml file that can be located relative to the workspace directory
> within the hudson job that builds each version.
>
> With the oss.sonatype.org repository I created a set of CI credentials
> that were then granted permission to deploy a specific groupID
> (org.wicketstuff) then I used a custom settings.xml file with those
> credentials to line up with the <id/>tag of the snapshot repository which
> allowed hudson to deploy the snapshots. In my hudson instance I needed to
> use shell access to place the settings.xml file in the right location.
>
> The release repository is configured to use staging so when a release is
> cut the deploy will upload into a temporary space within nexus.
>
> The nexus username/password is used to authenticate and 'close' (a right
> click menu option) the repository which makes the uploaded artifacts
> available for download by those knowing the link. If the vote to release is
> passed there is an option to 'promote' (another right click menu item) the
> staged release which will then within an hour sync it up with the central
> repository.
> I think testing the nexus release mechanism should be doable before the
> next release because it can be staged and if successful it can be dropped.
>
Great! Thanks for all the help. I'll get a ticket going with infra asap.
--
Jeremy Thomerson
http://www.wickettraining.com
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Michael O'Cleirigh <mi...@rivulet.ca>.
Hello,
I've attached the patches for the 1.4.x pom.xml and the trunk 1.5
pom.xml to the issue: (https://issues.apache.org/jira/browse/WICKET-2918)
I added the apache parent pom and then created a copy of the bamboo
profile minus the dependencyManagement section to let the definition
contained in the apache parent pom to be used.
I'm not totally clear at this point how the access credentials will work
but I think it should be the existing committer username/password
Essentially one username/password will have to be placed into a
settings.xml file that can be located relative to the workspace
directory within the hudson job that builds each version.
With the oss.sonatype.org repository I created a set of CI credentials
that were then granted permission to deploy a specific groupID
(org.wicketstuff) then I used a custom settings.xml file with those
credentials to line up with the <id/>tag of the snapshot repository
which allowed hudson to deploy the snapshots. In my hudson instance I
needed to use shell access to place the settings.xml file in the right
location.
The release repository is configured to use staging so when a release is
cut the deploy will upload into a temporary space within nexus.
The nexus username/password is used to authenticate and 'close' (a right
click menu option) the repository which makes the uploaded artifacts
available for download by those knowing the link. If the vote to
release is passed there is an option to 'promote' (another right click
menu item) the staged release which will then within an hour sync it up
with the central repository.
I think testing the nexus release mechanism should be doable before the
next release because it can be staged and if successful it can be dropped.
Regards,
Mike
> I don't see a downside to extending the Apache parent pom.
>
> Martijn
>
> On Wed, Jun 16, 2010 at 4:35 AM, Michael O'Cleirigh
> <mi...@rivulet.ca> wrote:
>
>> )Jeremy Thomerson wrote:
>>
>>> On Tue, Jun 15, 2010 at 6:58 PM, James Carman
>>> <ja...@carmanconsulting.com>wrote:
>>>
>>>
>>>
>>>> I believe that repository is for software published by the ASF, but I
>>>> could be wrong.
>>>>
>>>>
>>>>
>>>>
>>> He wants us to deploy Wicket to it, so I think that fits the bill. :)
>>>
>>> I'm +1 for this. I'll do the committer part with the help of Michael.
>>> Let's see if anyone has an objection. Michael, could you open a JIRA for
>>> this and attach a patch for our pom? If nobody has an objection, I'll
>>> work
>>> on it later in the week.
>>>
>>>
>>>
>> https://issues.apache.org/jira/browse/WICKET-2918
>> I've created an issue and will attach the modified pom's hopefully by
>> tomorrow. My thinking is that only future releases need to be handled so I
>> will create new snapshot and release profiles in the 1.4.x branch and the
>> 1.5 trunk to handle the snapshots right now and to support the next
>> releases.
>>
>> For the snapshots the apache build cluster job definition would need to be
>> modified with the appropriate server credentials to be able to deploy the
>> snapshot artifacts. I also found out that the nexus repository supports
>> auto removal of older snapshots (I think it will keep the last 3) and will
>> remove all the snapshots when a matching release is made. So the
>> <uniqueVersion>false<uniqueVersion> flag is no longer needed and apparently
>> maven 3.0 removes support for this tag anyways.
>>
>> I've looked at a couple of the other apache projects that were setup to use
>> the apache nexus repository and most of the have a parent pom of the
>> org.apache.apache artifact version 7.
>> http://svn.apache.org/repos/asf/maven/pom/tags/apache-7/pom.xml
>>
>> But I will try and figure out a profile that incorporates this definition
>> without needing the parent pom to be defined.
>>
>> Also the ticket (https://issues.apache.org/jira/browse/INFRA-1896) asks that
>> sub issues include a link (like through nabble) to the vote on switching
>> over to the nexus managed repository.
>>
>>
>> Regards,
>>
>> Mike
>>
>>
>
>
>
>
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Martijn Dashorst <ma...@gmail.com>.
I don't see a downside to extending the Apache parent pom.
Martijn
On Wed, Jun 16, 2010 at 4:35 AM, Michael O'Cleirigh
<mi...@rivulet.ca> wrote:
> )Jeremy Thomerson wrote:
>>
>> On Tue, Jun 15, 2010 at 6:58 PM, James Carman
>> <ja...@carmanconsulting.com>wrote:
>>
>>
>>>
>>> I believe that repository is for software published by the ASF, but I
>>> could be wrong.
>>>
>>>
>>>
>>
>> He wants us to deploy Wicket to it, so I think that fits the bill. :)
>>
>> I'm +1 for this. I'll do the committer part with the help of Michael.
>> Let's see if anyone has an objection. Michael, could you open a JIRA for
>> this and attach a patch for our pom? If nobody has an objection, I'll
>> work
>> on it later in the week.
>>
>>
>
> https://issues.apache.org/jira/browse/WICKET-2918
> I've created an issue and will attach the modified pom's hopefully by
> tomorrow. My thinking is that only future releases need to be handled so I
> will create new snapshot and release profiles in the 1.4.x branch and the
> 1.5 trunk to handle the snapshots right now and to support the next
> releases.
>
> For the snapshots the apache build cluster job definition would need to be
> modified with the appropriate server credentials to be able to deploy the
> snapshot artifacts. I also found out that the nexus repository supports
> auto removal of older snapshots (I think it will keep the last 3) and will
> remove all the snapshots when a matching release is made. So the
> <uniqueVersion>false<uniqueVersion> flag is no longer needed and apparently
> maven 3.0 removes support for this tag anyways.
>
> I've looked at a couple of the other apache projects that were setup to use
> the apache nexus repository and most of the have a parent pom of the
> org.apache.apache artifact version 7.
> http://svn.apache.org/repos/asf/maven/pom/tags/apache-7/pom.xml
>
> But I will try and figure out a profile that incorporates this definition
> without needing the parent pom to be defined.
>
> Also the ticket (https://issues.apache.org/jira/browse/INFRA-1896) asks that
> sub issues include a link (like through nabble) to the vote on switching
> over to the nexus managed repository.
>
>
> Regards,
>
> Mike
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Michael O'Cleirigh <mi...@rivulet.ca>.
)Jeremy Thomerson wrote:
> On Tue, Jun 15, 2010 at 6:58 PM, James Carman <ja...@carmanconsulting.com>wrote:
>
>
>> I believe that repository is for software published by the ASF, but I
>> could be wrong.
>>
>>
>>
> He wants us to deploy Wicket to it, so I think that fits the bill. :)
>
> I'm +1 for this. I'll do the committer part with the help of Michael.
> Let's see if anyone has an objection. Michael, could you open a JIRA for
> this and attach a patch for our pom? If nobody has an objection, I'll work
> on it later in the week.
>
>
https://issues.apache.org/jira/browse/WICKET-2918
I've created an issue and will attach the modified pom's hopefully by
tomorrow. My thinking is that only future releases need to be handled
so I will create new snapshot and release profiles in the 1.4.x branch
and the 1.5 trunk to handle the snapshots right now and to support the
next releases.
For the snapshots the apache build cluster job definition would need to
be modified with the appropriate server credentials to be able to deploy
the snapshot artifacts. I also found out that the nexus repository
supports auto removal of older snapshots (I think it will keep the last
3) and will remove all the snapshots when a matching release is made.
So the <uniqueVersion>false<uniqueVersion> flag is no longer needed and
apparently maven 3.0 removes support for this tag anyways.
I've looked at a couple of the other apache projects that were setup to use the apache nexus repository and most of the have a parent pom of the org.apache.apache artifact version 7. http://svn.apache.org/repos/asf/maven/pom/tags/apache-7/pom.xml
But I will try and figure out a profile that incorporates this definition without needing the parent pom to be defined.
Also the ticket (https://issues.apache.org/jira/browse/INFRA-1896) asks that sub issues include a link (like through nabble) to the vote on switching over to the nexus managed repository.
Regards,
Mike
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by Jeremy Thomerson <je...@wickettraining.com>.
On Tue, Jun 15, 2010 at 6:58 PM, James Carman <ja...@carmanconsulting.com>wrote:
> I believe that repository is for software published by the ASF, but I
> could be wrong.
>
>
He wants us to deploy Wicket to it, so I think that fits the bill. :)
I'm +1 for this. I'll do the committer part with the help of Michael.
Let's see if anyone has an objection. Michael, could you open a JIRA for
this and attach a patch for our pom? If nobody has an objection, I'll work
on it later in the week.
--
Jeremy Thomerson
http://www.wickettraining.com
Re: [proposal] Use apache nexus repository for org.apache.wicket
release and snapshot artifacts.
Posted by James Carman <ja...@carmanconsulting.com>.
I believe that repository is for software published by the ASF, but I
could be wrong.
On Tue, Jun 15, 2010 at 7:56 PM, Michael O'Cleirigh
<mi...@rivulet.ca> wrote:
> Hello,
>
> The wicketstuff.org site seems to have gone down over the weekend.
>
> The main item for me is that the maven repository is also missing which is
> breaking the wicketstuff-core trunk build (we depend on 1.4-SNAPSHOT).
>
> Apache has a sonatype nexus instance that is available for projects to use.
> As far as I can tell this is not being used by Apache Wicket right now.
>
> I propose that the current wicketstuff.org maven repository unavailable
> issue be resolved by migrating the Apache Wicket artifact deployment process
> from using the wicketstuff repository to the Apache Nexus maven repository.
>
> This page has the registration details:
> http://www.apache.org/dev/repository-faq.html
>
> It says to create a sub issue on this one:
> https://issues.apache.org/jira/browse/INFRA-1896
>
> The creation of the issue has to be done by a project committer.
>
> If this migration is deemed acceptable I would be able to assist since its
> similar to what we did for wicketstuff-core to be deployed into the
> oss.sonatype.org repository.
>
> Here is a summary of how we deploy wicketstuff-core into a nexus repository:
>
> We use hudson to build and deploy the artifacts into the oss nexus
> repository:
> 1. create profile that defines the repository url for snapshots
> 2. create <server> section in settings.xml with the username/password to use
> when deploying
>
> e.g. in wicketstuff core we use this profile:
>
> <profile>
> <id>oss.sonatype.org-snapshots</id>
>
> <distributionManagement>
> <snapshotRepository>
> <id>sonatype-nexus-snapshots</id>
> <name>Sonatype Nexus Snapshots</name>
> <url>http://oss.sonatype.org/content/repositories/snapshots</url>
> <uniqueVersion>false</uniqueVersion>
> </snapshotRepository>
> </distributionManagement>
> </profile>
>
>
>
> and then we specify a custom settings.xml file to the hudson job that
> defines a server like this:
>
> <?xml version="1.0"?>
> <settings>
>
> <servers>
> <!-- todo replace this with the hudson-wicketstuff user -->
> <server>
> <id>sonatype-nexus-snapshots</id>
> <username>username</username>
> <password>somepassword</password>
> </server>
> </servers>
>
> </settings>
>
> Then we activate the profile in the goals and options section like this:
> -P oss.sonatype.org-snapshots -fae deploy
>
> Regards,
>
> Mike
>
>
>