Thank you Curtis. That was very helpful.
On Tue, Jan 21, 2014 at 12:02 PM, Curtis Rueden <ctrue...@wisc.edu> wrote: > Hi Todd, > > > In our multi-module project we have one module that is only used for > > development in our IDE. Is there a way to configure this project so > > that it is always excluded from package phase? > > With Eclipse, you can do something similar using profiles: > > <profiles> > <profile> > <id>eclipse</id> > <activation> > <property> > <name>m2e.version</name> > </property> > </activation> > <modules> > <module>my-eclipse-specific-module</module> > </modules> > </profile> > </profiles> > > This excludes the "my-eclipse-specific-module" module completely from the > command-line build. > > If you aren't using Eclipse, perhaps your IDE sets a similar property. > > Regards, > Curtis > > > On Tue, Jan 21, 2014 at 10:52 AM, Todd Chapman <t...@chaka.net> wrote: > > > Hello, > > > > In our multi-module project we have one module that is only used for > > development in our IDE. Is there a way to configure this project so that > it > > is always excluded from package phase? > > > > Thanks, > > > > -Todd > > >
