Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 3.0-alpha-6, 3.0-alpha-7, 3.0-beta-1
    • Fix Version/s: 3.3.4
    • Component/s: Dependencies, POM
    • Labels:
      None
    • Environment:
      eclipse linux xp

      Description

      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

        Issue Links

          Activity

          Faruk created issue -
          Benjamin Bentmann made changes -
          Field Original Value New Value
          Link This issue is related to MNG-4297 [ MNG-4297 ]
          Brett Porter made changes -
          Fix Version/s Issues to be reviewed for 3.x [ 13145 ]
          Benjamin Bentmann made changes -
          Component/s Apache or Maven Parent poms [ 14457 ]
          Robert Scholte made changes -
          Description 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


          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
          Jason van Zyl made changes -
          Fix Version/s Issues to be reviewed for 3.x [ 13145 ]
          Assignee Jason van Zyl [ jason ]
          Fix Version/s 3.2.2 [ 20042 ]
          Jason van Zyl made changes -
          Fix Version/s 3.2.3 [ 20443 ]
          Fix Version/s 3.2.2 [ 20042 ]
          Jason van Zyl made changes -
          Fix Version/s 3.2.4 [ 20574 ]
          Fix Version/s 3.2.3 [ 20443 ]
          Jason van Zyl made changes -
          Fix Version/s 3.2.5 [ 20819 ]
          Fix Version/s 3.2.4 [ 20574 ]
          Jason van Zyl made changes -
          Fix Version/s 3.2.5 [ 20819 ]
          Fix Version/s 3.2.6 [ 20821 ]
          Jason van Zyl made changes -
          Fix Version/s 3.3.0 [ 21012 ]
          Fix Version/s 3.2.6 [ 20821 ]
          Jason van Zyl made changes -
          Fix Version/s 3.3.0 [ 21012 ]
          Fix Version/s 3.3.1 [ 21013 ]
          Jason van Zyl made changes -
          Fix Version/s 3.3.2 [ 21027 ]
          Fix Version/s 3.3.1 [ 21013 ]
          Mark Thomas made changes -
          Project Import Sun Apr 05 08:49:45 UTC 2015 [ 1428223785911 ]
          Mark Thomas made changes -
          Workflow jira [ 12714993 ] Default workflow, editable Closed status [ 12754637 ]
          Mark Thomas made changes -
          Project Import Sun Apr 05 21:45:26 UTC 2015 [ 1428270326204 ]
          Mark Thomas made changes -
          Workflow jira [ 12952513 ] Default workflow, editable Closed status [ 12989850 ]
          Mark Thomas made changes -
          Assignee jason lane [ jason ] Jason van Zyl [ jvanzyl ]
          Jason van Zyl made changes -
          Fix Version/s 3.3.3 [ 12332054 ]
          Fix Version/s 3.3.2 [ 12330194 ]
          Jason van Zyl made changes -
          Fix Version/s 3.3.4 [ 12332076 ]
          Fix Version/s 3.3.3 [ 12332054 ]

            People

            • Assignee:
              Jason van Zyl
              Reporter:
              Faruk
            • Votes:
              38 Vote for this issue
              Watchers:
              34 Start watching this issue

              Dates

              • Created:
                Updated:

                Development