This has only been happening recently - its like maven cant find 6.1.6 version of jetty. Change the line in your pom.xml to:
[6.1.6,) That will fix the problem for now... I need to change this in the archetypes but it will then mean that Eclipse wont run the tests out of the box (it appears to always try to donwload jetty 7 which doesn't have the right class)... Hmm. Annoying! Cheers, Tim On 31/07/2009 17:36, "glenn" <gl...@exmbly.com> wrote: > > Tim > > I cleaned out my local repository and even did a reindexing. When I > tried to run the basic > archetype this time, I got the following error: > > Couldn't find a version in [6.1.17, 6.1.18, 6.1.19] to match range > [6.1.6,6.1.6] > org.mortbay.jetty:jetty:jar:null > > from the specified remote repositories: > apache.incubating (http://people.apache.org/repo/m2-incubating- > repository), > scala-tools.org (http://scala-tools.org/repo-releases), > central (http://repo1.maven.org/maven2), > scala-tools.org.snapshots (http://scala-tools.org/repo-snapshots) > > I thought this problem was fixed a while ago. > > Glenn... > > On Jul 31, 9:26 am, David Pollak <feeder.of.the.be...@gmail.com> > wrote: >> On Fri, Jul 31, 2009 at 8:55 AM, glenn <gl...@exmbly.com> wrote: >> >>> Tim, >> >>> I'm using Eclipse's maven plugin to create a new maven project with >>> the following parameters: >> >>> <groupId>net.liftweb</groupId> >>> <artifactId>lift-archetype-basic</artifactId> >>> <version>1.1-SNAPSHOT</version> >>> <repository>http://scala-tools.org/repo-snapshot</repository> >> >>> The pom this creates in my project uses the 2.7.4 scala version. >> >>> Could it be that my local .m2 repository is not being updated with a >>> new archetype from repo-snapshot? >> >> Yeah... if there's a way to specify the "-U" flag from Eclipse, that should >> pull the latest from all the repos. >> >> >> >> >> >>> Glenn... >> >>> On Jul 31, 8:40 am, Timothy Perrett <timo...@getintheloop.eu> wrote: >>>> Glenn, >> >>>> What command are you using to pull the archetype? Its certainly not an >>> issue >>>> in lift as we don't have any 2.7.4 refs in the codebase now. >> >>>> The archetype catalog athttp://scala-tools.org/howeverstill points to >>> 1.0 >>>> of Lift, so that's on 2.7.3... >> >>>> Cheers, Tim >> >>>> On 31/07/2009 16:26, "glenn" <gl...@exmbly.com> wrote: >> >>>>> Seems like every time I create a new LIft project in Eclipse with , >>>>> drawing on the snapshots inhttp://scala-tools.org/repo-snapshots, I >>>>> get errors, telling me I'm missing some Apache commons jar, or worse. >>>>> Could It be a problem with my system? It's worked in the past without >>>>> a hitch, but something has changed, and I don't believe I've changed >>>>> anything local to cause this. >> >>>>> I am still investigating, but if anyone has similar experiences, that >>>>> would help me to debug. >> >>>>> Also, shouldn't the POM use >> >>>>> Thanks. <scala.version>2.7.5</scala.version> >> >>>>> rather than 2.7.4? >> >>>>> Glenn... >> >> -- >> Lift, the simply functional web frameworkhttp://liftweb.net >> Beginning Scalahttp://www.apress.com/book/view/1430219890 >> Follow me:http://twitter.com/dpp >> Git some:http://github.com/dpp > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---