Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

I have an update site in which I'm including my features, like this:

<?xml version="1.0" encoding="UTF-8"?>
   <feature url="features/my_feature1_1.0.0.qualifier.jar" id="my_feature1" version="1.0.0.qualifier">
      <category name="My Category"/>
   </feature>
   <feature url="features/my_feature2_1.0.0.qualifier.jar" id="my_feature2" version="1.0.0.qualifier">
      <category name="My Category"/>
   </feature>
</site>
Some of the plugins included by those features have dependencies on plugins that I download from other updates sites, right now I have to manually install those update sites before installing mine, to automate this, I can download and include those dependencies to my site.xml but at the end the .zip will contain them and the size will be too big, is there a way to link an external update site to mine so it is automatically downloaded during the installation of my update site?
It seems that there is a associateSitesURL tag that provides this behavior for site.xml. That being said, it looks like site.xml has been replaced in favor of category.xml (see for instance this answer on SO) and I don't know whether this tag is still supported.
Vogella has a section about how to create one. Using a category.xml file, you can specify an additional update site by adding a repository-reference tag. For instance, add the following code to the category.xml file to reference an Orbit update site:
<repository-reference location="https://download.eclipse.org/tools/orbit/downloads/drops/R20170818183741/repository" enabled="true" />
The URL can also be specified directly from the category.xml file editor:
I failed to find any documentation on this but I used it in a side project and it seemed to work as expected.
        
Thanks for contributing an answer to Stack Overflow!
Please be sure to answer the question. Provide details and share your research!
But avoid …
Asking for help, clarification, or responding to other answers.
Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.