Set Plugin and Feature file freely
Basically, if you put a plugin and feature jar files into your update-site, you must follow a rule defined by a specification of Eclipse update-site. Its rule is the creating a site.xml file, putting the plugin jar file into a sub directory named “plugins” and putting the feature jar file into a sub directory named “features”. When an user accesses to this update-site and install your plugin, Eclipse can find these files by the rule.
However, if you want to create your update-site, you wil not be able to create these subdirectories because of some reasons. Then, you will think that you want to set these files freely.
In this case, you can use a <archive> tag in your site.xml file. By specifying the tag, your update-site allows you to put your plugin jar file to any place. Of course, your feature jar file ca be set to any place, because you can specify the place by writing URL.
...
When your feature has your plugin named “jp.eisbahn.foo”, Eclipse will attempt to find the plugin from the sub directory “plugins”. Then, a path of your plugin jar file is “plugins/jp.eisbahn.foo_1.0.0.jar” (ex. the version number is 1.0.0). So, you can replace the path by using <archive> tag to any URL. In the case above, the path is replaced to “http://www.eisbahn.jp/any/foo-plugin.jar”.
This technic was used by OSDE’s update-site. Please see the site.xml file:
http://opensocial-development-environment.googlecode.com/svn/update-site-candidate/site.xml



