On 12 Jun 07, at 1:14 AM 12 Jun 07, Brett Porter wrote:
On 12/06/2007, at 6:07 PM, Jason van Zyl wrote:
On 11 Jun 07, at 11:23 PM 11 Jun 07, Emmanuel Venisse wrote:
Jason,
if the mavenVersion property is used only in dependencies
versions, you can remove it and replace all dependencies versions
by ${project.version}. We use it in continuum and the release
plugin works fine with it.
I used this for the 2.0.6 release so I'm not sure why this isn't
working now. I also tried setting mavenVersion to $
{project.version} which also yielded the same result.
Using ${project.version} has other nasty side effects doesn't it?
I'll go looking for the JIRA.
But I would really like to release the way I did last time without
having to rewrite the POM.
Sounds like a bit of an inconsistency in release beta-6, so
probably best to figure out why it isn't pinning to alpha-5 and fix
the release bug later (I know that there was the introduction of
the properties processing in there). I'm wondering if
pluginManagement doesn't correctly apply to the command line? You
could always try mvn org.apache.maven.plugins:maven-release-plugin:
2.0-beta-5:prepare as well if really necessary.
I released 2.0.6 with beta-4 and that works fine. So that's what I'll
use for 2.0.7. Once I fix the URI thing and rollback the mess I made
from the tag.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
