Community
Participate
Working Groups
Greetings, I have been using eclipse since I first started coding professionally over 12 years ago. I've used pretty much everything imaginable since then, but keep coming back to eclipse for one reason or another. Keep up the great work! I have only one complaint and this is that the Check for Updates -> Install feature almost always fails to work, even on fresh installs. This problem is more pronounced for me since I tend to load my eclipse install with a lot of extra features, and one Software Source or another will inevitably fail to respond tossing the whole update operation out the window. Going into Eclipse Marketplace and installing each individual update one at a time, skipping any that fail, is the only way I can seem to keep my eclipse installation up to date. This is usually a daily task due to things like Groovy JDT which have rapid release cycles. If you could improve this one thing, I would be able to sell more of my peers on Eclipse and be forced into using less capable IDEs less often. Cheers and thanks for your time!
Hello Aaron, I think platform.ui is the wrong component for this issue but at the same time I'm not sure myself what is the right component to report against. It might help the error message you get from the failing Check for Updates. And maybe the list of your installed plugins. You mentioned Groovy but the problem may arise from the combination with another plugin. @Ed: do I remember correctly that you are very experienced with such installation/dependency issues? Maybe you can help here.
This is the list of open p2 issues: https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&classification=Eclipse%20Project&component=p2&list_id=19301236&order=bug_id%20DESC&product=Equinox&query_format=advanced There are many and I expect that any problem with respect to install or update is somewhere already in this list. But without a specific failure message/symptom it's impossible to say which would be the duplicate. So definitely this bug should be in p2, but if it were in p2, I would ask for specific details, i.e., stack traces from the Error log view and/or screen captures. If those details weren't forthcoming, I would return as WONTFIX...
May I request for the issue ticket's title to be updated / changed so that it reflects correctly what this issue is reporting about? Thanks.
