2. Sometime, better remove the whole thing and install for multiple version updating
rm -Rf ~/.m2/repository/
In Eclipse, maven build... + insall + skip tests
3. An workaround for "Internal error when enable maven dependence management", check in with svn, them import --> import existing maven project, select local projects as a whole.
4. Switch maven version :
$ cd /usr/share/java
$ ls -q1 | grep maven #check if your desired maven version is there
apache-maven-2.0.9
maven-2.2.0
maven-2.2.1
maven-3.0.2
$ cd .. #go up
$ ls -l | grep maven #check what current version is
maven -> java/maven-3.0.2$ sudo rm maven #remove unwanted symlink
Password:
$ sudo ln -s java/maven-2.2.1 maven #set it to maven 2.2.1
5. mvn update version
3. An workaround for "Internal error when enable maven dependence management", check in with svn, them import --> import existing maven project, select local projects as a whole.
4. Switch maven version :
$ cd /usr/share/java
$ ls -q1 | grep maven #check if your desired maven version is there
apache-maven-2.0.9
maven-2.2.0
maven-2.2.1
maven-3.0.2
$ cd .. #go up
$ ls -l | grep maven #check what current version is
maven -> java/maven-3.0.2$ sudo rm maven #remove unwanted symlink
Password:
$ sudo ln -s java/maven-2.2.1 maven #set it to maven 2.2.1
5. mvn update version
mvn versions:set -DnewVersion=2.50.1-SNAPSHOT
It will adjust all pom versions, parent versions and dependency versions in a multi-module project.
update child module version
mvn versions:update-child-modules
If you made a mistake, do
mvn versions:revert
afterwards, or
mvn versions:commit