Maven
  1. Maven
  2. MNG-2653

using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 version instead)

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      win xp, maven 2.0.1, eclipse plugin 0.0.3, eclipse 3.1
    • Complexity:
      Intermediate
    • Number of attachments :
      3

      Description

      My project is a ear multiproject. It has 5 modules, that have internal dependencies. For example web module needs app and type modules.

      I usually use following declaration for this kind of dependencies. Note that I'm using $

      {version} in dependency. In result I'm requesting foo-type jar of the same version as current project.

      <project>
      <modelVersion>4.0.0</modelVersion>
      <parent>
      <groupId>foo</groupId>
      <artifactId>foo</artifactId>
      <version>0.0.1-SNAPSHOT</version>
      </parent>
      <artifactId>foo-app</artifactId>

      <dependencies>
      <dependency>
      <groupId>foo</groupId>
      <artifactId>foo-type</artifactId>
      <version>${version}

      </version>
      </dependency>
      </dependencies>
      </project>

      This works from commandline, but doesn't work in eclipse plugin. I get following message:

      "Unable to download the artifact from any repository foo:foo-type-2.4.1.jar"

      Maven (or maven plugin) tries to download foo-type module in very strange version (instead 0.0.1-SNAPSHOT)!

      I've attached simple multimodule project.

      1. org.maven.ide.eclipse-MNGECLIPSE-20-patch.txt
        8 kB
        Daniel Schulz
      1. mngeclipse20-trigger.jpg
        13 kB

        Issue Links

          Activity

          Hide
          Daniel Schulz added a comment -

          problem trigger

          Show
          Daniel Schulz added a comment - problem trigger
          Hide
          Michal Stochmialek added a comment -

          Basing on Daniel's comments the issue should be reopened.

          Show
          Michal Stochmialek added a comment - Basing on Daniel's comments the issue should be reopened.
          Hide
          Eugene Kuleshov added a comment -

          Folks, please report it to the Maven Embedder component. This issue should be fixed in there and not worked around in the plugin.

          Show
          Eugene Kuleshov added a comment - Folks, please report it to the Maven Embedder component. This issue should be fixed in there and not worked around in the plugin.
          Hide
          Nathan Pruett added a comment - - edited

          This should be left as an open issue until it is fixed in Maven Embedder (MNG-2651) and the new version of Maven Embedder is included in the Eclipse plugin.

          Show
          Nathan Pruett added a comment - - edited This should be left as an open issue until it is fixed in Maven Embedder ( MNG-2651 ) and the new version of Maven Embedder is included in the Eclipse plugin.
          Hide
          Kenney Westerhof added a comment -

          I'm tempted to 'close - won't fix'.
          $

          {version}

          is evaluated to either a system prop or a -Dversion=..., so this is expected.

          However, $

          {pom.version}

          should be evaluated to the pom's <version> tag. But that's a different issue alltogether.

          Show
          Kenney Westerhof added a comment - I'm tempted to 'close - won't fix'. $ {version} is evaluated to either a system prop or a -Dversion=..., so this is expected. However, $ {pom.version} should be evaluated to the pom's <version> tag. But that's a different issue alltogether.

            People

            • Assignee:
              Kenney Westerhof
              Reporter:
              Michal Stochmialek
            • Votes:
              7 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: