[
https://issues.apache.org/jira/browse/WICKET-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael O'Cleirigh updated WICKET-2918:
---------------------------------------
Attachment: wicket-1.4.x-pom.patch
wicket-1.5.x-pom.patch
I've attached patches for the 1.4.x branch pom.xml aswell as the current 1.5
trunk pom.xml
I created a <parent> entry for each that references the org.apache.apache
artifact version 7.
http://svn.apache.org/repos/asf/maven/pom/tags/apache-7/pom.xml
Then I copied the bamboo profile renaming it to apache-nexus-deploy and
removing the <dependencyManagement> sections as this allow the values set in
the parent pom to be inherited.
I tested with both pom's and with mvn -Papache-nexus-deploy deploy I see it
trying to upload the snapshot into the apache nexus repository.
For example in 1.5-SNAPSHOT I see:
[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] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error deploying artifact: Failed to transfer file:
https://repository.apache.org/content/repositories/snapshots/org/apache/wicket/wicket-parent/1.5-SNAPSHOT/wicket-parent-1.5-20100617.013747-1.pom.
Return code is: 401
The id's of the repositories are:
1. snapshot: apache.snapshots.https
2. release: apache.releases.https
Once the setup is done through the apache ticket there should be a
username/password combination usable for each or both. This pair of id's will
then need to be used for snapshot deployment within the apache hudson build
cluster and also as part of the individual developer manged release process.
I'm not totally sure on this part but will dig into it and update this ticket
as required with additional information.
> Use Apache Nexus Maven Repository instead of self hosted maven repository on
> wicketstuff.org
> --------------------------------------------------------------------------------------------
>
> Key: WICKET-2918
> URL: https://issues.apache.org/jira/browse/WICKET-2918
> Project: Wicket
> Issue Type: Improvement
> Components: wicket, wicket-auth-roles, wicket-datetime,
> wicket-examples, wicket-extensions, wicket-guice, wicket-jmx, wicket-portlet,
> wicket-quickstart, wicket-spring
> Affects Versions: 1.4.10, 1.5-M1
> Reporter: Michael O'Cleirigh
> Attachments: wicket-1.4.x-pom.patch, wicket-1.5.x-pom.patch
>
>
> As of June 15, 2010 the wicketstuff.org maven repository was down. Instead
> of fixing the wicketstuff.org server I proposed that the org.apache.wicket
> artifacts be switched to deploy through the Apache Nexus Maven repository.
> See this discussion:
> http://apache-wicket.1842946.n4.nabble.com/proposal-Use-apache-nexus-repository-for-org-apache-wicket-release-and-snapshot-artifacts-tp2256728p2256728.html
> 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
> I think the issue needs to be created by a org.apache.wicket committer
> This migration will allow snapshots to be deployed from the apache hudson
> build cluster into the apache nexus maven repository.
> There is some kind of switchover that occurs for artifacts that are located
> through the people at apache method but since wicket artifacts that have been
> released are in central I see limited impact at this point.
> Future releases would deploy into this nexus repository which supports
> staging.
> I will attach diff's for the trunk 1.5-SNAPSHOT pom.xml and the 1.4.x branch
> 1.4-SNAPSHOT pom.xml that will create the two additional snapshot and release
> profiles that can be used for this purpose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
