Hacky yes... but cool you made it work! :D Well I figured out why the MavenPathResolver was not getting invoked! The problem is a class loader issue when using a different version of the Flex SDK as described here https://docs.sonatype.org/display/FLEXMOJOS/How+to+set+Flex+SDK+version
When the Flex compiler POM is added as a dependency on the Flex Mojos Plugin it ends up higher on the class loader chain and then none of the ThreadLocalToolkit wrapper stuff runs :-( My temporary fix is to add the ThreadLocalToolkit wrapper dependency above the Flex compiler POM and then all is happy. Do you think this is something that I should log a bug about or just update the Wiki page or both? Lance On Jan 14, 1:32 pm, Marvin Froeder <[email protected]> wrote: > Very hacky.... but w8 for adobe would led me no where. > > > > > > > > On Fri, Jan 14, 2011 at 5:30 PM, Dtornkaew <[email protected]> wrote: > > Thanks for pointing out the ThreadLocalToolkit! Its all starting to > > make sense :-) > > > In ThreadLocalGenerator I can see how you are using Apache BCEL to > > modify the flex2.compiler.util.ThreadLocalToolkit to make calles to > > ThreadLocalToolkitHelper... very cool! > > > Lance > > > On Jan 14, 4:20 am, Marvin Froeder <[email protected]> wrote: > > > Flexmojos defiles a custom ThreadLocalToolkit..... > >https://github.com/Flexmojos/flexmojos/tree/flexmojos-4.x/flexmojos-s... > > > > VELO > > > > On Thu, Jan 13, 2011 at 9:43 PM, Dtornkaew <[email protected]> wrote: > > > > Maybe I am just leading myself into a dead end here... > > > > > With FlexMojos 4 calls Mxmlc.mxmlc(String[] args) which intern calls > > > > CompilerAPI.usePathResolver() which sets up a new PathResolver on > > > > ThreadLocalToolkit. > > > > > The way FlexMojos 3 worked it was able to set PathResolvers on the > > > > Application class which is how the property > > > > "enableMavenResourcesResolver" seemed to work. > > > > > With FlexMojos 4 the only thing I can imaging doing is call > > > > ThreadLocalToolkit and set this but it will be cleared out by > > > > CompilerAPI.userPathResolver() :@ > > > > > Unless there is some other way I don't think we can add additional > > > > PathResolvers to the OEM compiler from FlexMojos 4. > > > > > If there are any thoughts on this I am willing to investigate more but > > > > right now there doesn't seem to be an easy solution. > > > > > 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]<flex-mojos%2Bunsubscribe@googlegrou > > > > ps.com> > > <flex-mojos%2Bunsubscribe@googlegrou ps.com> > > > > For more options, visit this group at > > > >http://groups.google.com/group/flex-mojos > > > > >http://flexmojos.sonatype.org/ > > > -- > > 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]<flex-mojos%2Bunsubscribe@googlegrou > > ps.com> > > For more options, visit this group at > >http://groups.google.com/group/flex-mojos > > >http://flexmojos.sonatype.org/ -- 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/
