I'm also having problems getting the artifacts from remote repositories (during both mvn install and mvn eclipse). I do not know if it's because of my DNS problems or maven repository problems. But what's a pain is that sometimes only one pom prevents me from building the entire project or eclipsizing it.
On 2/26/06, Emmanuel Lecharny <[EMAIL PROTECTED]> wrote: > Sorry guys ... Another <rant>Mavhell</rant>... > > I tried a svn up with Alex modif to pom, and then : > - mvn eclipse:eclipse -> booooommmm > - mvn install -> booooommmm > - mvn clean : ok > - mvn install : ok > - mvn eclipse:eclipse -> booooommmm > > [WARNING] Unable to get resource from repository safehaus > (http://m2.safehaus.org) > [INFO] > ---------------------------------------------------------------------------- > [ERROR] BUILD ERROR > [INFO] > ---------------------------------------------------------------------------- > [INFO] Failed to resolve artifact. > > required artifacts missing: > org.apache.directory.daemon:daemon-bootstrappers:jar:1.1.0-SNAPSHOT > > for the artifact: > org.apache.directory.server:apacheds-server-tools:jar:1.1.0-SNAPSHOT > > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > mirrormax.mirror (http://apache.mirrormax.net/apache/maven-repository/), > safehaus (http://m2.safehaus.org), > apache.snapshots (http://cvs.apache.org/maven-snapshot-repository), > seekmeup.mirror (http://apache.seekmeup.com/apache/maven-repository/), > playboy.mirror (http://mirrors.playboy.com/apache/maven-repository/) > > > What I don't get is why when you just svn up, you have to first do a mvn > clean before anything else ? <rant>Ahhh... I liked the way ant worked > with pre-conditions...</rant> I'm a little bit old-fashion, I know, and > also a little bit brain dead too ;) > > Does it work for you on a brand new svn co ? > > --Emmanuel > -- Ersin
