[jboss-jira] [JBoss JIRA] Issue Comment Edited: (JBBUILD-683) Proxy to https://s3.amazonaws.com/maven.springframework.org/milestone under public repo

[Paul Gier (JIRA)]

    [ https://issues.jboss.org/browse/JBBUILD-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607525#comment-12607525 ] 

Paul Gier edited comment on JBBUILD-683 at 6/9/11 10:30 AM:
------------------------------------------------------------

Should we be using this URL instead?  
http://maven.springframework.org/milestone

The most recent docs I found about the various spring repos are from this blog post:
http://blog.springsource.com/2009/12/02/obtaining-spring-3-artifacts-with-maven/

An older blog post points to the amazon URL
http://blog.springsource.com/2007/09/18/maven-artifacts-2/


      was (Author: pgier):
    Should we be using this URL instead?  
http://maven.springframework.org/milestone

The most recent docs I found about the various spring repos are from this blog post:
http://blog.springsource.com/2009/12/02/obtaining-spring-3-artifacts-with-maven/
  
> Proxy to https://s3.amazonaws.com/maven.springframework.org/milestone under public repo
> ---------------------------------------------------------------------------------------
>
>                 Key: JBBUILD-683
>                 URL: https://issues.jboss.org/browse/JBBUILD-683
>             Project: JBoss Build System
>          Issue Type: Feature Request
>          Components: Sonatype
>            Reporter: Manik Surtani
>            Assignee: Paul Gier
>            Priority: Blocker
>
> Can we add this repo to the Nexus proxy so I don't have to hardcode it in my project POMs?  This is for milestone releases of Spring artefacts that don't go to central.
> https://s3.amazonaws.com/maven.springframework.org/milestone

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira