I understand completely. I just wanted to make sure the reasoning as explicitly stated.
Thanks for taking the time. > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Logan Allred > Sent: Wednesday, December 30, 2009 3:20 PM > To: [email protected] > Subject: Re: [flex-mojos] Compiling Multiple Source Files > > On Wed, Dec 30, 2009 at 11:45 AM, Lukas Bradley <[email protected]> > wrote: > > I'd also like to note that multiple source files is already supported > > by Flexmojos implicitly. If the POM author does not specify a > > sourceFile, the mojo compiles all the MXML files it finds. > > > > Personally, I'd like to see the following added to the configuration, > > with the implied functinality. > > > > <sourceFiles> > > <sourceFile file="Main.mxml" output="Main.swf" /> > > <sourceFile file="MyCSS.css" output="MySkin.swf" /> > > </sourceFiles> > > It isn't multiple source files that's the problem, it's multiple swf > output files that is the issue. One of the basic Maven principles, is > 1 artifact per module (swf or swc for Flex). The problem is that Maven > by default only knows how to archive and retrieve a single artifact > per project/module. To do more than 1 requires a bit of contortion, > and other Maven plugins will ignore the others. > > So if you create a Main.swf and a MySkin.swf, and this project becomes > a dependency in a different project, say a war project, only 1 of them > will be brought in by default. > > So the most Maven-ish way, is to have 2 projects, one for Main.swf and > 1 for MySkin.swf, and to have Main.swf depend on MySkin.swf, but have > them share source directories. > > It's basically an impedance between the Flex Builder way and the Maven > way, and Velo tends toward the Maven way because it makes the plugin > easier to manage and more compatible. > > We realize that for Flex apps that use lots of compiled css, modules, > and custom application swfs that differ only by a small amount, it is > inconvenient to have so many little projects. There's just no nice way > to make both sides happy. > > If you don't need the other swfs to be in the repo and used by other > projects, then there are ways to build lots of swfs in a single maven > project with FM, just be aware of the consequences. > > Logan > > -- > 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/ -- 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/
