On Mon, Feb 9, 2009 at 2:22 PM, Richard Rodseth <[email protected]> wrote: > Logan, > > Could you clarify where you have your "release" profile. I've seen profiles > in settings.xml, but also in poms. > In my case we have a "master pom" that builds several libraries and an app, > but if I put the profile there, it wouldn't apply if I built an individual > library, unless there's a way to tell the master pom to only build one of > its modules.
We declare most of the release profile in our root pom, but some settings that are specific to a module we set in the pom for that module. Profiles get inherited just like other pom settings. You can always build just a single module if you want. So if you have: root --components ----libraryA ----libraryB --model ----libraryC --app Then you can build just libraryA: mvn install -f components/libraryA/pom.xml -Pmyprofile and it will inherit all the profile settings from the root and components poms. So if we have a setting in the root pom that affects all the builds, we define the profile there and modify those settings. We may redefine the profile in components pom or a library pom if the settings only apply to those modules. Does that help? 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/ -~----------~----~----~----~------~----~------~--~---
