On Mon, Mar 16, 2009 at 12:38 PM, Stephen Connolly
<stephen.alan.conno...@gmail.com> wrote:
>
> so maybe what I do is add
>
> -DincludeProfiles=.....
> -DexcludeProfiles=.....
>
> Where includeProfiles can be used to add profiles that are not currently
> active into the mix (useful if you want to update the release profile for
> example)
>
> and excludeProfiles can be used to remove currently active profiles from the
> mix....
>
> I guess a side effect is that dependencies not in an "active/included
> profile" will not be picked up as an association.... which is kind of what I
> think should happen
>
Well, I was imagining the details to be slightly different.
Rather than both "includeProfiles" and "excludeProfiles", there would
just be "profiles".
If "profiles" property is present, then the user must give all
profiles in a comma separated list, using "!" for "not".
e.g.
some project has three profiles declared - "release", "snapshot", "test".
If they include the "profiles" property, then the property value must
include all three profiles in the comma separated list:
update-properties -Dprofiles=release,snapshot,!test
If they don't list all the profiles, the error message gives them the
filled-out sample command to use:
running
update-properties -Dprofiles=release,snapshot
results in
"bad parameters, blah, must look like [update-properties
-Dprofiles=release,snapshot,test]"
They can then copy and paste that template from the error message and
tweak as necessary.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
