[ 
https://jira.codehaus.org/browse/MNG-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348222#comment-348222
 ] 

Michael Osipov commented on MNG-4715:
-------------------------------------

How does that happen? I do not get this with Maven 3.1.1.

> 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
>            Assignee: Jason van Zyl
>            Priority: Critical
>             Fix For: 3.2.2
>
>         Attachments: untitled.JPG
>
>
> early versions, we define modules versions with expressions, and set them to 
> the parent pom, 
> simply;
> {code:xml}
> <properties>
>               <ibb-core-cache.version>1.0.1</ibb-core-cache.version>
>               <ibb-core-util.version>1.0.1</ibb-core-util.version>
> </properties>
> {code}
> and then, we give this property to modules pom as expression , 
> {code:xml}
>       <name>ik-plug</name>
>       <packaging>jar</packaging>
>       <version>${ibb-core-util.versionn}</version>
> {code}
> but know , it gives an error you know like this,
> {noformat}
> [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
> {noformat}
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to