ROTECTED]> wrote:
> related to MNG-1701 ?
>
>
>
> On Fri, Feb 22, 2008 at 1:15 PM, Ryan Ovrevik <[EMAIL PROTECTED]> wrote:
> > Thanks! You reiterated my thoughts almost exactly.
> >
> > Forcing executions into arbitrary adjacent phases will work
s you show) without POM syntax changes.
>
> But for now it seems to me that using different phases is your best
> solution..and hoping that there are suitable phases in the lifecycle
> available to be used. In your case, are pre-integration-test and
> post-integration-test suita
21, 2008 at 11:00 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> Put multiple blocks inside the . You would
> probably need to use two phases though.
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Ryan Ovrevik
>
> On Feb 20, 2008, at 11:42 PM, Brian E. Fox wrote:
>
>> Yep, I think this is related to it only picking the first version it
>> comes across, regardless of future version declarations.
>>
>> -----Original Message-
>> From: [EMAIL PROTECTED] [mailto:[EMA
specified group and plugin id
along with a matching execution id. The problem appears to be that the
iteration is stopped at the matching group and plugin id even if the
execution id does not match. This results in all future plugin
definitions not having the opportunity for consideration.
Th
