You should still be able to use the 0.7.4 launcher if you want.
Otherwise, the 0.7.5 launcher uses Ivy 2.2.0 and defaults to sbt 0.7.5
and Scala 2.8.1 for new projects. In either case, do 'set sbt.version
0.7.5.RC0' and 'reload' at the sbt prompt for an existing project.
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To post to this group, send email to simple-b...@googlegroups.com.
To unsubscribe from this group, send email to simple-build-t...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
> Wait a second, my patch is still not listed in the changelog?
It's in 0.7.5.RC0, it just wasn't on the Changes page.
> >> For more options, visit this group at
> >> http://groups.google.com/group/simple-build-tool?hl=en.
> > --
> > Viktor Klang,
> > Code Connoisseur
> > Work: Scalable Solutions <http://www.scalablesolutions.se>
Maybe this is obvious to everyone else, but in case anyone is as slow as
I am and has like 100 sbt projects lying around: I eventually figured
out that this can be accomplished non-interactively in the manner shown
at the end. It was the whole "quoting the whole thing" part which threw
me, as the error given is
[error] Invalid arguments for 'set': expected property name and new value.
so I went for a couple wild geese. Now I have this handy alias.
alias sbtup="sbt 'set sbt.version 0.7.5.RC0' update"
Paul Phillips | If this is raisin, make toast with it.
Caged Spirit |
ha! spill, pupil |----------* http://www.improving.org/paulp/ *----------
On Thu, 13 Jan 2011 02:06:19 -0800 (PST)
Jimmy Yuen Ho Wong <wyu...@gmail.com> wrote:
> It doesn't seem to be able to load Jetty dependencies once I've
> overriden jettyEnvXml. I keep getting
> java.lang.NoClassDefFoundError: org/eclipse/jetty/plus/webapp/
> Error running jetty-run: Jetty and its dependencies must be on the
> test classpath: java.lang.NoClassDefFoundError: org/eclipse/jetty/plus/
> I went into the sbt console-project and saw the jetty dependencies
> (webapp, server and plus) are clearly in testClasspath and
> jettyClasspath and I can confirm that jettyEnvXml really does point to
> the right file. I don't know what went wrong. This new feature clearly
> needs to be fixed and be documented.
Can you post an example project? There is a basic test for this feature that passes, so it isn't completely broken. Your issue may be unrelated to jettyEnvXml.