I'm trying to share preferences with other developers in my Team using Oomph's Project Model. What I did so far:
Create a Setup Project Model using the template Simple Project
Import the current Preferences using the icon Capture Preferences
Now I have a .setup-File that contains (hopefully) my current preferences. But how do I share this file? I expect that there is some way to convince eclipse to read this file and to sync the preferences with it. I was hoping I could commit this file to SVN and eclipse would then read this file on every Startup...
Is something like this possible, and how is it done?
Related
I would like to use Eclipse in an intro programming class. Is there some way I can make some kind of preferences file or some such that I can distribute with it that would set defaults for:
which buttons are in the toolbar
which menus are enabled in the application
which context-menus are enabled
what kinds of completions are available
I'd like it to start with only completing words from the current document
that is no Java API completions or code generation or whatever
This can be done using Eclipse Preferences File. All you need to do is import preferences into your workspace.
You can also export the workspace folder itself & publish Eclipse together with a default workspace folder, which will contain all the preferences.
Then create a shortcut to start eclipse with -data <path to your workspace> parameter
I'd try the following:
Install Eclipse
Put the configuration files and workspace under version control and commit.
Configure Eclipse as required.
Check all the changes in the version control to understand what configuration files are relevant to my changes.
Continue as Zilvinas is suggesting.
Look into Eclipse Oomph. It essentially automates all the tasks that you need to do to set up a fresh dev environment.
Also of interest are Yatta profiles which do a similar thing based off Oomph.
They're pretty easy to set up and publish. Get your local eclipse working, record to a profile, publish the profile, get your students to consume said profile. We've used these in a professional environment to more easily on-board new devs!
Is there any tool or plugin for intellij that let you propagate project settings (code formatting etc) across your team ?, something like Eclipse Workspace Mechanic for eclipse
Yes, you can select File -> Export Settings... and there you can find all properties you can export.
After that you give that settings.jar to all your team members, and all they need to do is File -> Import settings... and select all properties they want to be imported.
You can find more information here.
If you want it to be done automatically, you can look at Settings repository plugin (Preferences -> Plugins). It's description you can find here.
You don't need to export/import IDE settings for that. Using Settings Repository plug-in is also an overkill for such a simple task.
Instead, configure IntelliJ IDEA to store the code style and inspection profiles inside the project, then share your project files with the team.
In Eclipse I have exported code formatting, cleanup, import orders etc to files and checked them into svn.
This is useful for my team so that they can all use the same setup.
However, I can't find a way to do the same for Compiler options. There are quite a few useful settings that aren't switched on by default and its error prone for everyone to change them manually.
I know that I can use FindBugs (and we do through CI) but the Eclipse compiler options are better integrated and faster.
The best way to share all of those settings is to use Project-specific settings. Open the Project properties and select the various sections that you want to configure (for example, Java Compiler, then select the option Enable project specific settings.
Any settings you configure this way are stored in the project in a folder named .settings. Check that folder in to source control along with the .classpath and .project files, and whenever the project is checked out Eclipse will automatically apply the settings. Workspace settings are overridden by project-specific settings, so using this technique it doesn't matter how other workspaces or users have their settings configured.
The answer of #E-Riz is perfectly correct. If you find that you need to synchronize more than the listed settings for your team members in the future, then you should also have a look at Googles workspace mechanic, which allows to automatically apply any set of preferences to a workspace and to check during each start if the local preferences are still valid for the shared setup.
I want to set up certain configurations and preferences in IBM RAD (or say eclipse) so that a big team will be able to use the set-up already done. this would reduce the inconsistencies and rework effort in the team.
Preferably I want to keep that in subversion.
Right now, when created a workspace in my personal desktop and added it to SVN, everytime my team mates check it out obviously the .metadata and other eclipse internal files change based on their input.
Is there a standard practice/process to publish a common workspace setting in RAD/Eclipse?
Thanks
There are probably 2 things that matter most when getting yourself or someone else a new workspace. Getting the preferences set up, and checking out the appropriate source code.
1a) you can set up a workspace, and then export all the preferences. That provides a eclipse preference file that can be imported into a new workspace
1b) use project specific preferences where possible, as those will get checked into your SCM
2) the projects you work on can exported to a Team Project Set File. That can be imported into a new workspace.
Check them all into a releng project in your SCM. In this context, a releng project is just a project that has all of the build information in it. Then a new workspace setup involves checkout out the releng project, and importing the PSF and the preferences file.
Or have a look at Workspace Mechanic for Eclipse: http://code.google.com/a/eclipselabs.org/p/workspacemechanic/
If you are using Websphere RAD 7.5 it allows you to export a backup of your server profile preferences. So all of that configuration for databases and classpath can be backed up. I would try deploying that to your team and see if that helps.
Right click on the server, then click Server Configuration> Backup .
Hopefully that does the trick.
I was mistaken in thinking that the user libraries I define in one workspace would be available in all and subsequently created workspaces.
So I created a new workspace to organize the myriad of projects, but alas my user-defined libraries did not get replicated in the new ws. I am seeking a way to get my user library defs from the old ws into the new ws.
Is there any good way to hack this? (I've tried researching this but have come up empty handed.)
There's an export option, at least as of Eclipse 3.5.2:
Window > Preferences > Java > Build Path > User Libraries > Export...
If that's not available, what version of Eclipse are you using? Also, what language are you working with? I'm assuming Java, but that wasn't tagged in your question.
In the same place where you define user libraries (under Preferences -> Java -> Build Path -> User Libraries), you will find import/export buttons.