I currently use Google Code to host two open source Eclipse plug-in projects: Eclipse XPS and Eclipse Printers. Google Code is pretty cool. It provides a Subversion server, a wiki, download pages and an issue tracker for your project. All these functions are available through a basic - yet usable - web interface.
Unfortunately, the download pages are a little bit too basic. There is no way to set up an Eclipse update site. An Eclipse update site requires a specific directory structure but Google code does not allow the creation of subdirectories in its download area.
This means that people can not use Eclipse's built-in update manager to install your code. And more importantly, they can not use it to stay up-to-date and install the latest fixes.
Of course you could commit your update site to subversion but that really defeats the whole purpose of having a download section where each download is counted.

7 Comments
You could use a combined
Submitted by Eugene Kuleshov on
You could use a combined approach. Leave site.xml on the download page and put plugin jars into svn.
I did a test with a local
Submitted by litrik on
I did a test with a local site.xml file that points (with an absolute URL) to an existing update site on the web. The update manager finds the feature (it displays the license and such) but the installation fails.
I assume it fails because it tries to locate the plug-in relative to the site.xml file.
I'll do some more testing and report back...
Another idea would be to
Submitted by Thomas Hallgren on
Another idea would be to publish archived (zipped) sites on the download page and then publish your update site in SVN (tagged of course, so that it's stable).
Is there any new information
Submitted by François Rey on
Is there any new information on how to achieve this?
Actually looks like there is
Submitted by François Rey on
Actually looks like there is an example:
http://code.google.com/p/visualswing4eclipse/
It's already in place and
Submitted by Yadu on
It's already in place and doesn't need anything extra. You just need to ensure that you are accessing project update directory properly. Below are the examples if you are using SVN.
http://PROJECT_NAME.googlecode.com/svn/trunk/UPDATE-DIR-PATH
if code is hosted under "Eclipse Labs" follow below one
http://svn.codespot.com/a/eclipselabs.org/PROJECT_NAME/trunk/UPDATE-DIR-...
i.e.
http://svn.codespot.com/a/eclipselabs.org/restclient-tool/trunk/eclipse/...
And if you're using git?
Submitted by Lorenzo on
And if you're using git?
Add new comment