vitruv-tools/updatesite

The central Vitruv Eclipse update site

updatesite's Issues

Automatic history pruning using CI actions

As we push all our builds (nightly and commits to main) to this repo, its history gets pretty large although we only need the latest nightly build and all releases. Thus, we regularly prune the history manually.
Instead of doing this manually, we should implement a CI actions script which runs like once a month and does the cleanup automatically.

Update sites include jars of dependencies

All our built update sites in the individual projects include the jars of their dependencies (i.e. edu.kit.ipd.sdq.activextendannotations_1.5.0.jar) which are then pushed to our aggregated update site.
This is not intended and bloats the update site size. The intended behaviour is that only the features of the individual project are included in the update site and dependencies are linked such that they can be resolved by Eclipse.