Actually, after looking at the code a little bit it looks like this can
be done without needing to modify the install or deploy plugins at all.
This should just be a few lines in DefaultMavenProjectBuilder (my
favorite piece of code!).
Ralph
Ralph Goers wrote:
I've just run into the problem identified in these two issues (and in
others).
The suggestion in MNG-3267 proposes allowing the version (at a
minimum) as a property. It then proposes that the version be resolved
and the pom without properties be placed in the target directory. It
then proposes that the install and deploy plugins deploy it from
there. I don't see a response to this proposal in the issues.
So,
1. Is there some objection to this proposal? This would make life
simple for me. At the moment the release plugin does nothing to help
me as it doesn't work the way I need it to. I will address that at a
later time.
2. These are issues are flagged as 2.1. I'm not really sure why since
the proposal would be completely compatible.
Ralph
---------------------------------------------------------------------
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]
