Project dependency broken when setting output build for Java to any folder within 'build' folder
------------------------------------------------------------------------------------------------
Key: WOL-342
URL: http://objectstyle.org/jira/browse/WOL-342
Project: WOProject/WOLips
Issue Type: Bug
Components: wolips
Affects Versions: 2.0.0.* (unreleased please specify)
Environment: WOLips rev 3686
Eclipse 3.2.1
Reporter: Sebastien Sahuc
Project dependency broken when setting output build for Java to any folder within 'build' folder
For example if you have frameworkA with the output path set to FrameworkA/build/classes (instead of the default FrameworkA/bin) with a single ObjectA.
Then if you have FrameworkB that depends on frameworkA with an ObjectB that extends ObjectA, then doing a full clean ; build all will show an error that ObjectA type can't be found in frameworkA.
The main reason we want to allow such setting is to save the copy of the java classes, which is our case is significant. In this example the output folder would be FrameworkA/build/FrameworkA.framework/Content/Java
I'm attaching the simple example ready to be imported in Eclipse for testing.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://objectstyle.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
This archive was generated by hypermail 2.0.0 : Thu Dec 07 2006 - 18:09:16 EST