« Return to Thread: [VOTE] Maven 2.2.0 (Fourth Attempt)
Re: [VOTE] Maven 2.2.0 (Fourth Attempt)
by John Casey-5
::
Rate this Message:
That's a fair point. So, would you say it'd be better to reopen 3057 and
assign it to 3.x, or open a new issue that references 3057 and 4167, and
assign that to 3.x?
I lost track of the original reason 4167 was opened, which has indeed
been resolved. Apologies for not paying attention to the page title. :-)
-john
Benjamin Bentmann wrote:
> John Casey wrote:
>
>> I've backed out all version-expression transformation, including the
>> code that was added in 2.1.0-*.
>
> Yup, got that.
>
>> So, 4167 isn't fixed to my knowledge.
>
> I basically don't follow your comment on MNG-3538:
> > This issue duplicates the reports in MNG-3057 and MNG-4167
>
> To recap, we're talking about
>
> MNG-3057 - properties not expanded in generated POMs when building A/B/C
> nested projects
>
> MNG-4167 - version-expression transformation interferes with plugins
> like GPG
>
> From the descriptions, these look like two related but still different
> issues. The version-expression transformation is no longer interferring
> with the GPG Plugin (because it was entirely removed), isn't it? The GPG
> Plugin being back working with Maven 2.2.0, I consider MNG-4167 to be
> fixed in 2.2.0, matching the justification to close MGPG-14.
>
> So to me, interpolating artifact-related properties is the unresolved
> issue, not the negative side effect our initial attempt had on the GPG
> Plugin.
>
> Anyway, no biggie, just wanted to bring your attention to it, might
> simply be a language problem on my side.
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...
assign it to 3.x, or open a new issue that references 3057 and 4167, and
assign that to 3.x?
I lost track of the original reason 4167 was opened, which has indeed
been resolved. Apologies for not paying attention to the page title. :-)
-john
Benjamin Bentmann wrote:
> John Casey wrote:
>
>> I've backed out all version-expression transformation, including the
>> code that was added in 2.1.0-*.
>
> Yup, got that.
>
>> So, 4167 isn't fixed to my knowledge.
>
> I basically don't follow your comment on MNG-3538:
> > This issue duplicates the reports in MNG-3057 and MNG-4167
>
> To recap, we're talking about
>
> MNG-3057 - properties not expanded in generated POMs when building A/B/C
> nested projects
>
> MNG-4167 - version-expression transformation interferes with plugins
> like GPG
>
> From the descriptions, these look like two related but still different
> issues. The version-expression transformation is no longer interferring
> with the GPG Plugin (because it was entirely removed), isn't it? The GPG
> Plugin being back working with Maven 2.2.0, I consider MNG-4167 to be
> fixed in 2.2.0, matching the justification to close MGPG-14.
>
> So to me, interpolating artifact-related properties is the unresolved
> issue, not the negative side effect our initial attempt had on the GPG
> Plugin.
>
> Anyway, no biggie, just wanted to bring your attention to it, might
> simply be a language problem on my side.
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...
« Return to Thread: [VOTE] Maven 2.2.0 (Fourth Attempt)
| Free embeddable forum powered by Nabble | Forum Help |
