You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Emmanuel Venisse <em...@venisse.net> on 2007/06/12 08:23:50 UTC
Re: svn commit: r546388 - /maven/components/branches/maven-2.0.x/pom.xml
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.
Emmanuel
jvanzyl@apache.org a écrit :
> Author: jvanzyl
> Date: Mon Jun 11 23:16:16 2007
> New Revision: 546388
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=546388
> Log:
> o trying to use ${project.version} to fake out the release plugin
>
> Modified:
> maven/components/branches/maven-2.0.x/pom.xml
>
> Modified: maven/components/branches/maven-2.0.x/pom.xml
> URL: http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.x/pom.xml?view=diff&rev=546388&r1=546387&r2=546388
> ==============================================================================
> --- maven/components/branches/maven-2.0.x/pom.xml (original)
> +++ maven/components/branches/maven-2.0.x/pom.xml Mon Jun 11 23:16:16 2007
> @@ -127,7 +127,7 @@
> </dependency>
> </dependencies>
> <properties>
> - <mavenVersion>2.0.7-SNAPSHOT</mavenVersion>
> + <mavenVersion>${project.version}</mavenVersion>
> </properties>
> <dependencyManagement>
> <dependencies>
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: svn commit: r546388 - /maven/components/branches/maven-2.0.x/pom.xml
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
"Using ${project.version} has other nasty side effects doesn't it?
I'll go looking for the JIRA."
Yes it does. It causes snapshot deployments to look for dependencies with identical numbers, which is nearly impossible unless useUniqueVersion is false.
http://jira.codehaus.org/browse/MNG-2486
-----Original Message-----
From: Jason van Zyl [mailto:jason@maven.org]
Sent: Tuesday, June 12, 2007 4:07 AM
To: Maven Developers List
Subject: Re: svn commit: r546388 - /maven/components/branches/maven-2.0.x/pom.xml
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.
> Emmanuel
>
> jvanzyl@apache.org a écrit :
>> Author: jvanzyl
>> Date: Mon Jun 11 23:16:16 2007
>> New Revision: 546388
>> URL: http://svn.apache.org/viewvc?view=rev&rev=546388
>> Log:
>> o trying to use ${project.version} to fake out the release plugin
>> Modified:
>> maven/components/branches/maven-2.0.x/pom.xml
>> Modified: maven/components/branches/maven-2.0.x/pom.xml
>> URL: http://svn.apache.org/viewvc/maven/components/branches/
>> maven-2.0.x/pom.xml?view=diff&rev=546388&r1=546387&r2=546388
>> =====================================================================
>> =========
>> --- maven/components/branches/maven-2.0.x/pom.xml (original)
>> +++ maven/components/branches/maven-2.0.x/pom.xml Mon Jun 11
>> 23:16:16 2007
>> @@ -127,7 +127,7 @@
>> </dependency>
>> </dependencies>
>> <properties>
>> - <mavenVersion>2.0.7-SNAPSHOT</mavenVersion>
>> + <mavenVersion>${project.version}</mavenVersion>
>> </properties>
>> <dependencyManagement>
>> <dependencies>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: svn commit: r546388 - /maven/components/branches/maven-2.0.x/pom.xml
Posted by Jason van Zyl <ja...@maven.org>.
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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: svn commit: r546388 - /maven/components/branches/maven-2.0.x/pom.xml
Posted by Brett Porter <br...@apache.org>.
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.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: svn commit: r546388 - /maven/components/branches/maven-2.0.x/pom.xml
Posted by Jason van Zyl <ja...@maven.org>.
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.
> Emmanuel
>
> jvanzyl@apache.org a écrit :
>> Author: jvanzyl
>> Date: Mon Jun 11 23:16:16 2007
>> New Revision: 546388
>> URL: http://svn.apache.org/viewvc?view=rev&rev=546388
>> Log:
>> o trying to use ${project.version} to fake out the release plugin
>> Modified:
>> maven/components/branches/maven-2.0.x/pom.xml
>> Modified: maven/components/branches/maven-2.0.x/pom.xml
>> URL: http://svn.apache.org/viewvc/maven/components/branches/
>> maven-2.0.x/pom.xml?view=diff&rev=546388&r1=546387&r2=546388
>> =====================================================================
>> =========
>> --- maven/components/branches/maven-2.0.x/pom.xml (original)
>> +++ maven/components/branches/maven-2.0.x/pom.xml Mon Jun 11
>> 23:16:16 2007
>> @@ -127,7 +127,7 @@
>> </dependency>
>> </dependencies>
>> <properties>
>> - <mavenVersion>2.0.7-SNAPSHOT</mavenVersion>
>> + <mavenVersion>${project.version}</mavenVersion>
>> </properties>
>> <dependencyManagement>
>> <dependencies>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org