Hi Brett,
thanks for your response.
Wasn't there are mechanism in maven 2.1.x (maybe preview)
that copies pom.xml to target/pom-transformed.xml?
Yes, but it caused problems:
http://jira.codehaus.org/browse/MNG-4223
Ah. Good to know.
Is there any chance to get this into 2.2.x or
what is the real road-map for 3.x (alpha is released
but official release might still take a very long
way to got)?
If you can come up with a proposal that overcomes the issues and are willing
> to see it through it could certainly be included in 3.x.
I thought my suggestion is rather obvious. What do you expect as a "proposal".
An Issue?
I think they already exist in jira.
Or something like my last one?
http://docs.codehaus.org/display/MAVENUSER/EasyVersionMaintenance
IMHO it is some sort of a bug that
foo-2.1.7.pom is installed/deployed with
<version>${myVersion]</version>
instead of
<version>2.1.7</version>
That's almost everything about it.
For a general solution about where else in POM variables should be resolved,
there might be more to discuss. I alredy pointed some things out about this.
It might be a candidate for considering with other POM changes in 3.1...
- Brett
Regards
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
