This makes things a little easier for me: alias g1="cd ..; mvn clean compile; cd *app" alias g2="cd ../*per; mvn install; cd ../*app" alias g3="mvn jetty:run" alias g3u="mvn jetty:run -U"
(My persistence layer is xxx-per, and my app is xxx-app.) I run the above from the xxx/xxx-app directory. Chas. Tim Perrett wrote: > Cheers guys, one thing though that confusses me about Dereks' JPA > example is why the JPA stuff wasn't consolidated into the lift > project? > > For instance, I understand why you might well want or need a separate > persistence tier in some applications or environments, but for the > majority of arbitrary applications, it seems to just make things more > complex / lengthy as you need to do "mvn install" all the time after > any updates. So far, having it consolidated seems to be going very > well 8-) > > Also, IMO, the Model.scala and JPA.scala should really have the > majority of there functionality taken out and put into the lift master > under say, net.liftweb.jpa.Helpers or something? It appears that the > functionality is so generic im copying and pasting a lot of the time > those files into different project :-( > > Cheers > > Tim > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
