The M2 local repo and remote repo are NOT the same. They look the same at a first glance.
Some very important metadata files gets renamed when downloaded to your ~/.m2! Compare your local repo with some real remote repo! Look for maven-metadata.xml files! This difference get even worse with snapshot repositories.... Set up a proxy like Proximity or Maven-Proxy... ~t~ On 6/16/06, EJ Ciramella <[EMAIL PROTECTED]> wrote:
I have run about 90% of the goals that the users will run and have built up my local .m2 repository. From here, I've copied over these files to our (apache 2 served up) internal remote repository. But now I see: Downloading: file://build.corp.upromise.com/mavenrepository/org/apache/maven/wagon/wa gon-http-lightweight/1.0-alpha-5/wagon-http-lightweight-1.0-alpha-5.pom [WARNING] Unable to get resource from repository local-central (file://build.corp.upromise.com/mavenrepository) Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-http-lightwei ght/1.0-alpha-5/wagon-http-lightweight-1.0-alpha-5.pom 5K downloaded What am I doing wrong and how should I be setting up this internal remote repository?
