Unsupported Protocol: 's3'

[jpeterson]

I just checked out the newly minted 1.0.0 version (congrats by the way!) and I am getting the following build error:


$ mvn install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Spring Web Services
[INFO] Spring XML
[INFO] Spring O/X Mapping
[INFO] Spring WS Core
[INFO] Spring WS Security
[INFO] Spring WS Archetype
[INFO] Spring O/X Mapping - Java 5
[INFO] Spring WS Core - Java 5
Downloading: http://download.java.net/maven/1//net.java.dev.jets3t/jars/jets3t-0.5.0.jar
[WARNING] Unable to get resource from repository java.net http://download.java.net/maven/1/)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Unsupported Protocol: 's3': Cannot find wagon which supports the requested protocol: s3
net.java.dev.jets3t:jets3t:jar:0.5.0

from the specified remote repositories:
central (http://repo1.maven.org/maven2),
spring-release (s3://maven.springframework.org/release),
java.net (http://download.java.net/maven/1/),
spring-milestone (s3://maven.springframework.org/milestone),
spring-snapshot (s3://maven.springframework.org/snapshot)
Path to dependency:
1) org.springframework.ws:spring-ws:pom:1.0.0
2) org.springframework.aws:spring-aws-maven:jar:1.1.1
3) net.java.dev.jets3t:jets3t:jar:0.5.0



[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Mon Aug 20 15:06:08 PDT 2007
[INFO] Final Memory: 2M/4M
[INFO] ------------------------------------------------------------------------


Any ideas?

[Ben Hale]

What target are you running exactly? The s3 protocol is only needed for deployment of the artifact so you should never run into it. In addition to that both the spring-aws-maven and the net.java.dev.jets3t artifacts are available on http://repo1.maven.org/maven2 (the central repo).

[jpeterson]

Im running:


$ mvn install

[kxkannan]

I am getting the same "Unsupported protocol s3" error when I run the "mvn package" in the echo example (as told in the readme.txt file in the echo samples directory).

Unsupported Protocol: 's3': Cannot find wagon which supports the requested protocol: s3
net.java.dev.jets3t:jets3t:jar:0.5.0

from the specified remote repositories:
central (http://repo1.maven.org/maven2),
spring-release (s3://maven.springframework.org/release),
java.net (http://download.java.net/maven/1/),
spring-milestone (s3://maven.springframework.org/milestone),
spring-snapshot (s3://maven.springframework.org/snapshot)
Path to dependency:
1) org.springframework.ws:echo:war:1.0.0
2) org.springframework.aws:spring-aws-maven:jar:1.1.1
3) net.java.dev.jets3t:jets3t:jar:0.5.0


Any ideas on how to resolve this ?

Thanks,
Kannan

[Ben Hale]

I did some research on the central repo and the file is actually located there: http://repo1.maven.org/maven2/net/java/dev/jets3t/jets3t/0.5.0/

If you are having trouble retrieving the file, you may have some configuration issues with a proxy or something like that.

[jpeterson]

I have no proxy installed.

The odd thing is you can see maven trying to download jets3t.


Downloading: http://download.java.net/maven/1//net.java.dev.jets3t/jars/jets3t-0.5.0.jar


Maven see's all of the repositories, but for some reason is only trying java.net, not central.


central (http://repo1.maven.org/maven2),
spring-release (s3://maven.springframework.org/release),
java.net (http://download.java.net/maven/1/),
spring-milestone (s3://maven.springframework.org/milestone),
spring-snapshot (s3://maven.springframework.org/snapshot)


I also appear to not be the only one having this problem...

[Ben Hale]

Yeah, but it's a configuration issue. It'll never find that jar in the java.net maven1 repo. So you'll need to update your configuration to look into the central maven2 repo.

[jpeterson]

Ok, i can look into doing that. But the odd thing is that I have made no configuration changes. For all intents and purposes it is a stock maven2 install.

[Arjen Poutsma]

Do you have a special proxy that you normally use for internet access? You might want to specify this for maven2...

[jpeterson]

Nope, no proxy.

[Arjen Poutsma]

I still can't reproduce this for neither the modules nor the samples with a clean spring-ws 1.0.0 download (the full distribution), and an empty maven repository. You might try upgrading to maven 2.0.7 if you haven't done so already. I'm running OS X 10.4.10, Java 1.5.0-7.

Also, try cleaning your local maven repository (~/.m2/repository on Unix, C:\Documents and Settings\user\.m2\repository or something similar on Windows). Sometimes, when maven cannot download an artifact temporarily, it creates an empty pom, which can screw things up.

[kxkannan]

My issue was the maven repository was pointing to the wrong remote repository
at download.java.net/maven/1 under the C:\Documents and Settings\kkannan\.m2\repository. I had to change that to http://repo1.maven.org/maven2 to work.

Initially I experimented with adding the remote repository directly to my echo sample's pom.xml as and it got rid of the errors that I was having.

<repositories>
<repository>
<id>repo1-maven</id>
<url>http://repo1.maven.org/maven2</url>
</repository>
</repositories>


Thanks,
Kannan