That was my initial thought too but I double checked all dependencies that I am compiling (using mvn dependency:tree) and they are all on the same version of Flex. One exception is PureMVC but it is also marked as scope "external" on all libraries.
Something I noticed is when I turn on "keep-generated-code" Flex Compiler is creating classes for all resource bundles that are resolved even bundles that are marked "external". My fear is that these are getting compiled in to all of my libraries and conflicting with each other when they are later used with "include-libraries" which is the case with the unit tests. As soon as I get time I will build out some small scale projects and do further testing. Thanks for the help and suggestions! Lance On Apr 27, 3:26 pm, Marvin Froeder <[email protected]> wrote: > This seem to be a problem on your libraries... like something built with > flex 3.2 mixed with something built using 3.3 > > VELO > > On Mon, Apr 27, 2009 at 5:11 PM, dtornkaew <[email protected]> wrote: > > > VELO, > > > I Put "compile" and "merge" on the library-path and "internal", > > "external", "test", "rsl", "caching", "getDefaultLocale()", > > "runtimeLocales" and "compiledLocales" all on the include-libraries > > and I get the same problem. > > > I get the following error on rpc.rb.swc and datavisualization.rb.swc: > > [ERROR] /home/llinder/.m2/repository/com/adobe/flex/framework/ > > datavisualization/3.3.0.4852/datavisualization-3.3.0.4852-en_US.rb.swc > > $locale/en_US/skins.properties:[16,34] Incompatible override. > > override protected function getContent():Object > > > I also get this error for each of the standard flex resource bundles: > > [ERROR] /home/llinder/gjobs/md/data_tracking/trunk/datatracking-flex- > > project/datatracking-flex-framework/target/datatracking-flex- > > framework-1.0.1.0-SNAPSHOT.swc(en_US$collections_properties):[-1,-1] > > Incompatible override. > > > This seems like a bug with Flex Builder but I can't nail down > > specifically what is causing it. > > > For now I am going back to "internal", "test", "rsl", "caching" on the > > include-libraries and everything else on library-path :-( > > > When time permits I will put together a set of sample projects to > > duplicate the issue. In the main time if you or anyone else has any > > more thoughts I will gladly try them out! > > > Thanks! > > Lance > > > On Apr 27, 1:04 pm, Marvin Froeder <[email protected]> wrote: > > > Wow, this is a serious issue on flex compiler.... > > > I think is possible to workaround it by changing the test to include all > > > locales available.... but not sure if that is a wise decision. > > > I mean, does some see any problem on including all resource bundles > > > available into the test SWF? > > > > VELO > > > > On Mon, Apr 27, 2009 at 1:49 PM, Dtornkaew <[email protected]> wrote: > > > > > When compiling multiple SWC libraries AND marking all dependencies as > > > > scope "external" the unit tests won't compile. The Flex Compiler error > > > > complains about incompatible overrides on the generated locale > > > > classes. > > > > > This problem arises when I create 2 SWC libraries where library B > > > > depends on library A and both library A and B have locales and I mark > > > > both libraries with compileLocales property and all dependencies on > > > > library A and B are marked to scope "external". > > > > > I have been able to fix the problem by changing TestCompilerMojo to > > > > put all "external" and "test" dependencies on the library-path instead > > > > of on the include-path. When I do this everything works fine. > > > > > I am torn... I know there are problems with the Automation framework > > > > and Unit Tests if all dependencies marked "test" are not on the > > > > "include-path" but at the same time there are problems with compiling > > > > multiple dependent SWCs with compiled locales. The only way I can see > > > > to solve this problem is for more scopes such as "test-internal" and > > > > "test-merged" but this is not my decision to make... just my > > > > problem :'( > > > > > Anyone have suggestions or run into this problem before? > > > > > The reason I am using scope "external" for all dependencies on my > > > > libraries is to attempt to keep my libraries free of transient code. > > > > > Thanks, > > > > Lance --~--~---------~--~----~------------~-------~--~----~ 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://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
