...
Multiple different projects, or the same project in different build modes, can wrap the same swf artifact in different ways. For instance, a large development group may have multiple development integration, QA, and production/operations environments to worry about. Each may have its own unique network setup requiring varying levels of security, the presence/lack of proxies, or any of various other possibilities. This provides a relatively simple way to split out the differences in a way that can be naturally tracked by scm and configured in a familiar, accessible way.
Known Issues
- Wrapper mojo needs to communicate with the copy mojo: https://issues.sonatype.org/browse/FLEXMOJOS-185
- Build issues with 2.2.x: https://issues.sonatype.org/browse/FLEXMOJOS-184
- Eclipse 3.5 with m2e does not perform war wrapping properly (work around by executing on command-line)
- For external projects only: No project archetypes yet with original pre-packaged wrapper templates that can be cited in swf packaging (i.e. templateURI=embed:client-side-detection)
...