[SWS-500] remove amazonaws repository urls from spring-ws-parent pom Created: 13/Apr/09  Updated: 04/May/12  Resolved: 13/May/09

Status: Closed
Project: Spring Web Services
Component/s: Core
Affects Version/s: 1.5.6
Fix Version/s: 1.5.7

Type: Bug Priority: Minor
Reporter: Wouter de Vaal Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

When running mvn site on my project, the build hang on the following lines:

[INFO] Generating "Dependencies" report.
[WARNING] The repository url 'http://s3.amazonaws.com/maven.springframework.org/external' is invalid - Repository 'spring-external' will be blacklisted.
[WARNING] The repository url 'http://s3.amazonaws.com/maven.springframework.org/release' is invalid - Repository 'spring-release' will be blacklisted.

Doing a grep on my .m2 directory there was only file containing these repository urls:

~/.m2$ grep -r 'amazonaws' *
repository/org/springframework/ws/spring-ws-parent/1.5.5/spring-ws-parent-1.5.5.pom: <url>http://s3.amazonaws.com/maven.springframework.org/release</url>
repository/org/springframework/ws/spring-ws-parent/1.5.5/spring-ws-parent-1.5.5.pom: <url>http://s3.amazonaws.com/maven.springframework.org/external</url>

I think these are outdated and should be removed.or at least replaced by something that works.



 Comments   
Comment by Arjen Poutsma [ 13/May/09 ]

Quite frankly, I have no idea what's causing this. I can duplicate the warnings, but the build does not hang for me.

I think it might be due to Amazon S3 returning non-standard HTTP headers or bodies, which isn't something I can fix.

Comment by Wouter de Vaal [ 13/May/09 ]

My point was that the amazonaws repositories aren't used anywhere in Spring anymore, but for this parent pom. My suggestion is removing this repository, as it's not valid anymore

Comment by Arjen Poutsma [ 13/May/09 ]

You are right: other projects use maven.springframework.org/external or maven.springframework.org/release, but these resolve to the same Amazon S3 host/directory as the ones presently there. I will fix.

Comment by Arjen Poutsma [ 13/May/09 ]

I replaced the s3.amazonaws.com URLS with maven.springframework.org ones.

Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

Generated at Sat Dec 16 15:02:27 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.