Sometimes (is this, folk-tale or truth?) the maven repository around the application you'reworking on may get slightly out of sync. Then you might need to delete the part of the repository that your application is installed into.
On Tue, Jun 16, 2009 at 7:25 PM, Tobias Daub <hannes.flo...@gmx.li> wrote: > > Ok, thanks. > > Well, with the pom.xml file it was a little bit strange. I had to change > the Lift version to do the mvn clean install and then change it back. > I've no idea why, but it was the only things that helped..... > > > > Maven stores project dependencies in a repository (by default, its > > called .m2). When you move a Lift application from one system to > > another, the repository on the new system may need to be updated, > > hence your requirement to do a "mvn clean install". > > > > Don't know what you changed on the pom.xml (if you have any hard coded > > paths, you might have to change them). > > > > On Tue, Jun 16, 2009 at 2:41 AM, Tobias Daub <hannes.flo...@gmx.li > > <mailto:hannes.flo...@gmx.li>> wrote: > > > > > > Hi There, > > > > I would like to know whats the best way to move an existing Lift > > installation from one system to another. I ask this, because I had > > some > > problems after I just copied the whole directory (I had to edit the > > pom.xml file and do "mvn clean install"). > > > > > > thanks > > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
