For example, having only 2 fixed updates a year makes it impossible to provide an update shortly after a new version of Java.Furthermore, bugs can be present in releases despite all the testing, and would linger for months in the recommended Eclipse version, ready to be fixed only in the the next big update.The advantages are somewhat obvious: thanks to a fixed deadline, users know when to expect changes and get a version that is thouroughly tested by a large community.The disadvantage of having a simultaneous release is the lack of flexibility in the critical updates.In addition, optional features or plugins are installed aggressively - see Do not use the Eclipse Software Update option to install new versions of features and plugins that are located in IBM Eclipse based packages. You must use Installation Manager to update IBM Eclipse based packages to a newer version. It provides new buttons to stage and unstage files (selected one or all), as well as to sort the unstaged changes.
These newer version might conflict with the Installation Manager based Eclipse packages.
You then use the Eclipse Software Updates option to install third party software for these packages.
When you use Installation Manager to update or rollback a package, a failure occurs. Third party Eclipse features or plugins are installed using Software Updates that take precedence over the features or plugins installed using Installation Manager. Installation Manager modifies the file and then uses the p2 reconciler to synchronize the results.
If issues still occur with an update or rollback of a package installed by Installation Manager, uninstall the third party software.
Installing uncategorized features can cause issue to occur during an update or rollback.
To work around this issue, disable the Eclipse update sites before you install third party software.