I updated to use this tonight. It works fairly well. I did have one minor issue (not sure if it's flexmojos, maven, or a mistake by me).
I use a parent pom with pluginManagement for all my plugin versions. I set the flexmojos plugin to 3.3.0 in my parent pom and don't usually set it in any child modules. In my air (assembly) project I override the flexmojos plugin version and set it to 3.4-SNAPSHOT. If I build my air module by itself, everything works. If I build my full project (clean, install on the parent pom), the build fails on my air assembly module. It acts as if it's trying to use 3.3.0. I think I experienced something similar with the maven dependency plugin once, so maybe that's just the way maven works. Any opinions? Is it possible to pass the plugin different file names for descriptor.xml and sign.p12 or is using the defaults required? There have been a few times where I've observed flexmojos behaving differently depending on whether or not modules are built individually or as part of a full build using a parent project. Is that expected in some cases or should I be taking note of those situations and posting about them here? Ryan On Sep 8, 12:27 pm, Marvin Froeder <[email protected]> wrote: > Hi Folks, > I'm glad to say flexmojos is the first maven plugin with air support =D > > Sample > here:http://svn.sonatype.org/flexmojos//trunk/flexmojos-testing/flexmojos-... > > Not it is time for improvements! > Any suggestions? > > 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/ -~----------~----~----~----~------~----~------~--~---
