c newman <[email protected]> wrote: >Just getting going with flexmojos and really liking it so far. However, >I've hit a show stopper that will force me back to Ant if I can't >figure it >out: > >I cannot seem to get the merged (or internal) dependency scope to work >for >the osmf.swc for the swc I am building. I suspect the reason is the >OSMF >swc included in the Flex SDK since I'm seeing this in the generated >config.xml in my target path: > > <external-library-path> > ><path-element>.../.m2/repository/com/adobe/flex/framework/osmf/4.5.1.21328/osmf-4.5.1.21328.swc</path-element> > </external-library-path> > >So before you say, "why would you want to do that?", here's why: > >I have a some classes in my swc that use or extend the classes in OSMF >2.0 >(which is not the version in the Flex SDK) and I don't want the users >of my >SWC to have to include the OSMF.swc for these few classes. Sure, I >could >copy and paste source into my project but that doesn't feel right. With >Ant, I just comment out the OSMF swc from my flex-config file and >use <library-path>. I can also delete the osmf.swc from my local Flex >SDK >install to ensure I'm getting the correct one compiled in. > >But I cannot seem to get the OSMF classes included (merged) into my swc >no >matter what I do. I've even tried adding the osmf swc with a fake name >and >namespace into the repository and still no luck. > >I've added the OSMF.swc for OSMF 2.0 to my local repository and in my >pom.xml the scope is ignored, it's external no matter what: > ><dependency> ><groupId>org.osmf</groupId> ><artifactId>osmf</artifactId> ><version>2.0</version> ><type>swc</type> ><scope>merged</scope> ></dependency> > > >I also tried internal just to try it, no luck. I also have a >flex-config.xml I'm using with the osmf library commented out and that >has >no effect. I cannot seem to get my OSMF parent classes included in my >swc. >Is there any way to prevent the flexmojos plugin from adding the osmf >swc >to my local repository when I build? > >Or, is it possible to have two <sourceDirectory> tags, one for my code >and >one pointing at the OSMF src locally. Or am I going to have to do a >parent/child pom setup for this, which seems annoying because I have >other >projects that I want to behave exactly as what I'm getting now, OSMF >external. > >Adding OSMF to the Flex SDK was a huge mistake by Adobe in my opinion, >it >has caused all kinds of headaches for developers. > >Thanks for any and all assistance, >- chuck > >-- >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/
You can exclude the provided osmf swc by excluding the osmf artifact from the flex-framework dependency. Look at maven docs about dependencies management. -- Simon Morvan -- 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/
