Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4A121D65.5000806@commonjava.org>
Date: Mon, 18 May 2009 22:45:57 -0400
From: John Casey <jdcasey@commonjava.org>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Maven Developers List <dev@maven.apache.org>
Subject: [PROPOSAL] POM Version-Expression Transformation
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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