Do you know any documentation about the rules of using update sites? I have managed the last 2 and a half years the update site of our company, and these are the problems I have to address:
So the question is: How many update sites should we use, and if the number is more than 1, how can I minimize the work to do to maintain the update sites?
I suggest to put everything on one web server and deploy the packages for each version of Eclipse to a different URL:
http://your.server/eclipse-3.3/site.xml
http://your.server/eclipse-3.4/site.xml
etc.
This will make it easy to deploy, to keep things apart and it will make it simple for users to see "ah, this is the one for me".
You should probably be using features and categories, segmented by eclipse version.
|
+-WSAD-2-1 Category
| |
| +- Checkstyle 3.1 Feature
| |
| `- Team Checkstyle configuration for Checkstyle 3.1
|
`-Eclipse-3-4 Category
|
+- Checkstyle 4.4 Feature
|
`- Tema Checkstyle configuration for Checkstyle 4.4
This may be isomorphic with maintaining multiple update sites, though one may consider:
However, if it isn't possible or desirable to have multiple levels of categories, then promoting the categories suggested above to separate update sites is the way forward.
This has deployment advantages, as users can be pointed to the update site for the version of IDE they're using, but is exactly what you're seeking to avoid.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With