Wrong classes output directory when use of dependant projects

Question

Hi,
JDev 10.1.2.1 but also in previous versions.
Windows XP Prof, AMD Athlon, 1 Go Mem
I have following setup:
Projects:
DTO (data transfer objects and utility classes used in other projects)
-> dependies: none
Directory tree:
MyWorkspace\DTO\classes
MyWorkspace\DTO\src
Model (model classes)
-> dependies: DTO
Directory tree:
MyWorkspace\Model\classes
MyWorkspace\Model\src
View (JClient app)
-> dependies: DTO, Model
Directory tree:
MyWorkspace\View\classes
MyWorkspace\View\src
WebView (Struts app)
-> dependies: DTO, Model
Directory tree:
MyWorkspace\WebView\deploy
MyWorkspace\WebView\model
MyWorkspace\WebView\public_html
For some unexplained reasons sometimes (difficult to reproduce)
JDev get confused and DTO classes, sometimes Model classes are copied to the View project classes directory.
Example utility class of the DTO project:
source:
MyWorkspace\DTO\src\com\photoswing\dto\util\TextUtils.java
instead of being generated in:
MyWorkspace\DTO\classes\com\photoswing\dto\util\TextUtils.class
is found in the View claases output directory (directory tree created by JDev):
MyWorkspace\View\classes\com\photoswing\dto\util\TextUtils.class
I noticed that regularly the JDev navigator has synchronization problems and can't find the class when activating the right-click Select in Navigator action in an open source file.
This generally happens when switching from source files of different projects.
Now if you compile a source file and the navigator has a synchronization problem following warning is displayed:
Warning: The file is not part of the active project DTO.jpr, compiled class will be written to DTO.jpr output directory
When only one file gets compiled this can be repaired easely by deleting the class written in the wrong directory.
But when several files are changed and are compiled the warning is only displayed for the current source file and all classes output trees must be scanned manually.
When testing the app if I'm not wrong JDev reads from the classes directories and doesn't produce a jar file, so deleting manually the wrong classes is a valid workaround.
But what if the app gets deployed and jars are generated?
I can't imagine myself changing manually the produced jars by removing the wrong classes and what about the manifest?
Your help is requested.
Regards
Fred
PS Can't provide a TestCase => happens in complex environment only.

Answer 1

Glad to know I'm not the only one having that serious problem.
JDev by default create at least 2 different projects (model and view) so it seems to be a standard.
Working simultaneously on source files of different projects seems to the cause the trouble.
Is there somekind of patch available?
Could somebody of Oracle answer the question of the first message of this thread?
Thanks
Fred