Invalid systemPath allows build to continue--failing in later phase.
--------------------------------------------------------------------
Key: MNG-3288
URL: http://jira.codehaus.org/browse/MNG-3288
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.0.7
Reporter: David Siefert
Priority: Minor
Attachments: systempath-issue.zip
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.
--
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
