Problem when using different versions of Java (eclipse vs. mvn-command)

[oldschoolBavarianReferenceSystem]

Do you think the following mistake is worth to be mentioned in a developer-FAQ?

After mvn eclipse:eclipse I got the following error:

Unbound classpath container: 'JRE System Library [JavaSE-1.8]' in project 'shogun2-dao' 

Solution

Use the same Java-version for Eclipse and for executing mvn eclipse:eclipse.
If they differ, you can set the version manually on the command line like:

JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64/jre/ mvn eclipse:clean eclipse:eclipse

[marcjansen]

Yes please! A PR with such a doc change would be appreciated.

[buehner]

The doc is a bit outdated. I suggest to use Eclipse with the m2e plugin (in latest version) instead of mvn eclipse:eclipse. After a clone of the SHOGun2 repo, you can easily use the "Import existing Maven project" functionality of eclipse/m2e. This has some advantages, for example that dependencies can be resolved within the eclipse workspace.

I will expand the documentation regarding this!