i don´t know whether its possible with mxmlc either. was hoping that you could show me a way.
tks On Mar 17, 2:59 pm, Luiz Rolim <[email protected]> wrote: > Hi all, > > Suppose i have projects a,b,c with the following dependency graph: > > A-->B (A depends on B) > A-->C > B-->C > > Project A, includes dependencies B and C as Internal, but B-->C is of > external scope. > > Suppose, A and B, depends on a class called ReflectionUtils on project > C. Then, the class name gets refactored to ReflectionUtil. > > Now, i go to project A, and fix all the compilation problems, but i don > ´t change anything on project B (which is broken by now, but, assume A > is using a released version of B). > > The question is: > > Is there anyway that during the build of project A the > compilationFailures of project B get discovered? (since it depends on > class which no longer exists "ReflectionUtils") > Or do we have to rebuild B again for that? > > Simulating the scenario above, i got build success on A. > > Looking at the swf bytecode I could note that the class > ReflectionUtils, which B depends, no longer exists into that SWF, > however the classes of projects B which uses the old ReflectionUtils > are still on the SWF. > > Same issue with method rename refactoring. > > TKS. -- 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 http://flexmojos.sonatype.org/
