[JBoss JIRA] Created: (JBBUILD-683) Proxy to https://s3.amazonaws.com/maven.springframework.org/milestone under public repo
1:53 p.m.
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
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
9:02 a.m.
New subject: [JBoss JIRA] Updated: (JBBUILD-683) Proxy to https://s3.amazonaws.com/maven.springframework.org/milestone under public repo
[
https://issues.jboss.org/browse/JBBUILD-683?page=com.atlassian.jira.plugi...
]
Manik Surtani updated JBBUILD-683:
----------------------------------
Priority: Blocker (was: Major)
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
9:02 a.m.
New subject: [JBoss JIRA] Updated: (JBBUILD-683) Proxy to https://s3.amazonaws.com/maven.springframework.org/milestone under public repo
[
https://issues.jboss.org/browse/JBBUILD-683?page=com.atlassian.jira.plugi...
]
Manik Surtani updated JBBUILD-683:
----------------------------------
Complexity: Low
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
9:11 a.m.
New subject: [JBoss JIRA] Commented: (JBBUILD-683) Proxy to https://s3.amazonaws.com/maven.springframework.org/milestone under public repo
[
https://issues.jboss.org/browse/JBBUILD-683?page=com.atlassian.jira.plugi...
]
Paul Gier commented on JBBUILD-683:
-----------------------------------
Hi Manik,
Can you tell me which groupIds will come from this repo? Just org.springframework?
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
9:15 a.m.
New subject: [JBoss JIRA] Commented: (JBBUILD-683) Proxy to https://s3.amazonaws.com/maven.springframework.org/milestone under public repo
[
https://issues.jboss.org/browse/JBBUILD-683?page=com.atlassian.jira.plugi...
]
Manik Surtani commented on JBBUILD-683:
---------------------------------------
Yup
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
9:27 a.m.
New subject: [JBoss JIRA] Commented: (JBBUILD-683) Proxy to https://s3.amazonaws.com/maven.springframework.org/milestone under public repo
[
https://issues.jboss.org/browse/JBBUILD-683?page=com.atlassian.jira.plugi...
]
Paul Gier commented on JBBUILD-683:
-----------------------------------
Should we be using this URL instead?
http:// maven.springframework.org/milestone
The only docs I could find about the various spring repos are from this blog post:
http://blog.springsource.com/2009/12/02/obtaining-spring-3-artifacts-with...
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
9:27 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBBUILD-683) Proxy to https://s3.amazonaws.com/maven.springframework.org/milestone under public repo
[
https://issues.jboss.org/browse/JBBUILD-683?page=com.atlassian.jira.plugi...
]
Paul Gier edited comment on JBBUILD-683 at 6/9/11 10:26 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...
was (Author: pgier):
Should we be using this URL instead?
http:// maven.springframework.org/milestone
The only docs I could find about the various spring repos are from this blog post:
http://blog.springsource.com/2009/12/02/obtaining-spring-3-artifacts-with...
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
9:31 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBBUILD-683) Proxy to https://s3.amazonaws.com/maven.springframework.org/milestone under public repo
[
https://issues.jboss.org/browse/JBBUILD-683?page=com.atlassian.jira.plugi...
]
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...
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...
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
10:15 a.m.
New subject: [JBoss JIRA] Closed: (JBBUILD-683) Proxy to https://s3.amazonaws.com/maven.springframework.org/milestone under public repo
[
https://issues.jboss.org/browse/JBBUILD-683?page=com.atlassian.jira.plugi...
]
Paul Gier closed JBBUILD-683.
-----------------------------
Fix Version/s: Build Support 2011
Resolution: Done
New proxy repo added: http://maven.springframework.org/milestone/
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
Fix For: Build Support 2011
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
5536
days inactive
5537
days old
8 comments
2 participants
participants (2)
-
Manik Surtani (JIRA) -
Paul Gier (JIRA)