Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] New PDE error reporting in 4.2m4

Martin, this may be caused by new PDE tooling, not 4.2...what was the environment you were using before the switch ?

Do you get the same errors when using 3.8M4 ?

Note that we only modify the org.eclipse.ui.workbench bundle (effectively) so there should be no way for us to introduce compile errors unless you are down-casting and calling internal methods.

Let be know what you discover, I'll try to get some more input from Curtis Windatt (he's on my buddy list now..;-) and post anything I find here...


From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
To: "Cross project issues (cross-project-issues-dev@xxxxxxxxxxx)" <cross-project-issues-dev@xxxxxxxxxxx>
Date: 01/19/2012 09:37 AM
Subject: [cross-project-issues-dev] New PDE error reporting in 4.2m4
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

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 ?
cross-project-issues-dev mailing list

Back to the top