my experience regarding this issue is that running tests with
flashbuilder is different from running them by "mvn test".
in flashbuilder4 beta2 i had to add a reference to the
ASMockClassRunner class
within my code ("-include" didn't work) to be able to run tests with
the new "Execute FlexUnit Tests" feature.
with mvn this direct code dependency wasn't necessary,
so i guess flashbuilder ignores everything you have defined as
compiler arguments and just uses some default compiler invocation... :-
(furthermore flashbuilder has the ugly characteristic to add its own provided flexunit/hamcrest libraries as project dependencies, each time you use the new wizard to create a testcase/suite or even when you execute a single test. besides of having polluted dependencies, this confuses some of our developers as there are now plenty of possible imports in auto- completion... :-( ~christoph BTW for some reasons i am still using flexmojos 3.3.0 -- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos?hl=en?hl=en http://flexmojos.sonatype.org/
