| NOTE: The info in this page should not be applied to updatesites that participate in a build, ie. individual component update sites like hibernate, freemarker, drools, fuse etc. should have zero associated sites. |
|---|
To create an update site which refers to upstream sites (in order to resolve upstream dependencies, eg., from a target platform update site), you can use the JBoss Tools Tycho plugin repository-utils.
Here are some examples of how to use it:
Then, when you aggregate this content into a larger update site, the above Tycho plugin will automatically remove these references.
Or you can simply exclude them to produce an update site with NO external references.
as seen in JBDS IS update site content.jar, which needs to refer to its target platform and to the upstream JBoss Tools content to enable easier installation from a single URL.
In this case, the reason for excluding any external references is twofold:
-
the JBDS IS update site contains both the JBDS IS content and its target platform, co-located in the same zip or folder, so no external references are needed
-
the JBDS IS udpate site needs to work for offline installs, so having it require upstream URLs would not work
To verify this process of inclusion and removal/replacement continues to work, simply:
-
add more associateSites to the upstream projects' site/pom.xml files, and build those sites, then
-
aggregate them into JBTIS and JBDSIS, and check for <references> in the content.jar!/content.xml files.
In the examples above, you should only see <references> in the JBTIS content.jar, as defined by the site/pom.xml file.
For the JBDSIS content.jar, there should be no <references>, as the site/pom.xml defines NO associateSites.