So every time there's a new Eclipse release, you can look forward to finding out which of the following cases is true: The JBoss Tools aren't in the Simultaneous Release and they seem to be tightly coupled to the Eclipse version. For example, there's the Red Hat JBoss Tools which you need if want to develop on Wildfly from within Eclipse. There's also lots of JDT bugs that don't get fixed because JDT doesn't have enough developers.Īnd then there's annoyances like not being able to stop JUnit tests.Īnd then there's everything that doesn't belong to Eclipse foundation projects but that you can't do without. They produced lots of annoying popups for update sites that don't support HTTPS. The recent changes to HTTPS verification for update sites also didn't help. The error message is limited to 4 lines shown at once and anything of the sort is more like 20-40 lines long. And there's the error messages when an installation or update attempt fails: "Can't install X because of a conflicting dependency ". Additionally, it feels like the option makes the update checks take forever when you've got a few update sites no matter how fast your connection is. And then there's options like "Contact all update sites during install to find required software" which sounds sensible but mostly doesn't help when you've really got a problem. when it cannot find a solution and insists on spending minutes trying to find an alternative solution while ignoring any cancel attemps). For example, it prevents you from doing anything else (e.g. I loathe the "user experience" of the install software dialog (Help -> Install New Software. Having written that, I will spend the rest of the comment complaining about the shortcomings of the Eclipse IDE and its ecosystem.
0 kommentar(er)
