[Lift] Re: Lift Installers
Actually, I believe it's more due to the maven archetype plugin not knowing about the most recent lift. When we start mirroring the scala-tools repository on central, this should be fixed. On Sun, Jan 18, 2009 at 3:54 PM, Tim Perrett wrote: > > Matt, > > Well spotted - this must be something to do with what's hosted on > scala-tools. I'll drop David B a note about this... > > Tim > > On Jan 18, 6:02 pm, Matt Harrington wrote: > > Update: "mvn archetype:generate" gets you Lift 0.8, but "mvn > > archetype:generate -DarchetypeCatalog=http://scala-tools.org/"; gets > > you 0.9. > > > > Matt > > > > On Sun, Jan 18, 2009 at 9:50 AM, Matt Harrington > wrote: > > > An updated catalog would certainly be helpful. I believe it still has > > > Lift 0.8, and it's broken. > > > > > Matt > > > > > On Fri, Jan 16, 2009 at 3:37 PM, Tim Perrett > wrote: > > > > >> Possibly - but this is what I mean about using the auto-generated, one > > >> liner with maven rather than the -D hell we have... > > > > >> I'll tap up David B and see if he knows how far that system can be > > >> extended (i.e. to add another stage to say if you want snapshot, or > > >> release version of lift) > > > > >> Thoughts? > > > > >> Cheers > > > > >> Tim > > > > >> On Jan 16, 9:46 pm, Matt Harrington wrote: > > >>> I like the idea of sticking with plain maven. What do you think > about > > >>> lifting, no pun intended, the maven syntax generator from Wicket's > > >>> quickstart page? > > > > >>>http://wicket.apache.org/quickstart.html > > > > >>> Matt > > > > >>> On Fri, Jan 16, 2009 at 10:54 AM, Tim Perrett > wrote: > > > > >>> > People, > > > > >>> > I'm going to finish the lift installers this weekend and I just got > to > > >>> > thinking about writing some shell scripts to include as well. > However, > > >>> > I then got to think about previous conversations had on this list > and > > >>> > im wondering if we even need shell scripts to wrap the maven > > >>> > commands? > > > > >>> > I mean, as lift nears 1.0, the API is solidifying, and the need for > > >>> > users to track the snapshots will become less and less unless > someone > > >>> > has a direct need to (or want to), or they are a committer. In this > > >>> > way, I see: > > > > >>> > mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/ > > > > >>> > becomming the main way to get started with lift? The installers > would > > >>> > then just need to provide a well setup environment etc (which I > have > > >>> > covered off already). It just strikes me that I don't want to start > re- > > >>> > inventing the wheel by creating generation scripts etc etc when > maven > > >>> > can handle stuff like project templates. > > > > >>> > Thoughts? > > > > >>> > Tim > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift Installers
> Install Java if it's not already installed. Set JAVA_HOME. Yup it already does this too (provides the bundles I gave you a while back are still on scala-tools) > I think JavaRebel installation should be opt-in rather than opt-out. Yeah - its an option during the install. You can choose to install it, and if you choose to install it it wont actually be hooked into maven by default. As we discussed previously this slows maven compilation five fold so having it turned on by default isnt a great idea. I think this is a fair rational, what are your thoughts? Cheers, Tim --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift Installers
On Sun, Jan 18, 2009 at 1:06 PM, Tim Perrett wrote: > > Getting back on topic - if the generate command were to actually use > the right version of Lift, this would indeed be a nice solution? > > Otherwise, the installer does the following: > > - install maven 2.0.9 > - install java rebel 1.2.2 > - adds maven to the PATH > > Is there anything else it needs to do? Install Java if it's not already installed. Set JAVA_HOME. I think JavaRebel installation should be opt-in rather than opt-out. > > > Cheers, Tim > > > > -- Lift, the simply functional web framework http://liftweb.net Collaborative Task Management http://much4.us 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift Installers
Getting back on topic - if the generate command were to actually use the right version of Lift, this would indeed be a nice solution? Otherwise, the installer does the following: - install maven 2.0.9 - install java rebel 1.2.2 - adds maven to the PATH Is there anything else it needs to do? Cheers, Tim --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift Installers
Matt, Well spotted - this must be something to do with what's hosted on scala-tools. I'll drop David B a note about this... Tim On Jan 18, 6:02 pm, Matt Harrington wrote: > Update: "mvn archetype:generate" gets you Lift 0.8, but "mvn > archetype:generate -DarchetypeCatalog=http://scala-tools.org/"; gets > you 0.9. > > Matt > > On Sun, Jan 18, 2009 at 9:50 AM, Matt Harrington wrote: > > An updated catalog would certainly be helpful. I believe it still has > > Lift 0.8, and it's broken. > > > Matt > > > On Fri, Jan 16, 2009 at 3:37 PM, Tim Perrett wrote: > > >> Possibly - but this is what I mean about using the auto-generated, one > >> liner with maven rather than the -D hell we have... > > >> I'll tap up David B and see if he knows how far that system can be > >> extended (i.e. to add another stage to say if you want snapshot, or > >> release version of lift) > > >> Thoughts? > > >> Cheers > > >> Tim > > >> On Jan 16, 9:46 pm, Matt Harrington wrote: > >>> I like the idea of sticking with plain maven. What do you think about > >>> lifting, no pun intended, the maven syntax generator from Wicket's > >>> quickstart page? > > >>>http://wicket.apache.org/quickstart.html > > >>> Matt > > >>> On Fri, Jan 16, 2009 at 10:54 AM, Tim Perrett > >>> wrote: > > >>> > People, > > >>> > I'm going to finish the lift installers this weekend and I just got to > >>> > thinking about writing some shell scripts to include as well. However, > >>> > I then got to think about previous conversations had on this list and > >>> > im wondering if we even need shell scripts to wrap the maven > >>> > commands? > > >>> > I mean, as lift nears 1.0, the API is solidifying, and the need for > >>> > users to track the snapshots will become less and less unless someone > >>> > has a direct need to (or want to), or they are a committer. In this > >>> > way, I see: > > >>> > mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/ > > >>> > becomming the main way to get started with lift? The installers would > >>> > then just need to provide a well setup environment etc (which I have > >>> > covered off already). It just strikes me that I don't want to start re- > >>> > inventing the wheel by creating generation scripts etc etc when maven > >>> > can handle stuff like project templates. > > >>> > Thoughts? > > >>> > Tim --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift Installers
Update: "mvn archetype:generate" gets you Lift 0.8, but "mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/"; gets you 0.9. Matt On Sun, Jan 18, 2009 at 9:50 AM, Matt Harrington wrote: > An updated catalog would certainly be helpful. I believe it still has > Lift 0.8, and it's broken. > > Matt > > > > On Fri, Jan 16, 2009 at 3:37 PM, Tim Perrett wrote: >> >> Possibly - but this is what I mean about using the auto-generated, one >> liner with maven rather than the -D hell we have... >> >> I'll tap up David B and see if he knows how far that system can be >> extended (i.e. to add another stage to say if you want snapshot, or >> release version of lift) >> >> Thoughts? >> >> Cheers >> >> Tim >> >> On Jan 16, 9:46 pm, Matt Harrington wrote: >>> I like the idea of sticking with plain maven. What do you think about >>> lifting, no pun intended, the maven syntax generator from Wicket's >>> quickstart page? >>> >>> http://wicket.apache.org/quickstart.html >>> >>> Matt >>> >>> On Fri, Jan 16, 2009 at 10:54 AM, Tim Perrett wrote: >>> >>> > People, >>> >>> > I'm going to finish the lift installers this weekend and I just got to >>> > thinking about writing some shell scripts to include as well. However, >>> > I then got to think about previous conversations had on this list and >>> > im wondering if we even need shell scripts to wrap the maven >>> > commands? >>> >>> > I mean, as lift nears 1.0, the API is solidifying, and the need for >>> > users to track the snapshots will become less and less unless someone >>> > has a direct need to (or want to), or they are a committer. In this >>> > way, I see: >>> >>> > mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/ >>> >>> > becomming the main way to get started with lift? The installers would >>> > then just need to provide a well setup environment etc (which I have >>> > covered off already). It just strikes me that I don't want to start re- >>> > inventing the wheel by creating generation scripts etc etc when maven >>> > can handle stuff like project templates. >>> >>> > Thoughts? >>> >>> > Tim >> >> >> > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift Installers
An updated catalog would certainly be helpful. I believe it still has Lift 0.8, and it's broken. Matt On Fri, Jan 16, 2009 at 3:37 PM, Tim Perrett wrote: > > Possibly - but this is what I mean about using the auto-generated, one > liner with maven rather than the -D hell we have... > > I'll tap up David B and see if he knows how far that system can be > extended (i.e. to add another stage to say if you want snapshot, or > release version of lift) > > Thoughts? > > Cheers > > Tim > > On Jan 16, 9:46 pm, Matt Harrington wrote: >> I like the idea of sticking with plain maven. What do you think about >> lifting, no pun intended, the maven syntax generator from Wicket's >> quickstart page? >> >> http://wicket.apache.org/quickstart.html >> >> Matt >> >> On Fri, Jan 16, 2009 at 10:54 AM, Tim Perrett wrote: >> >> > People, >> >> > I'm going to finish the lift installers this weekend and I just got to >> > thinking about writing some shell scripts to include as well. However, >> > I then got to think about previous conversations had on this list and >> > im wondering if we even need shell scripts to wrap the maven >> > commands? >> >> > I mean, as lift nears 1.0, the API is solidifying, and the need for >> > users to track the snapshots will become less and less unless someone >> > has a direct need to (or want to), or they are a committer. In this >> > way, I see: >> >> > mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/ >> >> > becomming the main way to get started with lift? The installers would >> > then just need to provide a well setup environment etc (which I have >> > covered off already). It just strikes me that I don't want to start re- >> > inventing the wheel by creating generation scripts etc etc when maven >> > can handle stuff like project templates. >> >> > Thoughts? >> >> > Tim > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift Installers
Possibly - but this is what I mean about using the auto-generated, one liner with maven rather than the -D hell we have... I'll tap up David B and see if he knows how far that system can be extended (i.e. to add another stage to say if you want snapshot, or release version of lift) Thoughts? Cheers Tim On Jan 16, 9:46 pm, Matt Harrington wrote: > I like the idea of sticking with plain maven. What do you think about > lifting, no pun intended, the maven syntax generator from Wicket's > quickstart page? > > http://wicket.apache.org/quickstart.html > > Matt > > On Fri, Jan 16, 2009 at 10:54 AM, Tim Perrett wrote: > > > People, > > > I'm going to finish the lift installers this weekend and I just got to > > thinking about writing some shell scripts to include as well. However, > > I then got to think about previous conversations had on this list and > > im wondering if we even need shell scripts to wrap the maven > > commands? > > > I mean, as lift nears 1.0, the API is solidifying, and the need for > > users to track the snapshots will become less and less unless someone > > has a direct need to (or want to), or they are a committer. In this > > way, I see: > > > mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/ > > > becomming the main way to get started with lift? The installers would > > then just need to provide a well setup environment etc (which I have > > covered off already). It just strikes me that I don't want to start re- > > inventing the wheel by creating generation scripts etc etc when maven > > can handle stuff like project templates. > > > Thoughts? > > > Tim --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift Installers
I like the idea of sticking with plain maven. What do you think about lifting, no pun intended, the maven syntax generator from Wicket's quickstart page? http://wicket.apache.org/quickstart.html Matt On Fri, Jan 16, 2009 at 10:54 AM, Tim Perrett wrote: > > People, > > I'm going to finish the lift installers this weekend and I just got to > thinking about writing some shell scripts to include as well. However, > I then got to think about previous conversations had on this list and > im wondering if we even need shell scripts to wrap the maven > commands? > > I mean, as lift nears 1.0, the API is solidifying, and the need for > users to track the snapshots will become less and less unless someone > has a direct need to (or want to), or they are a committer. In this > way, I see: > > mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/ > > becomming the main way to get started with lift? The installers would > then just need to provide a well setup environment etc (which I have > covered off already). It just strikes me that I don't want to start re- > inventing the wheel by creating generation scripts etc etc when maven > can handle stuff like project templates. > > Thoughts? > > Tim > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
