Our project has multiple modules that are loaded dynamically. We have a separate pom per module and it has been very successful for us. Another advantage has been that our modules can be developed fairly independently from the rest of the project.
On Sep 11, 1:49 pm, Scott Langeberg <[email protected]> wrote: > they'd definitely seem more portable, with stand-alone project / pom setups. > > we'll be looking at this shortly, so has been in back of my mind.. > > On Fri, Sep 11, 2009 at 12:15 PM, Marvin Froeder <[email protected]> wrote: > > No, no, it is completely out of scale.... I just wanna express I really > > dislike this projects with everything in the same source tree =D > > > On Fri, Sep 11, 2009 at 2:08 PM, Scott Langeberg > > <[email protected]>wrote: > > >> Wait - one hundred poms for two (hundred) modules? > > >> On Fri, Sep 11, 2009 at 11:51 AM, Marvin Froeder <[email protected]>wrote: > > >>> Flexmojos support both way, so your call. > >>> From pass experience I prefer to write one hundred poms to have two > >>> modules on the same project. But that is me. > > >>> VELO > > >>> On Fri, Sep 11, 2009 at 1:42 PM, theo2xl <[email protected]>wrote: > > >>>> I am having some trouble finding comprehensive documentation on Flex > >>>> module support. I am unclear if I should be building a new Maven > >>>> project for each module, or if I should be building modules into my > >>>> project and then using a feature of the plugin (such as moduleFiles) > >>>> to compile and use them. Just a nudge in the right direction would be > >>>> greatly appreciated. > > >>>> thanks, --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
