[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-releng-dev] Manually tweaking your .classpath file
|
Why was the default severity set to
error? Since this has no effect on runtime execution of code, this
should be a compiler warning at best. Many plugins are trying to
slowly wean themselves from using non-API between "friend" plugins
but won't be ready for 3.1. I don't think we should have out of box
compiler settings that show Eclipse projects having errors.
Wassim Melhem/Toronto/IBM@IBMCA
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx
12/04/2005 12:51 PM
|
Please respond to
"Eclipse platform release engineering list." |
|
|
To
| platform-releng-dev@xxxxxxxxxxx
|
|
cc
|
|
|
Subject
| [platform-releng-dev] Manually
tweaking your .classpath file |
|
In today's build, JDT raised the default severity
level of forbidden access
restrictions to ERROR.
If your team had chosen to manually tweak their .classpath file to impose
arbitrary access restrictions on the PDE classpath container, you
might
see red X's.
Note that this is a result of your choice and PDE's classpath computation
is not a factor.
Either
1. remove these restrictions from your .classpath file as they are
arbitrary and not real (ie. they are not enforced by the runtime)
OR
2. lower the default severity level of forbidden access restrictions back
down to WARNING.
Wassim.
Wassim Melhem
(Embedded image moved to file: pic28340.gif) Wassim Melhem
Staff Software Developer, The Eclipse Project
IBM Toronto Laboratory
8200 Warden Ave, Markham, ON L6G 1C7
Internal Mail: D1/R0Q/8200/MKM PWA: 318
Phone: 905-413-2620 T/L: 969-2620 Fax: 905-413-4850
Email: wassimm@xxxxxxxxxx
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
Attachment:
pic28340.gif
Description: GIF image
