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
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
On Tue, Jun 16, 2009 at 6:43 AM, Oliver Lambert olambo...@gmail.com wrote:
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
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
