[jira] Commented: (WICKET-2918) Use Apache Nexus Maven Repository instead of self hosted maven repository on wicketstuff.org

["Martin Grigorov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976050#action_12976050 ] 

Martin Grigorov commented on WICKET-2918:
-----------------------------------------

Can we close this ticket ?
Wicket uses Apache Nexus. WicketStuff uses Sonatype OSS Nexus ...

> 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.