On 2/23/16, 5:24 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Ok ... so today I started having a look at the Unit tests. Turns out the >reason for them failing is quite obvious :-) >The test classes make heavy uses of those Environment Variables that I am >so unhappy with to build the paths to the swc files of the flex sdk. Most >tests I had a look at all trace back to MXMLNodeBaseTests which does the >path assembling. >As replacing a parent class isn't as easy as overriding, I would have to >adjust the MXMLNodeBaseTests class itself. Would it be ok to refactor the >build-system-dependent-code into a helper class and to have multiple >implementations of this adapter? So we could have an AntTestAdapter and a >MavenTestAdapter? The Ant one could be used per default and the maven one >could be activated via System property, which is automatically set by >Maven. > >What do you think? Fine with me, but I thought the environment variable code was in EnvProperties.java which I recently changed to try other default locations if the environment variables are not set. It would also be fine just to add other default locations that Maven will likely use. I was going to do something similar to the Ant scripts. Instead of relying on, for example, FLASHPLAYER_DEBUGGER being set, I was going to try to have the Ant script search in the Maven local repo. -Alex
