[jdt-core-dev] Changing classpath validation rules...

["Philippe Mulet/SNZ/OTI" <Philippe_Mulet@xxxxxxx>]

In bug 5943 is described a scenario where the JavaModel fails to honour a 
classpath change request because of some inconsistent validation check.


http://bugs.eclipse.org/bugs/show_bug.cgi?id=5943

1. There is a classpath validation API: JavaConventions#validateClasspath

2. When using IJavaProject#setRawClasspath, it only performs a lightweight 
check of the new
   classpath, which however did catch a scenario missed by 
JavaConventions#validateClasspath.

   The offending scenario is a library folder nested inside a source 
folder. This should be
   forbidden, but the classpath validation did not find it.


The proposed change is:

a) Make the classpath validation code stricter (include a check for this 
scenario)
b) Have IJavaProject#setRawClasspath run the full classpath validation 
check before accepting
   the classpath update.

Any concern about this change ?