re why would you want to? I've been looking at http://www.nabble.com/Release-aggregating-parent-poms-td20852139.html relasing aggregating parent poms - when releasing an aggregating parent whose children have their own independent release cycles, such as the apache maven maven-plugins suite, you need to ignore the child modules. Take a look at the released versions of the maven-plugins project, the <modules> section is commented out and then uncommented back in trunk, becuase they are not releasing all the sub-modules (which are the actual plugins), I was looking for a way of selectively limiting the reactor (similar to -N) rather than commenting them out.
baerrach wrote: > > On Sat, Dec 6, 2008 at 9:40 PM, jallen <[EMAIL PROTECTED]> wrote: >> >> Anyone know of a way of excluding which projects are involved in a >> reactor >> build from the command line, i'm thinking some kind of global >> 'excludeProjects' or 'reactorProjects' option that can be used to define >> a >> subset of the reactor to be run. > > No. > > Why would you want to do that anyway? > > Maven allows you to ADD to the module set (via profiles) but not subtract. > > -- View this message in context: http://www.nabble.com/command-option-to-control-which-projects-are-in-the-reactor--tp20868969p20871687.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
