Let’s say we’re compiling artifactA, and it has one dependency, a dependency on artifactB.swc.
What I’d expect is the compiler.library-path for compiling artifactA to look like so: -compiler.library-path artifactB.swc But, if artifactB.swc has a dependency on artifactC.swc, compiling artifactA will add both B and C. -compiler.library-path artifactB.swc artifactC.swc I would like to just compile with artifactB.swc, because it has been compiled and unit tested and deployed. If artifactC.swc changes after artifactB has been compiled, I will now be getting fresh code for artifactC, and things could go wrong with artifactB. This happened to our project, it was an accident that artifactC changed, but we were counting on the stability of artifactB, and no one new artifactC changed. Compiling with Flash Builder, the only thing that's passed is artifactB, so the bug never manifested on developer machines (we compile with maven locally too, but not all the time). Anyway, I'm hoping there is a setting for this, because with lots of dependencies, this backdoor makes our software very vulnerable to human error. Thanks, Gianni -- 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/
