maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arnaud HERITIER <aherit...@gmail.com>
Subject Re: [PROPOSAL] POM Version-Expression Transformation
Date Tue, 19 May 2009 07:09:17 GMT
Thx a lot John for this good sum-up about this issue.Seing your thoughts
about how to fix it, I understand that we have few solutions.
You are talking about Maven 3.0. How will it handle this case ?
Can't we reuse something from it ?

Arnaud

On Tue, May 19, 2009 at 4:45 AM, John Casey <jdcasey@commonjava.org> wrote:

> I've been grappling with version-expression interpolation since before
> Maven 2.1.0 (See MNG-3057, MNG-4140, and now MNG-4167). It seems that doing
> this transformation within an ArtifactTransformation implementation is a
> flawed concept, since it means that plugins are using old content when they
> produce derivative files/metadata from a POM that contains version
> expressions.
>
> I've written up my thoughts on what exactly the problem is here, what I see
> as our options for solving it, and how I think we ought to proceed. You can
> find them here:
>
> http://docs.codehaus.org/display/MAVEN/Transforming+POM+Version+Expressions
>
> Please, read it over and let me know what you think. If you have a
> completely different direction you think the solution should go, I want to
> hear from you! If you have something you think I haven't considered in this
> write-up, say so. I took a shot at fixing the version-expression problem in
> 2.1.0, and opened up a pretty big bug for projects that want GPG signatures
> of their POMs. I'd rather not repeat that mistake.
>
> Thanks!
>
> -john
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
Arnaud

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message