| Company installation [message #696147] |
Wed, 13 July 2011 11:20  |
 Christian Opitz
Messages: 11
Registered: July 2009 |
Junior Member |
|
|
Hi everyone,
Since I don't want to already give the direction to a possible solution, I am posting my question to the Newcomers section - although I guess it is not completely a newcomer's issue 
We are working in a team with several people that should use the same Eclipse environment (including plugins and settings). To make things easier for the team members, I would like to find a good way to predefine a package that can be easily distributed to everybody. In the past I had mirrored the sites required to a local storage. Everybody extracted the base-Eclipse to his PC. I created a bookmarks.xml defining all the locations for initial plugin installations, created a policy.xml for updates and created one default-workspace everybody copied and started with.
However this is not really the ideal solution and is becoming hard to handle and update. I have read and tried several things from RCP to P2 to B3, but did not really find the best way yet.
Are there any hints from you what should be considered or where to get additional information? What would be the best approach? What is the common way to achieve this?
Some things that have to be considered:
- Same package for everybody
- Plugins from different locations are required
- Everybody uses same set of plugins
- Pre-configuration of core Eclipse (e.g. update mechanism)
- Pre-configuration of Plugins
- Updates should be possible (from local mirror only)
- No downloads from internet, only from local mirror
- Least possible effort for Eclipse users
Thank you very much in advance!
[Updated on: Wed, 13 July 2011 11:20] Report message to a moderator |
|
|
| Re: Company installation [message #696250 is a reply to message #696147] |
Wed, 13 July 2011 13:43  |
|
On 13-Jul-11 05:20, Christian Opitz wrote:
> Hi everyone,
>
> Since I don't want to already give the direction to a possible solution,
> I am posting my question to the Newcomers section - although I guess it
> is not completely a newcomer's issue :)
>
> We are working in a team with several people that should use the same
> Eclipse environment (including plugins and settings). To make things
> easier for the team members, I would like to find a good way to
> predefine a package that can be easily distributed to everybody. In the
> past I had mirrored the sites required to a local storage. Everybody
> extracted the base-Eclipse to his PC. I created a bookmarks.xml defining
> all the locations for initial plugin installations, created a policy.xml
> for updates and created one default-workspace everybody copied and
> started with.
>
> However this is not really the ideal solution and is becoming hard to
> handle and update. I have read and tried several things from RCP to P2
> to B3, but did not really find the best way yet.
>
> Are there any hints from you what should be considered or where to get
> additional information? What would be the best approach? What is the
> common way to achieve this?
>
> Some things that have to be considered:
> - Same package for everybody
> - Plugins from different locations are required
> - Everybody uses same set of plugins
> - Pre-configuration of core Eclipse (e.g. update mechanism) -
> Pre-configuration of Plugins
> - Updates should be possible (from local mirror only)
> - No downloads from internet, only from local mirror
> - Least possible effort for Eclipse users
>
> Thank you very much in advance!
There are a number of solutions to your problem.
Commercially, there is http://www.poweredbypulse.com; there is even a
free version that may or may not meet your needs.
There is an Eclipse project for doing much the same thing, but I can't
remember its name and I can't seem to find it. (Someone with a better
memory might.)
There are other utterings and pontifications on this topic like
http://sysadminsjourney.com/content/2009/12/18/share-your-eclipse-plugins-and-configurations-across-platforms.
Google is your friend. I found this link using the string "eclipse share
plug-ins".
Best of luck.
|
|
|
| Re: Company installation [message #696352 is a reply to message #696147] |
Wed, 13 July 2011 18:03 |
|
Hello
I am in charge of providing an Eclipse environment for the company I
work for and one for the development team of one our clients and we
have very similar requirements than you do.
I don't know whether our approach is the easiest or most sophisticated,
but I can assure you that it works.
We do our own distribution and provide our developers complete archive
files. So they don't have to install anything - they just unzip/untar.
This distribution is created as follows:
- download/mirroring of all required components (using b3 aggregator or
simple manual downloads)
- a python script driving the p2 director application assembles
our distribution (we create each distro for 5 platforms)
- a number of own plug-ins are used to configure things that are not
stored in the preferences. Examples are: Repo configuration for Mylyn,
XML Catalog entries, and the URLs for ETE (see below).
- configurations (VM settings) in eclipse.ini are accomplished with an
own plugin containing p2 touchpoints.
The configuration (preferences) are managed centrally and the EPF file
is kept in our SVN repo. We then use Eclipse Team Etceteras [1] - a
tool we started inhouse and that we later open sourced - to get these
centrally managed preferences into the workspaces of our developers.
The undbundling of the distribution from the preferences allows for
more frequent preference changes without the need to re-distribute
new archives.
[1] http://ete.kenai.com
Take care,
Michael
|
|
|
Powered by
FUDForum. Page generated in 0.10407 seconds
] 
Search
Help
Register
Login
Home
