Summary: | Cannot specify java source path for resource ! | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Marc Boily <Marc.Boily> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | major | ||
Priority: | P3 | ||
Version: | 2.0.1 | ||
Target Milestone: | 2.1 M3 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Marc Boily
2002-10-31 09:24:05 EST
Can you please provide exact steps to reproduce ? I presume your source folder is on your classpath, doesn't it ? Create a project, with java and bin direcory ! java containing source code. In the classpath, try to add class folder with the same java directory ! and the problem is there ! :-) Why don't you move these in a separate folder where they would be taken into account (through a class folder) ? Source folders always implicitly ignore .class files. Because before we use JBuilder and he take the .xml files directly in java source directory ! We have a big project and the .xml file is classed with package ! In own system of source sharing only java is committed into database ! :-( it's very difficult to move into other directory for the moment ! So why did you want to add a class folder with the same Java directory to start with ? What is a class folder for you ? The closest thing I could imagine was a what we call a library folder (a folder containing .class files). Source folders will ignore all .class files, but only .class files. The .xml files buried in it will be considered and copied to the output location so they can be seen at runtime (you can enable a filter through the options if you don't mean to have them copied to the output folder). Is there still a problem? Closing, please reopen if you disagree and have more information to provide (exact steps would then be appreciated) |