Eclipse Oomph
-
|
Due to issues with AJDT, I have to keep using Eclipse Platform 2024-09 and often have to uninstall incompatible updates (I've disabled automatic updates, but occasionally try to install something). The Revert feature had been very useful for this. 
Recently I've removed some obsolete update sites from Preferences/Install/Update/Available Software Sites and the following revert has failed with: All mentioned artifacts were still available in P2 cache. Why does Revert function need to redownload them? I thought the large cache was needed specifically to enable revert for the case when original sources were unavailable. |
Beta Was this translation helpful? Give feedback.
Answered by
merks
Dec 3, 2025
Replies: 2 comments 2 replies
-
|
Nevermind, wrong logs. I'll have to reproduce to provide actual logs. In these particular samples, at least some files were installed from local repositories, which would explan why are they missign from cache. The case I remember was complaining about other files. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Revert does in general require update sites. In an IDE not installed by Oomph the older content is quickly garbage collected. With Oomph garbage collection is manually triggered. (And of course revert is a p2 action that not implemented by Oomph.) |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Does this imply that an artifact not referenced by any current profile is deleted? Because my experience is that only profile deletion results in collection from ~/.p2/pool. Profile update does not. I've thought the reason for that is that a reference from a historic profile state still counts as a reference. |
Beta Was this translation helpful? Give feedback.
-
|
In a non-Oomph-installed installation yes, unused stuff is garbage collected, as in deleted, quite quickly. The shared bundle pool is only garbage collected when you invoke the operation for that: 
It will garbage collect based on all the current profiles, not the entire history of profiles. |
Beta Was this translation helpful? Give feedback.
Answer selected by
basilevs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In a non-Oomph-installed installation yes, unused stuff is garbage collected, as in deleted, quite quickly. The shared bundle pool is only garbage collected when you invoke the operation for that:
It will garbage collect based on all the current profiles, not the entire history of profiles.