his restriction.
>
> -Original Message-
> From: John Casey [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 08, 2006 3:58 PM
> To: dev@maven.apache.org
> Subject: Re: Assembly - profile bug
>
> activeByDefault is unlikely to be affected by the assembly plugin
> its
just haven't needed the settings in the other 2
today).
The settings descriptor document makes no mention of this restriction.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 08, 2006 3:58 PM
To: dev@maven.apache.org
Subject: Re: Assembly - profile bug
on.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 08, 2006 3:58 PM
To: dev@maven.apache.org
Subject: Re: Assembly - profile bug
activeByDefault is unlikely to be affected by the assembly plugin
itself.
Also, only one profile can be activeByDefault..
activeByDefault is unlikely to be affected by the assembly plugin itself.
Also, only one profile can be activeByDefault...this really means that this
is the profile which will be activated when no others are, not that it is
active unless deactivated (we don't actually have a specific mechanism for
