I'd like to provide an Eclipse update site on an internal corporate server so that we can manage the deployment of Eclipse features to our developers (as long as this is allowed by the plug-ins licence of course).
Essentially I'd like one update site where we can store the plugins and developers can connect to this as needed. We can also then deploy updates to this site so that we can keep the developers machines synchronised and ensure plugins are compatible with each other and work well together.
I couldn't find any documentation on how to do this online, though I'm sure there must be some out there. Does anyone have any pointers or can provide an overview of what is required?
A new update site can be created in Eclipse by doing the following:
site.xml
file with the "Site Manifest Editor" (the default).After following these steps the structure needed will have been created. You can then deploy this static structure onto a web server for other members of the team to access.
I posted a similar question last September on Stackoverflow.
The p2 mechanism was clearly too young with eclipse3.4.
Since then, I only found (with eclipse 3.5 Galileo):
Composing and updating custom Eclipse distros
(not tested myself, but it is supposed to be a way to define your own Eclipse distro, and their updates)
I'd suggest you to visit an existing update site and get the general structure. As far as I know you dont need any special configuration for that. The archieves are auto detected by Eclipse Update Manager...