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@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
