Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.run Help/Check for Updates
All Eclipse packages (inclusing those installed from RPMs) are suggested for upgrade
Only packages from the third party repos should be suggested, RPMs are upgraded in the regular RHEL/Fedora manner via yum
There are 2 parts of the problem.
1. Make sure that at the time of release we ship latest version always - This would give us at least minimal time to look good. This is plain workaround but the best that can be done in the available timeframes. Having a QE check for this would be helpful.
2. Stop shipping plugins as dropins but start using droplets so RPM installed plugins can be locked in the way the main profile is.
We can't make it for 3.1. Will try for 4.0. Roland, please consider this as push for droplets :).
Postpone for 4.1 as we failed delivering to 4.0.
At the very least we will not have droplets until DTS 5.0, so I'm bumping this bug.
verified with rh-eclipse46-eclipse-4.6.0-3.5.el7
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.