I have two projects called mme-common-flex and mme-games-flex. Games has Common as a dependency, and both are at version 0.5.0-SNAPSHOT. Several classes in Games extend classes in Common. The Common SWC is already built and installed.
Running the Games' Maven POM from the command line works perfectly. The dependencies in the Common SWC are found, and everything runs great. However, when running "Maven install" from within Eclipse, the dependent parent classes in Common are not found. This is due to the following compiler.library-path. The first entry is for target/ classes. -compiler.library-path C:\Users\lbradley\Projects\thrust\thrust-mme \mme-common-flex\target\classes C:\Users\lbradley\.m2\repository\com \adobe\flex\framework\flex\3.3.0.4852\flex-3.3.0.4852.swc [ omitted for brevity ] >From the command line, the SWC is referenced instead: -compiler.library-path C:\Users\lbradley\.m2\repository\thrust\mme- common-flex\0.5.0-SNAPSHOT\mme-common-flex-0.5.0-SNAPSHOT.swc C:\Users \lbradley\.m2\repository\com\adobe\flex\framework\flex\3.3.0.4852\fl ex-3.3.0.4852.swc [ omitted for brevity ] I'm assuming the Maven plugin is trying to be smart, and directly reference the classes directly, since the open project is of the same version. To be sure, if I change the version number of the Common project, or close the project in Eclipse, it runs correctly, with a reference to the SWC. SO-- my question is this-- is it possible to force the build to always utilize the SWC? Many thanks. -- 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/
