> Maven is totally the right tool for lift project management, and im not
> suggesting moving that or anything, but im considering having a lift
> archetype that uses SBT so people have the choice when developing their
> applications.
You might have already seen this, but Nathan and I did some wo
:
> excellent, thanks for finishing this off mark! is it possible this
> might get into a later sbt release or does this belong somewhere in
> the lift source tree?
>
> thank you!
> Alex
>
> On Thu, Apr 16, 2009 at 7:11 PM, Mark Harrah wrote:
> > Hi,
> >
>
Hi,
Thanks for putting effort into this. The inline dependency
declarations replace the pom.xml, so it isn't needed. You can also
declare the archetype as a dependency and extract and process it. I
have attached a project definition that does not require downloading
the zip manually or processi
Hi David,
I have used sbt to compile and test lift at some point (I haven't
updated for the recent reorganization). However, let me point out
that sbt cannot do the following yet:
1) build with a different version of scala/java than the one sbt was called with
2) package a war file
3) start jett
