[ https://jira.codehaus.org/browse/MNG-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308997#comment-308997 ]
Stephan Pauxberger commented on MNG-5230: ----------------------------------------- Just to add my two cents: This would be especially useful for automated ci-builds, i.e. to exclude archives from the build, which usually take a long time to build but do not offer any value to a ci build. Right now, I use the profile axis model described in http://www.blackbuild.com/how-to-really-use-maven-profiles-without-endangering-your-karma/ using a separate profile for ci jobs (which i would continue to use, but differently). Another option would be to be able to exclude modules not only in the command line, but in a profile as well, something like: <profile> <id>ci</id> <modules> <module>!ear</module> </modules> </profile> or (perhaps better, but requiring a change of the model) <profile> <id>ci</id> <excludedModules> <excludedModule>!ear</excludedModule> </excludedModules> </profile> > Command line option to exclude modules from reactor > --------------------------------------------------- > > Key: MNG-5230 > URL: https://jira.codehaus.org/browse/MNG-5230 > Project: Maven 2 & 3 > Issue Type: New Feature > Components: Command Line > Affects Versions: 3.0.3 > Reporter: Falko Modler > > Every now and then I want to exclude one or more modules from a rather large > reactor build. > One reason for this can be: The respective module has tests that take long > time to execute and I know that I don't need to execute them. > Introducing yet another profile for this is not desirable for various reasons. > So, something like an opposite to -pl would come in handy. Let's say "-el" > for "exclude list". > Example: > {code} > root > + module a > + module a1 > + module a2 > + module b > + module b1 > + module c > {code} > Calling _mvn -el a1,c_ would build all modules execpt a1 and c. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
