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?
I find that maven will ease your work a lot. Usually it take only one
step to get a lift app running.
mvn jetty:run
if you want to create an eclipse project for the downloaded app, you
just do mvn eclipse:eclipse and then import it to eclipse.
Not using maven you'll have to deal with all the dependency management
by yourself :(
Can you specify what do you expected from maven? what were the
problems encountered?
On Tue, Apr 14, 2009 at 12:11 PM, 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?
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 ?
Br's,
Marius
On Apr 14, 2:23 pm, Joćo Pereira <joaomiguel.pere...@gmail.com> wrote:
> I find that maven will ease your work a lot. Usually it take only one
> step to get a lift app running.
> mvn jetty:run
> if you want to create an eclipse project for the downloaded app, you
> just do mvn eclipse:eclipse and then import it to eclipse.
> Not using maven you'll have to deal with all the dependency management
> by yourself :(
> Can you specify what do you expected from maven? what were the
> problems encountered?
> On Tue, Apr 14, 2009 at 12:11 PM, 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?
On Tue, Apr 14, 2009 at 1:38 PM, marius d. <marius.dan...@gmail.com> wrote:
> 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 ?
Nice angle!
Or perhaps have an online service where you can specify the archetype
details and have a compressed payload downloaded?
> > I find that maven will ease your work a lot. Usually it take only one
> > step to get a lift app running.
> > mvn jetty:run
> > if you want to create an eclipse project for the downloaded app, you
> > just do mvn eclipse:eclipse and then import it to eclipse.
> > Not using maven you'll have to deal with all the dependency management
> > by yourself :(
> > Can you specify what do you expected from maven? what were the
> > problems encountered?
> > On Tue, Apr 14, 2009 at 12:11 PM, 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?
I am using Ant (or respectively the Eclipse built-in Ant-based
dependency management) for my Java and Scala work. I am on Vista.
Maven sputtered a number of different error messages on several
trials. I don't want to learn Maven and get to the bottom of this.
Busy schedules... What I am trying to do is to fit Lift into my
existing dev tool stack, Eclipse, Tomcat, MySQL, and (possibly)
Hibernate.
Cheers, CNX
On Apr 14, 6:23 pm, Joćo Pereira <joaomiguel.pere...@gmail.com> wrote:
> 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 ?
>> I find that maven will ease your work a lot. Usually it take only one
>> step to get a lift app running.
>> mvn jetty:run
>> if you want to create an eclipse project for the downloaded app, you
>> just do mvn eclipse:eclipse and then import it to eclipse.
>> Not using maven you'll have to deal with all the dependency management
>> by yourself :(
>> Can you specify what do you expected from maven? what were the
>> problems encountered?
>> On Tue, Apr 14, 2009 at 12:11 PM, 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?
> 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?
On Apr 14, 2:40 pm, Viktor Klang <viktor.kl...@gmail.com> wrote:
> On Tue, Apr 14, 2009 at 1:38 PM, marius d. <marius.dan...@gmail.com> wrote:
> > 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 ?
> Nice angle!
> Or perhaps have an online service where you can specify the archetype
> details and have a compressed payload downloaded?
Yup crossed my mind ... and I love it. Basically run the archetype on
demand and serve back the zip content.
> > > I find that maven will ease your work a lot. Usually it take only one
> > > step to get a lift app running.
> > > mvn jetty:run
> > > if you want to create an eclipse project for the downloaded app, you
> > > just do mvn eclipse:eclipse and then import it to eclipse.
> > > Not using maven you'll have to deal with all the dependency management
> > > by yourself :(
> > > Can you specify what do you expected from maven? what were the
> > > problems encountered?
> > > On Tue, Apr 14, 2009 at 12:11 PM, 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?
On Tue, Apr 14, 2009 at 7:58 PM, marius d. <marius.dan...@gmail.com> wrote:
> On Apr 14, 2:40 pm, Viktor Klang <viktor.kl...@gmail.com> wrote:
>> On Tue, Apr 14, 2009 at 1:38 PM, marius d. <marius.dan...@gmail.com> wrote:
>> > 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 ?
>> Nice angle!
>> Or perhaps have an online service where you can specify the archetype
>> details and have a compressed payload downloaded?
> Yup crossed my mind ... and I love it. Basically run the archetype on
> demand and serve back the zip content.
>> > > I find that maven will ease your work a lot. Usually it take only one
>> > > step to get a lift app running.
>> > > mvn jetty:run
>> > > if you want to create an eclipse project for the downloaded app, you
>> > > just do mvn eclipse:eclipse and then import it to eclipse.
>> > > Not using maven you'll have to deal with all the dependency management
>> > > by yourself :(
>> > > Can you specify what do you expected from maven? what were the
>> > > problems encountered?
>> > > On Tue, Apr 14, 2009 at 12:11 PM, 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?
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.
Perhaps. But, it's a bit like this:
"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.
> On Apr 14, 10:58 pm, Timothy Perrett <timo...@getintheloop.eu> wrote: >> Perhaps we could couple this with Hudson? Hudson has an API (see >> here:http://wiki.hudson-ci.org/display/HUDSON/Remote+access+API) so >> perhaps we could serve stuff up on the fly through that? Just >> spitballing here....
Does the ant build file already exist? If not, it wouldn't be too hard to create a maven assembly that "assembles" all the various dependencies and such into a directory (or uses something like the maven-ant-tasks to materialize them for the project later), and includes an ant build script/starter project code. I can add this to my list of things todo, however if someone else is interested and has time, I'm more than willing to help answer questions / point you in the correct maven direction.
I guess it would be ideal to make use of the current archetypes, but I don't even see this as necessary. An assembly for a zip/tgz file could be generated which includes a project-starter kit for ANT and could be deployed into the maven repository with all the other artifacts for a build. This could be downloaded from the maven repository then (and versioned, etc.). We actually use this at work for our "ubiquituous" install (we also have RPMs, etc. for installing our software).
My question here, is why should the project be generated on the fly? Is that so you can have your desired package structure on startup?
On Tue, Apr 14, 2009 at 8:52 PM, tk050305cnx <tk050305...@gmail.com> wrote:
> 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.
> Perhaps. But, it's a bit like this:
> "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."
You know... it's more like:
"I want all of you hundreds of people who have successfully used Lift with
Maven to stop what you're doing and pay attention to me and throw out your
work and do things my way."
While we are a community that welcomes newbies and tries to work with as
many different people and with as many different styles as possible, there
are things that we've collectively learned. We've found that Maven is
preferable for our style of development. If you want to use Ant, there's
nothing stopping you and we'd welcome some Ant scripts for building Lift,
but we're not going to stop what we're doing and write one for you just
because you demand that we do so. Please go back and write the Ant scripts
yourself and contribute to the community rather than being rude to us
because we don't do things the way you want. That will demonstrate that you
are willing to contribute in rather than demand and insult when your demands
are not met.
> 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.
On Tue, Apr 14, 2009 at 8:58 PM, marius d. <marius.dan...@gmail.com> wrote:
> On Apr 14, 2:40 pm, Viktor Klang <viktor.kl...@gmail.com> wrote:
>> On Tue, Apr 14, 2009 at 1:38 PM, marius d. <marius.dan...@gmail.com> wrote:
>> > 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 ?
>> Nice angle!
>> Or perhaps have an online service where you can specify the archetype
>> details and have a compressed payload downloaded?
> Yup crossed my mind ... and I love it. Basically run the archetype on
> demand and serve back the zip content.
>> > > I find that maven will ease your work a lot. Usually it take only one
>> > > step to get a lift app running.
>> > > mvn jetty:run
>> > > if you want to create an eclipse project for the downloaded app, you
>> > > just do mvn eclipse:eclipse and then import it to eclipse.
>> > > Not using maven you'll have to deal with all the dependency management
>> > > by yourself :(
>> > > Can you specify what do you expected from maven? what were the
>> > > problems encountered?
>> > > On Tue, Apr 14, 2009 at 12:11 PM, 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?
<feeder.of.the.be...@gmail.com> wrote: > While we are a community that welcomes newbies and tries to work with as > many different people and with as many different styles as possible, there > are things that we've collectively learned. We've found that Maven is > preferable for our style of development. If you want to use Ant, there's > nothing stopping you and we'd welcome some Ant scripts for building Lift, > but we're not going to stop what we're doing and write one for you just > because you demand that we do so. Please go back and write the Ant scripts > yourself and contribute to the community rather than being rude to us > because we don't do things the way you want. That will demonstrate that you > are willing to contribute in rather than demand and insult when your demands > are not met.
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 :)
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
On 15/04/2009 17:37, "Alexander Kellett" <lypa...@gmail.com> wrote:
> 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 :)
from what i can see the latest sbt supports jetty-run command :)
testing it out now!
next step, write a command for it to perform the equiv of mvn idea:idea.
> 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
> On 15/04/2009 17:37, "Alexander Kellett" <lypa...@gmail.com> wrote:
>> 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 :)
On Wed, Apr 15, 2009 at 8:17 PM, Alexander Kellett <lypa...@gmail.com> wrote:
> from what i can see the latest sbt supports jetty-run command :)
> testing it out now!
> next step, write a command for it to perform the equiv of mvn idea:idea.
> Alex
> On Wed, Apr 15, 2009 at 7:22 PM, Timothy Perrett
> <timo...@getintheloop.eu> wrote:
>> 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
>> On 15/04/2009 17:37, "Alexander Kellett" <lypa...@gmail.com> wrote:
>>> 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 :)
> On Wed, Apr 15, 2009 at 5:26 PM, David Pollak
> <feeder.of.the.be...@gmail.com> wrote:
> > While we are a community that welcomes newbies and tries to work with as
> > many different people and with as many different styles as possible,
> there
> > are things that we've collectively learned. We've found that Maven is
> > preferable for our style of development. If you want to use Ant, there's
> > nothing stopping you and we'd welcome some Ant scripts for building Lift,
> > but we're not going to stop what we're doing and write one for you just
> > because you demand that we do so. Please go back and write the Ant
> scripts
> > yourself and contribute to the community rather than being rude to us
> > because we don't do things the way you want. That will demonstrate that
> you
> > are willing to contribute in rather than demand and insult when your
> demands
> > are not met.
> 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 :)
I am all in favor of an Ant build script or an SBT-based build script. Both
would be great contributions. I do not have time for them, but anyone out
there who has skills with Ant and/or SBT, I'll buy you a beer or two if you
spend a couple of hours putting together examples.
My rant is against the attitude that somehow the Lift community should
instantly change its priorities because one person has a different
perspective on things. We are not waiters in a restaurant. We are not
serving peoples whims. We are a collaborative community. Anybody who
treats the folks in this community as wait-staff fundamentally
misunderstands the ethos of the Lift community.
The Lift community is a place that I like being because almost everybody is
willing to roll up their sleeves and help. Marius, Derek, Tyler, Charles,
Jorge, Tim, etc. roll up their sleeves and help all comers. Each of these
guys can be making more money and/or spending time with their friends and
family rather than helping newbies, but when they came to the community,
they were newbies and I helped them and they have perpetuated that spirit.
Newbies help us by asking questions, by learning Lift, by making
suggestions, by contributing code, and ultimately by helping other newbies.
We welcome different perspectives, but we do not welcome insulting
attitudes.
Had the conversation gone more along the lines of "any chance you'll change
your priorities to support Ant?" "Not for 1.1, but perhaps you can help." "I
can write Ant Scripts, but I need some guidance about the dependencies..."
The poster would have gotten what he wanted and the whole Lift community
would have benefited.
So, yes, I am in favor of lots of different build options. Are committers,
we have limited time and will officially support Maven. If someone else
comes along and demonstrates Ant, SBT, etc. support and sticks with it for a
while, they might become the owner of that build system and a Lift
committer.
attached a replacement for the sbt script provided, with inline
comments for getting it to work. barely tested and trivial. not yet
verified that this works without a preexisting maven install. will
automate more at weekend.
will look into getting the blocking-on-page-load modification into
sbt/lift somehow also given that it has its own continuous compile
system.
> On Wed, Apr 15, 2009 at 9:37 AM, Alexander Kellett <lypa...@gmail.com>
> wrote:
>> On Wed, Apr 15, 2009 at 5:26 PM, David Pollak
>> <feeder.of.the.be...@gmail.com> wrote:
>> > While we are a community that welcomes newbies and tries to work with as
>> > many different people and with as many different styles as possible,
>> > there
>> > are things that we've collectively learned. We've found that Maven is
>> > preferable for our style of development. If you want to use Ant,
>> > there's
>> > nothing stopping you and we'd welcome some Ant scripts for building
>> > Lift,
>> > but we're not going to stop what we're doing and write one for you just
>> > because you demand that we do so. Please go back and write the Ant
>> > scripts
>> > yourself and contribute to the community rather than being rude to us
>> > because we don't do things the way you want. That will demonstrate that
>> > you
>> > are willing to contribute in rather than demand and insult when your
>> > demands
>> > are not met.
>> 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 :)
> I am all in favor of an Ant build script or an SBT-based build script. Both
> would be great contributions. I do not have time for them, but anyone out
> there who has skills with Ant and/or SBT, I'll buy you a beer or two if you
> spend a couple of hours putting together examples.
> My rant is against the attitude that somehow the Lift community should
> instantly change its priorities because one person has a different
> perspective on things. We are not waiters in a restaurant. We are not
> serving peoples whims. We are a collaborative community. Anybody who
> treats the folks in this community as wait-staff fundamentally
> misunderstands the ethos of the Lift community.
> The Lift community is a place that I like being because almost everybody is
> willing to roll up their sleeves and help. Marius, Derek, Tyler, Charles,
> Jorge, Tim, etc. roll up their sleeves and help all comers. Each of these
> guys can be making more money and/or spending time with their friends and
> family rather than helping newbies, but when they came to the community,
> they were newbies and I helped them and they have perpetuated that spirit.
> Newbies help us by asking questions, by learning Lift, by making
> suggestions, by contributing code, and ultimately by helping other newbies.
> We welcome different perspectives, but we do not welcome insulting
> attitudes.
> Had the conversation gone more along the lines of "any chance you'll change
> your priorities to support Ant?" "Not for 1.1, but perhaps you can help." "I
> can write Ant Scripts, but I need some guidance about the dependencies..."
> The poster would have gotten what he wanted and the whole Lift community
> would have benefited.
> So, yes, I am in favor of lots of different build options. Are committers,
> we have limited time and will officially support Maven. If someone else
> comes along and demonstrates Ant, SBT, etc. support and sticks with it for a
> while, they might become the owner of that build system and a Lift
> committer.
> Thanks,
> David
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 processing with sed (it does require sbt, of
course).
Put it in 'project/build/src' directory in your new project directory. Then do:
$ sbt
bootstrap
jetty-run
(fill in the name and other info when prompted)
Thanks again,
-Mark
On 4/16/09, Alexander Kellett <lypa...@gmail.com> wrote:
> attached a replacement for the sbt script provided, with inline
> comments for getting it to work. barely tested and trivial. not yet
> verified that this works without a preexisting maven install. will
> automate more at weekend.
> will look into getting the blocking-on-page-load modification into
> sbt/lift somehow also given that it has its own continuous compile
> system.
> On Thu, Apr 16, 2009 at 3:57 PM, David Pollak
> <feeder.of.the.be...@gmail.com> wrote:
>> On Wed, Apr 15, 2009 at 9:37 AM, Alexander Kellett <lypa...@gmail.com>
>> wrote:
>>> On Wed, Apr 15, 2009 at 5:26 PM, David Pollak
>>> <feeder.of.the.be...@gmail.com> wrote:
>>> > While we are a community that welcomes newbies and tries to work with
>>> > as
>>> > many different people and with as many different styles as possible,
>>> > there
>>> > are things that we've collectively learned. We've found that Maven is
>>> > preferable for our style of development. If you want to use Ant,
>>> > there's
>>> > nothing stopping you and we'd welcome some Ant scripts for building
>>> > Lift,
>>> > but we're not going to stop what we're doing and write one for you just
>>> > because you demand that we do so. Please go back and write the Ant
>>> > scripts
>>> > yourself and contribute to the community rather than being rude to us
>>> > because we don't do things the way you want. That will demonstrate
>>> > that
>>> > you
>>> > are willing to contribute in rather than demand and insult when your
>>> > demands
>>> > are not met.
>>> 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 :)
>> I am all in favor of an Ant build script or an SBT-based build script.
>> Both
>> would be great contributions. I do not have time for them, but anyone out
>> there who has skills with Ant and/or SBT, I'll buy you a beer or two if
>> you
>> spend a couple of hours putting together examples.
>> My rant is against the attitude that somehow the Lift community should
>> instantly change its priorities because one person has a different
>> perspective on things. We are not waiters in a restaurant. We are not
>> serving peoples whims. We are a collaborative community. Anybody who
>> treats the folks in this community as wait-staff fundamentally
>> misunderstands the ethos of the Lift community.
>> The Lift community is a place that I like being because almost everybody
>> is
>> willing to roll up their sleeves and help. Marius, Derek, Tyler, Charles,
>> Jorge, Tim, etc. roll up their sleeves and help all comers. Each of these
>> guys can be making more money and/or spending time with their friends and
>> family rather than helping newbies, but when they came to the community,
>> they were newbies and I helped them and they have perpetuated that spirit.
>> Newbies help us by asking questions, by learning Lift, by making
>> suggestions, by contributing code, and ultimately by helping other
>> newbies.
>> We welcome different perspectives, but we do not welcome insulting
>> attitudes.
>> Had the conversation gone more along the lines of "any chance you'll
>> change
>> your priorities to support Ant?" "Not for 1.1, but perhaps you can help."
>> "I
>> can write Ant Scripts, but I need some guidance about the dependencies..."
>> The poster would have gotten what he wanted and the whole Lift community
>> would have benefited.
>> So, yes, I am in favor of lots of different build options. Are
>> committers,
>> we have limited time and will officially support Maven. If someone else
>> comes along and demonstrates Ant, SBT, etc. support and sticks with it for
>> a
>> while, they might become the owner of that build system and a Lift
>> committer.
>> Thanks,
>> David
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?
On Thu, Apr 16, 2009 at 7:11 PM, Mark Harrah <dmhar...@gmail.com> wrote:
> 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 processing with sed (it does require sbt, of
> course).
> Put it in 'project/build/src' directory in your new project directory. Then do:
> $ sbt
> bootstrap
> jetty-run
> (fill in the name and other info when prompted)
> Thanks again,
> -Mark
> On 4/16/09, Alexander Kellett <lypa...@gmail.com> wrote:
>> attached a replacement for the sbt script provided, with inline
>> comments for getting it to work. barely tested and trivial. not yet
>> verified that this works without a preexisting maven install. will
>> automate more at weekend.
>> will look into getting the blocking-on-page-load modification into
>> sbt/lift somehow also given that it has its own continuous compile
>> system.
>> On Thu, Apr 16, 2009 at 3:57 PM, David Pollak
>> <feeder.of.the.be...@gmail.com> wrote:
>>> On Wed, Apr 15, 2009 at 9:37 AM, Alexander Kellett <lypa...@gmail.com>
>>> wrote:
>>>> On Wed, Apr 15, 2009 at 5:26 PM, David Pollak
>>>> <feeder.of.the.be...@gmail.com> wrote:
>>>> > While we are a community that welcomes newbies and tries to work with
>>>> > as
>>>> > many different people and with as many different styles as possible,
>>>> > there
>>>> > are things that we've collectively learned. We've found that Maven is
>>>> > preferable for our style of development. If you want to use Ant,
>>>> > there's
>>>> > nothing stopping you and we'd welcome some Ant scripts for building
>>>> > Lift,
>>>> > but we're not going to stop what we're doing and write one for you just
>>>> > because you demand that we do so. Please go back and write the Ant
>>>> > scripts
>>>> > yourself and contribute to the community rather than being rude to us
>>>> > because we don't do things the way you want. That will demonstrate
>>>> > that
>>>> > you
>>>> > are willing to contribute in rather than demand and insult when your
>>>> > demands
>>>> > are not met.
>>>> 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 :)
>>> I am all in favor of an Ant build script or an SBT-based build script.
>>> Both
>>> would be great contributions. I do not have time for them, but anyone out
>>> there who has skills with Ant and/or SBT, I'll buy you a beer or two if
>>> you
>>> spend a couple of hours putting together examples.
>>> My rant is against the attitude that somehow the Lift community should
>>> instantly change its priorities because one person has a different
>>> perspective on things. We are not waiters in a restaurant. We are not
>>> serving peoples whims. We are a collaborative community. Anybody who
>>> treats the folks in this community as wait-staff fundamentally
>>> misunderstands the ethos of the Lift community.
>>> The Lift community is a place that I like being because almost everybody
>>> is
>>> willing to roll up their sleeves and help. Marius, Derek, Tyler, Charles,
>>> Jorge, Tim, etc. roll up their sleeves and help all comers. Each of these
>>> guys can be making more money and/or spending time with their friends and
>>> family rather than helping newbies, but when they came to the community,
>>> they were newbies and I helped them and they have perpetuated that spirit.
>>> Newbies help us by asking questions, by learning Lift, by making
>>> suggestions, by contributing code, and ultimately by helping other
>>> newbies.
>>> We welcome different perspectives, but we do not welcome insulting
>>> attitudes.
>>> Had the conversation gone more along the lines of "any chance you'll
>>> change
>>> your priorities to support Ant?" "Not for 1.1, but perhaps you can help."
>>> "I
>>> can write Ant Scripts, but I need some guidance about the dependencies..."
>>> The poster would have gotten what he wanted and the whole Lift community
>>> would have benefited.
>>> So, yes, I am in favor of lots of different build options. Are
>>> committers,
>>> we have limited time and will officially support Maven. If someone else
>>> comes along and demonstrates Ant, SBT, etc. support and sticks with it for
>>> a
>>> while, they might become the owner of that build system and a Lift
>>> committer.
>>> Thanks,
>>> David
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.
On Apr 14, 6:53 am, TylerWeir <tyler.w...@gmail.com> wrote:
> > 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?
|
