Springframework Maven OSGified Artifacts Repository doesn't work

[jacek.laskowski]

Hi,

On the front page there are Maven Repositories listed, but they don't seem to be working. I'm getting errors "The specified key does not exist" from S3 service. Is it me or do they really malfunction? Shouldn't the repos be updated or removed from the page at the very least?

Jacek

[habuma]

The S3 repositories come in sets of 2 URLs. The one that starts with "http://s3." are the ones you'll want to tell Maven about, but you won't be able to explore them in your browser. The one that starts with "http://s3browse." is the one that you can explore in a web browser.

It's kinda weird how that works...actually, even more annoying. But it is what it is.

[jacek.laskowski]

I kept thinking maven is just a mere http client as far as dependency downloads are concerned, but somehow I'd have missed obvious things and was easily mistaken. What's the reason to keep them both? Interesting.

Jacek

[habuma]

I kept thinking maven is just a mere http client as far as dependency downloads are concerned, but somehow I'd have missed obvious things and was easily mistaken. What's the reason to keep them both? Interesting.

Honestly, I've never taken the time to figure it out--I just know that if you want to browse it, use the s3browse...if you want to *use* it, then use s3. It's really an Amazon S3 kinda question. Maybe someone else in these forums knows the answer.

[Costin Leau]

This is how S3 works - S3 serves HTTP requests but doesn't act as a full HTTP server. When Maven looks for certain artifacts, it checks various locations which match on the S3 server and thus it starts downloading. However, when you are trying to hit S3 with a browser you are browsing and actually looking for a web page that is not found (since it doesn't exist). Moreover, S3 cannot create a browsing page (as most server do) listing resources since that's not its purpose.
To find out more about S3, take a look at its home page at: http://aws.amazon.com/s3/