IvyDE
  1. IvyDE
  2. IVYDE-326

Support for variables in the retrieve pattern

    Details

      Description

      The retrieve pattern for the classpath container appears to be strictly relative to the project.

      In Ivy/ant, it is possible to specify something like

      ${some.dir}/lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]
      

      We would like to use the same in IvyDE, e.g. utilizing Eclipse variable substitution mechanism so that you could use

      ${env_var:SOME_HOME}/lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]
      

      Doing this relative to the project e.g. with

      ../../../lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]
      

      would be too fragile as it would break as soon as a project is moved in the directory hierarchy.

        Activity

        Carsten Pfeiffer created issue -
        Carsten Pfeiffer made changes -
        Field Original Value New Value
        Description The retrieve pattern for the classpath container appears to be strictly relative to the project.

        In Ivy/ant, it is possible to specify something like
        {code}
        ${some.dir}/lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]
        {code}
        We would like to use the same in IvyDE, e.g. utilizing Eclipse variable substitution mechanism so that you could use
        ${env_var:SOME_HOME}/lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]

        Doing this relative to the project e.g. with ../../../lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]
        would be too fragile as it would break as soon as a project is moved in the directory hierarchy.
        The retrieve pattern for the classpath container appears to be strictly relative to the project.

        In Ivy/ant, it is possible to specify something like
        {code}
        ${some.dir}/lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]
        {code}
        We would like to use the same in IvyDE, e.g. utilizing Eclipse variable substitution mechanism so that you could use
        {code}
        ${env_var:SOME_HOME}/lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]
        {code}
        Doing this relative to the project e.g. with
        {code}
        ../../../lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]
        {code}
        would be too fragile as it would break as soon as a project is moved in the directory hierarchy.
        Hide
        Carsten Pfeiffer added a comment -

        Something along those lines.

        Show
        Carsten Pfeiffer added a comment - Something along those lines.
        Carsten Pfeiffer made changes -
        Carsten Pfeiffer made changes -
        Labels patch
        Hide
        Nicolas Lalevée added a comment -

        This looks good to me.
        I would need to test it a little bit though, it would need a test project (see the test folder at root the IvyDE sources).
        It would also need an update in the doc.
        I have no time right now to do it. You can beat me to do it

        Show
        Nicolas Lalevée added a comment - This looks good to me. I would need to test it a little bit though, it would need a test project (see the test folder at root the IvyDE sources). It would also need an update in the doc. I have no time right now to do it. You can beat me to do it
        Hide
        Nicolas Lalevée added a comment -

        Patch applied in trunk. I have added some buttons to help put variables and patterns.
        Thank you for your contribution.

        Show
        Nicolas Lalevée added a comment - Patch applied in trunk. I have added some buttons to help put variables and patterns. Thank you for your contribution.
        Nicolas Lalevée made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee Nicolas Lalevée [ hibou ]
        Fix Version/s trunk [ 12320552 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Nicolas Lalevée
            Reporter:
            Carsten Pfeiffer
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development