Maven 2 & 3

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.7
• Fix Version/s: 2.0.9
• Component/s: Dependencies
• Labels:

  None

When the system scoped dependency is specified as follows:

<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>system</scope>
<systemPath>${env.USERPROFILE}/.m2/repository/junit/junit/3.8.1/junit-3.8.2.jar</systemPath>
</dependency>

Maven fails and complains correctly (junit-3.8.2.jar is incorrect, and should be junit-3.8.1.jar).

However, when the following is used:

<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>system</scope>
<systemPath>${env.USERPROFILE}/.m2/repository/junit/junit</systemPath>
</dependency>

Maven DOES NOT COMPLAIN, the build process proceeds and fails later in the compile/testCompile build phases since the dependency is not available. You can see attached minimal project.

FYI-This was tested on a Windows XP system, I have not yet tried to replicate this issue on *nix.

1. $i18n.getText("admin.common.words.hide")

   

   systempath-issue.zip

   16/Nov/07 2:30 PM

   3 kB

   David Siefert

   1. 
      systempath-issue/pom.xml 0.7 kB
   2. 
      systempath-issue/src/main/.../maven/App.java 0.2 kB
   3. 
      systempath-issue/src/.../maven/AppTest.java 0.6 kB

   Download Zip

   $i18n.getText("admin.common.words.show")

   

   systempath-issue.zip

   16/Nov/07 2:30 PM

   3 kB

   David Siefert

• Assignee:

  Vincent Siveton

  Reporter:

  David Siefert

• Created:

  16/Nov/07 2:30 PM

  Updated:

  26/Sep/08 5:30 AM

  Resolved:

  04/Jan/08 1:20 PM