[jira] Commented: (MNG-4715) version expression constant

["Axel Fontaine (JIRA)" <ji...@codehaus.org>]

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

Axel Fontaine commented on MNG-4715:
------------------------------------

I also believe expressions should be allowed.

This enables you to decouple updating your version number from checking in to version control, which is one of the big problems with the traditional Maven release process.

This way, the only change actually commited for a new release is the code. No need to additionally modify the POM.

I've described this in detail here: http://www.axelfontaine.com/2011/01/maven-releases-on-steroids-adios.html

> version expression constant
> ---------------------------
>
>                 Key: MNG-4715
>                 URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira