|Re: [cross-project-issues-dev] New PDE error reporting in 4.2m4
Thanks Eric, Dani and John.
Turns out that in fact somehow my PDE Compiler Warning Preferences were messed up to all be Error.
And what’s oddest: After a quit and restart, they were all back to the normal default settings.
Fortunately I had collected all kinds of logs as well as a stripped-down ZIP of my .metadata before the quit-and-restart.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=369182 to follow up.
Regarding Dani’s advice to fix all the errors … that would not have been possible since it were just too many. We’re talking about 10 or more different kinds
of errors, and 500 or so in total. Some of them I didn’t _want_ to fix. For others, I tried fixing them as a group but having the properly sorted group selected and applying Quickfix the tool insisted that they can’t be fixed as a group (I think I tried
some encoding errors where the tool thought that build.properties should reproduce my project encoding setting).
I haven’t filed a bug yet for making it easier to change warning levels right from the Problems view but I think this would be a good approach. Reproducing
the problem is easy by just setting all PDE > Compiler warning levels to “Error”. I’m wondering how many errors jdt.core / jdt.ui would report if that is done?
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx]
On Behalf Of John Arthorne
I suggest entering a bug against PDE and we can track it down from there. According to Curtis the default severity for missing versions is "ignore"
and this hasn't changed in Juno. I quickly checked these settings in latest 4.2 build and I also see them as "ignore". It could be something peculiar about your target platform or about how your workspace was upgraded.
Back to the top