Is there a way to keep the full Eclipse configuration so that no additional configuration is required?
What I mean is that I want the developer to be able to check out the project and not have to change anything so that it can be built and run. One of the problems I ran into is that the proper compiler has to be added to the build path - is there a way to do this? I understand that the actual JDK will still have to be downloaded, but could it be clear when looking at Eclipse which JDK is needed?
source to share
The build path is usually stored in a file named .classpath
under the project directory, consisting of class entries that were added to Eclipse. Among the entries in the file is the one that points to the JRE library.
There is no complete configuration that can be saved. Each configuration is saved in a separate file. Some of them are stored in the project directory. Others are stored in the root directory of your workspace. You will need to select the exact configuration you want to save.
One way to save configuration for a project and its dependencies is to use a project management tool like Maven. It can configure the required JDK to compile the project (it can even enforce this rule), required dependencies, etc.
source to share
If you have configured your project to use the runtime as the JRE library (as opposed to the "Workspace default" option), check the files .classpath
and .project
then checkout is a straightforward process. The runtime is an abstraction of the actual JRE / JDK installed on any computer / workspace; Eclipse uses this to display the physical JDK in whatever workspace it runs in.
As mentioned above, using Maven (or even better Gradle) to manage dependencies will also help - as long as every developer has m2e (Maven Integration for Eclipse) features installed in their Eclipse.
source to share