Yes, why do you need something like that? There is some confusion about that... all call it Maven religion or politics. I think that mechanism is core to Maven and so it won't be going anyway, even though it provides a supported means to break this so-called rule. Definately not a bug.
I think you are safe, but even if it did disappear one day, I'm sure a tweak to your setup would yield something equally viable. BTW, from what I can tell you opted for solution 1 above: if you use the flexmojos:wrapper mojo in a war project, I really have no idea what would happen; I think solution 2 is safer in that scenario. Cheers On Dec 22, 5:29 pm, velo <[email protected]> wrote: > Well, they way you did is the only way I think will work, but still > flexmojos won't support, promote or incentive it.... > > Anyway, any problems and you are on your own =/ > > I wonder why do you need something like that. > > VELO > > On Dec 22, 12:56 pm, eprevot <[email protected]> wrote: > > > > > But when you use a classifier, maven creates 2 jars/swf/..., it breaks > > the rule 1 application per project. > > > So ? Is it going to stay that way (it's ok for me, since it allows me > > to do what I want), or is it a bug to fix some day ? > > > On Dec 22, 1:08 pm, velo <[email protected]> wrote: > > > > Well, flexmojos is meant to not build more then one application per > > > project. -- 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/
