Removing "forbidden" from the default warnings is certainly scary. The access restrictions generated by PDE only create "forbidden" restrictions for packages that aren't exported by the bundle manifest. In this case, forbidden means it's guaranteed to fail to resolve the reference at runtime. Perhaps in your case someone has explicitly added "forbidden" restrictions where they shouldn't, but by turning this off you're masking potentially severe runtime errors. In fact I recommend leaving "forbidden" restrictions at the default severity: error. That will ensure the problems are cleaned up in a hurry ;)
John
| David M Williams <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 02/03/2006 02:37 AM
|
|
Just to keep all informed,
reducing the default compiler warnings helped quite a bit, but the remaining "access violations" were
not as related to non-listed packages as I thought ... were was still a lot remaining.
So .. on first blush, seems to be a bug in the PDE batch builder, but we'll see .. maybe we've specified something
wrong for our "third party jars". You can follow
https://bugs.eclipse.org/bugs/show_bug.cgi?id=130067
if you like nitty gritty.
In the mean time, I did remove "forbidden" from the default warnings.
I know this sounds scary ... but ... doesn't really change the code, and I don't think any of us could
read though 600 such warnings to figure out if they are 'real' or not.
So .. remaining warnings *are* quite meaningful, I think, indicated wasted space ... either dead code,
or "live" memory in the form of unused variables. We'll attach those during M6.
Thanks (and .. do be sure to 'check my work' for all your plugins in touched).
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
