Community
Participate
Working Groups
This is probably not a UI bug, but I didn't really know which component is responsible for that. It would be *VERY* helpful if I could set the Build output folder in a Java Project to a directory in another project, but this does not seem to be supported.
Asking Core if support is in general possible.
Currently, the output folder must be defined inside its project. Having it outside might be troublesome, if the folder containing project was disappearing or something like that... We may allow this however, when considering workspace structure evolution with possibility of mapping external resources; though in that case, I would rather have the output folder locally map to a folder defined elsewhere (inside or outside the workspace). Will reconsider before 2.1
I found the following solution that works for me (it's quite a hack, though): I manually go to the .classpath file of the project and edit the classpathentry (kind "output") to be something like "../other-project/path/to/folder" and it works quite fine, but a "supported" solution would be much better and defenitely more elegant :)
Based on workspace mount point, this scenario should work. Need to double check. Also we may want to add a flag for controlling the scrubbing behavior.
The scrub flag is in for M3. Mount points (aka linked resources) will soon be made available at the platform level.
Kent - please tag as fixed once we have some test coverage
We now have tests verifying our behaviour for linked output folders from another project.
Verified.
