Yes, it will do this. We'll probably sort that out for 2.0.1, but for now you can report the missing pom as an issue or create it in your repo.
- Brett On 10/20/05, Eric Pugh <[EMAIL PROTECTED]> wrote: > Interesting... > > I do have maven 2 beta 3 as well, but when I check the version: > > xativa:~/Documents/java/ergito/manager eric$ mvn -v > Maven version: 2.0 > > The messages I am getting are: > Downloading: http://bronze.jbpub.com/maven/repo/jurt/jurt/ergito/jurt- > ergito.pom > [WARNING] Unable to get resource from repository bronze (http:// > bronze.jbpub.com/maven/repo) > Downloading: http://repo1.maven.org/maven2/mssqlserver/mssqlserver/ > ergito/mssqlserver-ergito.pom > [WARNING] Unable to get resource from repository central (http:// > repo1.maven.org/maven2) > > Which is Maven attempting to retrieve non existent pom's..... > > Eric > > On Oct 20, 2005, at 6:19 PM, Carlos Sanchez wrote: > > > 2.0 final doesn't check for poms after they are dowloaded. That > > happened with first beta versions > > > > On 10/20/05, Eric Pugh <[EMAIL PROTECTED]> wrote: > > > >> Hi all, > >> > >> I'm noticing that M2 is constantly checking for POM's from the > >> repositories. It seems like I can control how often we check via: > >> <repositories> > >> <repository> > >> <release> > >> <enabled>true</enabled> > >> <updatePolicy>daily</updatePolicy> > >> <checksumPolicy>warn</checksumPolicy> > >> </release> > >> <id>central</id> > >> <name>Maven Repo</name> > >> <url>http://repo1.maven.org/maven2</url> > >> <layout>default</layout> > >> </repository> > >> </repositories> > >> > >> > >> However, the <release> tag causes an XML parsing error: > >> > >> Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: > >> Unrecognised tag: 'release' (position: START_TAG seen ...<repository> > >> \n <release>... @125:16) > >> at > >> org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseRepository > >> (MavenXpp3Reader.java:3656) > >> > >> Most of my "build" time is filled with attempting to download POM's > >> that don't exist. Should I create them in my local corporate > >> instead? > >> > >> Eric > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
