Community
Participate
Working Groups
20021216 1. create new project 2. source folder on project 3. set the source folder's output folder also to the project src-entry: /proj1 output folder: /proj1 default output location: /proj/bin 4. ok 5. reopen the build paths dialog: source folder's output location is null setRawClasspath contains the output folder path. A getRawClasspath just following still contains it, but when reopening the wizard, the getRawClasspath has a 'null' value for the output folder.
Martin, isn't it a dup of bug 28463?
.classpath file looks fine. Sounds like a dup of UI bug.
I fixed bug 28463, but then I saw this problem. the created .classfile is <?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry excluding="src/" kind="src" output="" path=""/> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/> <classpathentry kind="output" path="bin"/> </classpath> Shouldn't the output be "proj", or is it also a project relative path? If it is, I guess the problem is to know if "" means 'project' or 'no output folder set'
It is a project relative path. Null should be answered when no output is used. Need to double check. Not critical.
When reading the .classpath file, we used to consider that the "output" attribute if empty was equivalent to no attribute. Fixed ClasspathEntry.elementDecode to check if the attribute exists instead. Added ClasspathTests.testReadEmptyCustomOutput().
Verified.
