Summary: | Classpath Entry: Output folder can not be set to project | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Martin Aeschlimann <martinae> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.1 | ||
Target Milestone: | 2.1 M5 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Martin Aeschlimann
2002-12-17 11:35:18 EST
.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. |