CODEWITHSUNDEEP
javaeclipsemaven-2m2eclipse
Emil Sit
Emil Sit

Reputation: 23542

How does one automate configuration of Eclipse?

A team working on a project will tend to need a common configuration of Eclipse. This includes general configuration and project specific configuration. For example, generally, everyone might wish to share indentation, installation of certain plugins (say m2eclipse, testng, egit, Spring support). Further, for a project, you might want specific plug-in configurations (e.g., for m2eclipse, setting up a custom Maven settings file, configuring extra Maven targets for eclipse build events), or a custom Eclipse target platform, or even just to set-up certain custom launchers.

Currently, my team executes a series of manual steps to try and get everything configured correctly. This is tedious, error-prone and difficult for new developers to follow. Instructions also tend to get out-dated.

To what extent can this sort of configuration be automated? How should it be done?

Upvotes: 7

Views: 4038

Answers (6)

zvikico
zvikico

Reputation: 9825

There are several solutions for sharing Eclipse Installation/Configuration and settings. For example, Pulse (has a free version). If you browse previous questions in StackOverflow, you will find many discussions regarding these issues.

I would suggest against copying the configuration and workspace folders. From my experience, it won't always work. Plus, this technique only works once. It doesn't sync later.

Update: I just recalled that there's another useful plugin to checkout: Google Workspace Mechanic.

Upvotes: 4

Alex_M
Alex_M

Reputation: 1874

i agree with "Thorbjørn Ravn Andersen" but the preferences export doesn't export all preferences, especially from additonal plugins. you should additionally als zip a working eclipse and provide it to all teammembers.

Upvotes: 1

M.J.
M.J.

Reputation: 16646

configure the eclipse at one workstation and then make a zip file or rar file for the same and pass it to others.. that will help and otherwise you can also write cmd scripts to copy the plugins and other useful stuff in to the same and these will be less error prone.

Upvotes: 2

Thorbjørn Ravn Andersen
Thorbjørn Ravn Andersen

Reputation: 75376

The simplest thing available without modifications is to have a common preferences file (Export->General->Preferences), which everybody can then load. Works the best with the same Java installations present.

It is possible to drop in plugins these days but I have not worked with it. Also it might be beneficial to create a local repository with a default package depending on all the plugins you want. Then you can just install that and it will pull in the references. A local cache might be very beneficial as some repositories are quite slow.

Upvotes: 5

Kane
Kane

Reputation: 8172

I think different parts have different ways to configure/share.

  1. installation

    The installation could be installed in the nfs as central deployment, and maintain by administrator. All team members share the installation(eclipse and other plug-ins).

  2. plug-ins preference

    The preferences of some feature could be exported a file, then imported in other environments. But it depends on the implementation of the plug-ins. For example, you can export/import key setting and jre setting.

  3. project's specific settings

    For example, the java compiler level and code format setting are stored .pref configuration file under the folder of project. You can manage them via source control tool. So those setting can share among team members.

Upvotes: 0

pablosaraiva
pablosaraiva

Reputation: 2343

Configure it once and then make copies of the configuration folder. If its not enough, copy the entire Eclipse folder.

Upvotes: 1

Related Questions