On Jan 17, 2007, at 4:51 PM, Joe Bohn wrote:
Jason Dillon wrote:
I think we may want to setup some profiles to disable the minimal
assemblies by default, or at least allow the user to configure
which assemblies to build.
Since these are among our deliverables that users are dependent
upon I wouldn't want to remove them from the default build. Could
we introduce an optional parameter to skip them (similar to
skipping tests/itests)?
Not really... mvn does not include profiles from lack of properties
being set, but from existence of a property. Mvn does have some
crude support to enable a profile by default, but if you happen to
flip any other profile on then the default won't get loaded. So, for
example if you enabled to -Devn=site which will enable the site-
environment profile, then no default profiles will get loaded.
It is possible to hook up a custom plugin or script to run mvn
executions for assemblies to allow better customization, but that
gets messy.
--jason
