Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.1.0-M1
-
Fix Version/s: None
-
Component/s: Artifacts and Repositories
-
Labels:None
-
Environment:Any
-
Complexity:Intermediate
Description
My project use system dependencies pointing to class folders.
<dependency>
<groupId>class-folder</groupId>
<artifactId>class-folder</artifactId>
<version>N</version>
<scope>system</scope>
<systemPath>C:/appli/classes</systemPath>
</dependency>
Such class folders dependencies worked fine with maven 2.0.7
They are needed by my project as it relies on a legacy application not packaged into a jar file.
Root cause is located in file DefaultArtifactResolver.java:
if ( !systemFile.isFile() )
{ throw new ArtifactNotFoundException( "System artifact: " + artifact + " is not a file: " + systemFile, artifact ); }Issue Links
- is related to
-
MNG-3288
Invalid systemPath allows build to continue--failing in later phase.
-
Patch proposal correcting issue.