> > Unfortunately, I started the refactoring to make Flex SDK optional > yesterday and don't really want to revert everything or set up another > Eclipse workspace. It will be several days until I get Eclipse working > again, and hopefully it will make this issue go away for future Eclipse > users. >
I'm not in a hurry, so if you know what's going on, please take your time fixin' it ;-) FLEX_HOME should point to a Flex SDK, not a FlexJS/Royale SDK. ASJS_HOME > points to a FlexJS/Royale SDK. It probably has to be a Royale SDK if you > are synced up with develop branch. See env-template.properties. > Hopefully it is up to date after the renaming. > I tried all combinations of FLEX_HOME and ASJS_HOME I could think of. No variation left me with 0 errors or failures. The errors or failures changed over the variations, but none made it to 0. > Also, I did not re-use old Eclipse run configs for flex-falcon after the > rename. I built a whole new workspace against the Royale repos. It might > be that the SWC tests were never run given how I set up my run configs. > I came back in after Flex was forked, so my workspace is "royale only." I didn't even have a clone of the flex-sdk and flex-falcon repos until I tried to make it work by including them this afternoon. > IMO, we want the Royale compiler to be backward compatible as much as > possible with compiling old Flex apps. Maybe some code is still needed to > fallback from royale-config.xml to flex-config.xml. I'm pretty sure the > code already doesn't care if the tag inside a -config.xml file is > <flex-config> or <royale-config>. > I appreciate the effort, and my comments earlier were meant as constructive observations. The ant build are working, but I think that is because not all test failures cause the builds to fail. The JUnit tests in Eclipse are brutal. If not all pass, it will bug you about it ;-) Thanks, EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
