All geek questions in one place

Enterprise Eclipse Provisioning - or - How to share standard Eclipse setup with other developers

We use Eclipse as an IDE to develop all kinds of Java / J2EE applications in our non-standard IT department for 150 people. One of the common problems that we observe is that developers download and install different versions of Eclipse and plugins based on their personal likes and dislikes.

We tried to bring some consistency to this and standardized the version and plugins that developers should use. So now the problem is how we distribute this installation to the command. We fixed the directories and shared them through a shared drive. But I'm looking for a better solution using some kind of Eclipse provisioning tool with which people can install IDEs or receive updates.

Has anyone encountered this problem? What are your solutions? How do you provide a standard Eclipse environment for developers?

I found Yoxos as a potential solution to this. Does anyone have any experience? Can p2 be used for this?

+4
source share
2 answers

You can create your own p2 composite repository and use the p2 installer to download Eclipse. Alternatively, you can use one of the commercial tools such as Yoxos, Pulse or Nexus.

+2
source

Our solution is currently non-freware based on Nexus Pro .

Since it supports p2 repositories , as well as the ability to combine multiple Eclipse update sites into a single URL, we use this last function to offer one URL for each project, each of which refers to the correct set of plugins for each project.

alt text http://img714.imageshack.us/img714/9762/mavenp2.png

+1
source

Source: https://habr.com/ru/post/1310010/

More articles:


All Articles