Option one is easy to implement on flexmojos... just need to overwrite the method that add the rsls on LibraryMojo.java.... Can you write a ticket, so I won't forgot that?
VELO On Mon, Jun 22, 2009 at 3:13 PM, Carsten Schlipf <[email protected]>wrote: > > Hi Velo, > > I was expected that lib-b could track the RSL dependency to lib-a > itself so that the application only needs to have a dependency to lib- > b, but obviously this is not the case. When I open the lib-b RSL in a > browser it does not try to load lib-a. > > So I share your opinion: Always use the 'external' scope for > libraries. However I would have expected that the 'rsl' scope would > work the same way as it is more logical that RSLs are not statically > linked to other RSLs just like you have written. > > Maybe flex-mojos could improve the situation here? > (1) In case a library is linked against another library with rsl > scope, show a warning or info message and automatically change the > scope to 'external'. > (2) Or just show a warning with the hint to switch the library to > 'external' scope so that the developers know at least that this might > not be what he wants to do. > > I would prefer the solution 1, because then you will be able to define > the dependencies in a super POM with RSL scope for libraries and > applications and it would work as expected. Solution 2 is more like it > is today: There must be a different set of the dependencies for > applications (scope:RSL) and libraries (scope:External). > > What do you think of that? > > Best regards, > Carsten > > On Jun 22, 4:34 pm, Marvin Froeder <[email protected]> wrote: > > Hrmmm, now I finally saw what you was doing and why it wasn't working... > > Well, swcs don't do RSL, and that makes sense, think if me, can you run a > > SWC? No! So, makes no sense to load content at runtime in something that > > doesn't run, there is no runtime to load content. > > > > The bug on flex compiler api here is it should throw an error if you try > to > > use a RSL to build a SWC. So to achieve what you wanna you should build > the > > libraries using external scope. BTW, I always build libraries using > > external. Makes no sense to me to include flex framework.swc into > my.swc, > > so I build all external. > > > > VELO > > > > --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
