Does this page need to be marked out of date since it was pulled from
2.2.0?
I was also thinking further about this - what extent would separating
the resolution metadata in the repository from the POM help?
I think this has been mentioned before - so if a 4.0.0 POM in the
current format, transformed as discussed, with minimal information
from the POM required for resolution is deployed to the current
location and the original POM (in whatever format) is pushed alongside
it as part of the release - would it overcome the main issue? I'd need
to refresh myself on the touchpoints.
- Brett
On 19/05/2009, at 12:45 PM, John Casey 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: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
