pre-scanned build extension not being resolved

[Frank Adcock <fr...@bushlife.com.au>]

I have the problem with Eclipse where the spring-aws-maven project will not
build within eclipse because it is unable to solve the extension
(effectively to itself).

 

The error I get is:

 

Project build error:Cannot resolve pre-scanned extension artifact:
org.springframework.aws:spring-aws-maven: Unable to download metadata from
repository for extension artifact
'org.springframework.aws:spring-aws-maven:jar:1.2.3-SNAPSHOT': Unable to
read the metadata file for artifact
'org.springframework.aws:spring-aws-maven:jar': POM
'org.springframework.aws:spring-aws-maven' not found in repository: Unable
to download the artifact from any repository

 

  org.springframework.aws:spring-aws-maven:pom:1.2.3-SNAPSHOT

 

from the specified remote repositories:

  central (http://repo1.maven.org/maven2)

 for project org.springframework.aws:spring-aws-maven     spring-aws-maven
pom.xml            line 1    1209686291687 2245

 

 

 

Running it at a command prompt, or via the context menu Run-As Maven Install
produces the correct jar files and meta-data to the local repository, but
for some reason it is trying to locate it in the repo1.maven.org/maven2
repository.

 

I have the maven integration plugin using the same settings files as maven
is using, of which the only settings in the local one are for proxy, and the
gobal settings are as per maven 2.0.9 release.  The maven integration
version is 0.9.2.20080413-2321 for the scm and subclipse feature, whist the
org.maven.ide.eclipse.feature is at version 0.9.3.20080421-2352

 

Can anyone identify the problem with this?

 

Regards

 

Frank Adcock