Re: [cross-project-issues-dev] New PDE error reporting in 4.2m4

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

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.

John

"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

01/19/2012 09:36 AM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To	"Cross project issues (cross-project-issues-dev@xxxxxxxxxxx)" <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject	[cross-project-issues-dev] New PDE error reporting in 4.2m4

Hi all,
 
Updating to 4.2m4 as my SDK for development,
I’m finding myself swamped with tons of new errors such that I can’t
compile my code any more.
 
I do see some value in reporting issues
such as version constraints in require-bundle, but …
-          Some
messages do not seem appropriate to report as errors (eg exporting an “internal”
package with x-friends should not require specifying a version with the
package; or, adding additional files to the source build should not be
an error).
-          And
it should be easier to turn them from “error” to “warning” (which Preference
Page item corresponds to what error?)
 
The effort needed before I can compile
my code which has been running fine for years seems not acceptable for
me.
For instance, I’d expect a quickfix “convert
this error into a warning” with each of the new reports introduced.
 
Is this already discussed in a bug anywhere
?
What are other projects doing ?
 
Thanks,
Martin_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev