Having a bit of a problem,
Due to the source-control set-up we use, each bug/enhancement is worked on in a new branch. This is fine, but when in Eclipse, we need to set-up a new project for every branch.
Is there any way of easily setting up default preferences for a project, or importing/exporting project preferences within Eclipse?
Thanks,
Stuart
One possible solution would be to store those common preferences at the workspace level for Eclipse (see Manage your Eclipse environment article)
The downside of having multiple workspaces is the need to share development preferences among them.
Since preferences are persisted on a workspace basis within Eclipse, you have to export your workspace preferences and import them to your desired workspaces (File > Export > Preferences).
Even if you stay in the same workspace (with several projects), you can share common settings with other developers by exporting those workspace preferences.
As mentioned by Fabian, the project specific settings are in .classpath and .project, but he left out .settings:
.settings are for IDE project-specific settings like compiler warnings and so on.
It you want to share project-specific IDE-related settings, just copy the .settings directory from project directory to project directory.
Tips: copy your project launcher (created by default in <workspace>\.metadata\.plugins\org.eclipse.debug.core\.launches) into your .settings directory: that way, you will also share your custom project launchers.
The above methods might work in some settings but do not address the problem of exporting a single project from your workspace including its properties for use by another person.
One way of doing this is to export the project folder as a zip archive as described above but also save the following file from your workspace: .metadata/.plugins/org.eclipse.core.resources/.projects/MYPROJECT/.indexes/properties.index where MYPROJECT is your project name.
If you then import the project as a new project in a different workspace you can afterwards copy this file into your new workspace metadata and you will have the original project properties.
The project-specific settings (contrary to the already mentioned workspace-specific settings) are stored in two hidden files in the project: .classpath and .project, which you might be able to reuse to setup your projects.
