Even if I find maven quite helpful for Lift there are people that just
want to stay away from maven. I can understand that. Perhaps it would
be helpful to also have some ant script to build a lift project? ...
or perhaps have a downloadable zip archive from lift's site that
contains incipient projects like the results produced by Lift's
archetypes? ... so that people can just download that project zip file
with the ant build in it and then start building the app on top of
that? ... would that work ?
Cheers, Tim
Perhaps. But, it's a bit like this:
On Apr 14, 7:53 pm, TylerWeir <tyler.w...@gmail.com> wrote:
>
> You'll have a better experience if you take the time to learn how
> maven works.
"Can I have a beer, please."
"We don't have beer right now, but I think you would have a better
experience with our own brand whiskey."
Never mind. I can't get it to work right now. I know how to write
servlets and filters directly, so that may be the easier approach for
me. I'll certainly check in again later.
Thanks & keep up the good work,
CNX
many people are scared by maven. myself included after my previous
"fun" with getting lift working.
is there a way to get a self contained "hello world" zip up on github
if it is not already there? afaiu maven also allows for local caches,
could that that be placed in the zip, or is it simply too big?
i think that might scare people much less than pasting the very opaque
four liner which asks questions i do not know the answer to :)
Alex
We could do something like this, but it would still need to use maven to
start the server (mvn jetty:run). Unfortunately, you'll need to have a local
maven repo, that's a) part of how maven works and b) the legal implications
of us redistributing a bunch of other peoples code to make it self contained
probably had various ramifications.
We could supply a hello world on github, but this is just what the archetype
creates for you. Perhaps this is a case of education in our community about
how maven works? If there were supporting documentation would it be so
scary? (it might help you answer mvn's questions too!)
Cheers, Tim
Alex
I am a newcomer to Scala and Lift, and I plan on trying to figure out
how to use either Buildr or Raven, to run Lift, and if I can
successfully do so I will try to share my work. If I cannot, I will
probably stop pursuing Lift and start looking at other areas of Scala.
I say this simply to state you will drive many potential users of Lift
away by enforcing the use of Maven without even giving sufficient
documentation to allow other build tools to be used. I cannot see any
productivity gain from any web framework over other existing
competitors that could offset the productivity loss from using Maven.
hey sean,
i hope you're open to other possibilities than buildr/raven :)
i myself have no real interest in messing with maven after my terrible
experiences from when i was working on java code full time..
i just verified that it takes just a few minutes to install sbt and
get a running lift app :)
you can find the things needed in Marks Harrah's reply to this thread
and sbt can be found at http://code.google.com/p/simple-build-tool/
I am a newcomer to Scala and Lift, and I plan on trying to figure out
how to use either Buildr or Raven, to run Lift, and if I can
successfully do so I will try to share my work. If I cannot, I will
probably stop pursuing Lift and start looking at other areas of Scala.
I say this simply to state you will drive many potential users of Lift
away by enforcing the use of Maven without even giving sufficient
documentation to allow other build tools to be used.
I cannot see any
productivity gain from any web framework over other existing
competitors that could offset the productivity loss from using Maven.
> > expected output. I don't want to bother with Maven at this time. Can
>
> You'll have a better experience if you take the time to learn how
> maven works.
>
> On Apr 14, 7:11 am, tk050305cnx <tk050305...@gmail.com> wrote:
>
> > I am new to Liftweb. Unfortunately, the example app in the "getting
> > started" doc did not work. That is... Maven did not produce the
> > expected output. I don't want to bother with Maven at this time. Can
> > you point me to a source that describes how to set up a helloworld
> > type of application manually and deploy it on Tomcat? Is there any
> > Eclipse automation for that?
>
> > Cheers, CNX
=begin
Differences between maven pom.xml and this buildr file:
1. I could not get buildr to build this project without setting
my environment variable SCALA_HOME to point to my scala
distribution.
2. Many jars had to be specified manually that did not need not
specified in the maven pom.xml
3. They jetty plugin seems to force it's own version, 6.1.3, though
the source code documentation tauntingly suggests a way to specify
your own version
I am inlining the buildr buildfile I created for Lift's hello world
example below.