| I agree with Mickael. To reuse Doug’s words:
"Food for thoughts": If the Eclipse Foundation would support a general error reporting service similar to Mozilla, Apple, Microsoft at Eclipse that would (IMHO) be a step into the right direction. People don’t know where to report errors. But a service that lists known issues and sends notifications to registered committers - that would show how many people (and how often) run into this problem.
I’m aware of Mylyn-2-Bugzilla integration. I mean something more automated. M2E was asking for something similar. But we don’t need to get into details yet. Eclipse Foundation, would you support/host a service that collects/shares error logs (basically that’s what it is)?
Best, Marcel
could provide a default tested and certified against the release train discovery instead of an "everything goes" style discovery.
Still allow for anyone to register but have them clearly separated from certified ones.
I believe that is what netbeans does with their addons. /max (sent from my phone)
I share the vision that this post about general inconsistence in
Eclipse is actually a set of 5 "normal" bugs and that it is not that
much about the IDE in general.
However, something we can see here is that users are not able to
detect who is to blame for a bug, and blame Eclipse when they
install an external plugin which has bugs. I also had some NetBeans
users complaining against Eclipse because the m2e catalog was
populated with connectors that couldn't be installed. However, those
connectors are not Eclipse project.
For most users, anything that can be installed in Eclipse is
Eclipse. And whenever something fails in Eclipse, then they blame
Eclipse. Not sure what we can do to avoid this confusion, except
answering to such messages on forums.
_______________________________________________
ide-dev mailing list
ide-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ide-dev
ide-dev mailing list
ide-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ide-dev
|
