Thanks Wayne and Wendy. I will experiment with both options - multiple pom.xmls and profiles. I'll post what I find.
-----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: June 08, 2006 2:21 PM To: Maven Users List Subject: Re: How to exclude modules from a build lifecycle? On 6/8/06, Chris Wall <[EMAIL PROTECTED]> wrote: > In a mutli-level project, is there a way to exclude modules from a > build? Our use case is that we want to minimize build lifecycle time > for developer check-ins by excluding less frequently changed modules. > For our full builds (nightly), we obviously want to include all modules. > > An example would be: Given that module A is the parent of module B > which has sub-modules 1 and 2, and the parent of module C which has > sub-modules 3 and 4, how might we exclude sub-modules 2 and sub-modules > 4 when executing the build of module A. Profiles? We (Struts) have some modules that can't be in the 'default build' because they have dependencies that aren't freely available or have incompatible licenses. So 'mvn install' will not build those modules, but 'mvn install -Pextras' will. HTH, -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
