I should have mentioned that I have everything working the way I want now. The only thing I had to compromise on was the artifact naming described in #185 which isn't a big deal. I'll probably start using default naming for non-assembly modules anyway.
I don't know much about the different Maven versions, but if you're not able to support the newest branch it may be useful to add a warning to the build process. I know I've seen a few very good error messages with URLs for more info on a couple failed builds. Those hints for common issues probably saved me a couple hours of searching google already. Thanks for the effort that's been put into FlexMojos. They add a lot of value to Flex IMO. I might abandon the Java UI I've started for my application (which I've put tons of work into) and switch to Flex. It don't think it would even be an option without FlexMojos. Ryan On Aug 29, 4:09 pm, David Rom <[email protected]> wrote: > Is 2.2 considered production ready or is it a moving target? Should we even > be worrying about issues supporting it yet? > > I remember seeing a series of slides or something explaining the motivations > and statuses for the different branches, but I can't seem to find it > anymore. It may have just popped up in an RSS feed. I remember it made > sense at the time, but now my memory's fuzzy and I don't see any other > equivalent explanations on the ASF page (at least not front and center). > > --David --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
