Community
Participate
Working Groups
Build 20011101 Class files in source folders (assuming source folder project setup) should be treated as source and hence be visible. The problem appears in the Packages view and the JAR exporter
What are we doing in a setup where the output folder == source folder and the source folder contains additional class files. Do we show all class files. I would be suprised to see all class files. I think as long as we don't know which class file have been created we should stick to the current implementation.
Agree. I thought that it is not possible to declare a source folder as output folder.
Should be reconsidered when core supports tagging of compiler generated files
Philippe, now that we can tag compiler generated files are you thinking about only filtering those class files in the Java Model which are compiler generated. This would give use "easy" access to these class files. Then the package explorer would show them as normal resources.
Moving to Core for commenting
Sounds a good idea, however this would break the rule telling a source folder only cares about sources. Maybe we should rather support allowing to map a library folder onto it, and have library folders ignore generated files (optionally).
I'd rather vote for informing the user when this occurs (marker?) and encourage to use a library folder instead.
Kent = what about flagging those as we build ? Like we do for duplicate resources, we could have a new "ignored classfile located in source folder" warning (I'm sure you'll find a better wording for it).
The builder does not look for .class files inside a source folder unless the output folder is the same as one of the source folders... then we only see the 'extra' .class files inside the output folder if/when they're needed by the compiler. I'm not in favour of searching for additional .class files inside every source folder and everyone of its package folders. Its a waste of time. FYI: Core is investigating moving the output folder outside the project's directory structure. Changing the source/output folder separation issue now increases the complexity of the problem.
Closing, won't change
