Community
Participate
Working Groups
1) create a project 'P' 2) add 'src' folder in 'P' 3) add 'src2' folder in 'src' 4) open .classpath file 5) copy the following text in .classpath <?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry kind="src" path="src"/> <classpathentry kind="src" path="src/src2"/> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/> <classpathentry kind="output" path="bin"/> </classpath> 6) release the project in a CVS repository 7) delete the project 8) check out the project There is no classpath error in the task view.
This classpath validation issue is only detected when setting a classpath, not when reading in some classpath file. It should be done there too (in mode where marker refresh is requested), in case users are editing manually their classpath file, or a 2.1 project is loaded into 2.0 client. Should fix for RC2, and also needs to be backported to 2.0 stream. If we don't fix this, then nested source folders with missing exclusion patterns are never diagnosed before the builder kicks in (and report a lot of unexpected package name given file location). Note that nested source folders (with exclusion patterns) in 2.1 are actually exactly looking as invalid nested source folders for a 2.0 client, however it will never discover this problem until he goes to the build path preference page (which could be too late in 10.000 source files scenario).
Fix is quite easy.
Released fix into it. Backported fix to 2.0.x stream, so it get issued along into a 2.0.4 delivery (if any).
Bug 32974 was introduced by this fix.
Verified.
