Enhancement Request: Output Directory per Java Content directory

Question

I don't know if this is the right location for a feature request, but I've seen others in the forum here, so I guess I won't be reprimanded.
It would be great for our project here if we could specify a unique output directory for each source directory that we add to a project. There is a similar feature in Eclipse and we would like to get off our Eclipse crutch and this would really help us out. We have several applications, that consist of dozen or so projects each, but each project may contain anywhere from two to many (scores) of source directories. We keep each source folder's output in separate folders.
Alternatively, perhaps a way to import a dependency on a project in another application without having to actually add that project to the application would be a solution.
What we're trying to avoid is having applications with 50 or more projects to keep track out each individual output folder and avoid changing our build process to accommodate JDeveloper limitation in this area.
If the dev team doesn't see this happening, perhaps some thoughts or direction on whether this could be accomplished from our side as a plugin would be appreciated.
Cheers
-Christian

Answer 1

hi Christian
about "perhaps a way to import a dependency on a project in another application without having to actually add that project to the application would be a solution."
Maybe a scenario like this could fit (part of) your needs:
If you have two applications MyAppA and MyAppB.
The MyAppA application has a MyProjectA1 project with a MyClassA1A.java file in its source path.
The MyAppB application has a MyProjectB1 project with a MyClassB1A.java file in its source path that has a dependency on the MyClassA1A class.
You could add a Project Library to the MyProjectB1 project that has a Class Path defined as the MyAppA/MyProjectA1/classes Output Directory.
Although this approach could be of some help, one difference I see with "regular project dependencies" is that JDeveloper will not help you with building this kind of dependencies. You will have to make sure dependant class files exist, so you will have to "manually" compile the dependencies first.
success
Jan Vervecken