[
https://jira.codehaus.org/browse/MNG-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317883#comment-317883
]
Nathaniel Mishkin commented on MNG-4715:
----------------------------------------
FWIW, my use case for using properties in specifying the <version> for a
project's component is this: I've created a project whose sole purpose in life
is to create a variant (in this case, signed) of an existing artifact that's
not mine (not produced by any of my projects). In the variant project I've
created I want to do something like this:
<project>
<properties>
<x.version>4.32</x.version>
</properties>
<dependencies>
<dependency>
<groupId>...</groupId>
<artifactId>x</artifactId>
<version>${x.version}</version>
</dependency>
</dependencies>
<groupId>...</groupId>
<artifactId>x.variant</artifactId>
<version>${x.version}</version>
...
</project>
(In real life the property definition is specified an ancestor POM.)
> version expression constant
> ---------------------------
>
> Key: MNG-4715
> URL: https://jira.codehaus.org/browse/MNG-4715
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Dependencies, POM
> Affects Versions: 3.0-alpha-6, 3.0-alpha-7, 3.0-beta-1
> Environment: eclipse linux xp
> Reporter: Faruk
> Priority: Critical
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: untitled.JPG
>
>
> early versions, we define modules versions with expressions, and set them to
> the parent pom,
> simply;
> <properties>
> <ibb-core-cache.version>1.0.1</ibb-core-cache.version>
> <ibb-core-util.version>1.0.1</ibb-core-util.version>
> </properties>
> and then, we give this property to modules pom as expression ,
> <name>ik-plug</name>
> <packaging>jar</packaging>
> <version>${ibb-core-util.versionn}</version>
> but know , it gives an error you know like this,
> "[WARNING] Some problems were encountered while building the effective model
> for ibb-parent:ibb-modules-parent:pom:1.0.0
> [WARNING] 'version' contains an expression but should be a constant. @
> ibb-parent:ibb-modules-parent:${ibb-core-jars.version},
> C:\dev\ibb\workspace\core\ibb-modules-parent\pom.xml
> "
> but I think that, this enhancement is causes wrong result,
> think that , if we have i project already developing about 3 years, this
> project has a lot of modules, and this modules have sub modules , and this
> sub modules already bound to some other modules not define in your pom, but
> your updates must be affect them, at this situation, developer want to write
> the existing version numbers with properties to parent pom, and want to
> manage them like this. at the attach file below , the close projects are
> belongs to open projects, but they are the different team developing this. I
> cant force the other developers to cache their versions, I must use this
> versions as initial step
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
