Installing Wild Web Developer tools forces update of JustJ and Platform to latest version #1380
Description
Follow-up on #938.
Wild Web Developer uses the same updatesite for both the RCP product and the regular update site.
This is a problem, as the RCP product update site also contains transitive dependencies such as JustJ which are undesired in the 'other RCP product + install wild web as plugin' use-case.
An attempt was made in #1238 to filter out these dependencies, but this actually made things worse:
While it does result in the dependencies to be gone from the updatesite, the updatesite now contains references to the dependencies:
https://github.com/vrubezhny/wildwebdeveloper/blob/62d007dcfaf17c69cdf84f15ed8ae03952482245/repository/category.xml#L84-L85
This results
- in these referenced repositories to be added to users' 'Available Update Sites' by p2, even when the check-for-update operation is canceled:
-
Before
-
Check for updates
-
Press Cancel (!) and check update sites again:
- What's worse, these two referenced repositories are not static updatesites, but dynamic ones (
/latest). This actually causes an update of the underlying Platform and JustJ to potentially unwanted, newer versions.
I think using <repository-reference> in category.xml is a bad idea and should be removed.
Instead, the update-site should be split in two: one for the actual RCP product including the platform and JustJ dependencies, and one for the pure wild web developer features.