[MNG-7424] "systemPath" of dependency can't set cross system platform

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Incomplete
• Affects Version/s: 3.8.4
• Component/s: Dependencies
• Flags: Patch
• Assignee: Unassigned
• Reporter: RayLee
• Created: 25/Feb/22 16:22
• Updated: 24/Dec/22 21:38
• Resolved: 24/Dec/22 21:38

Description

In my team we work on both linux and windows .

And we use some jar library not in maven repository，so we use "system" scope to help.

"systemPath" must set a absolute path, but:

        on windows "c:/xxx" is absolute path, "/opt/xxx" not

        on linux "/opt/xxx" is absolute path, "c:/xxx" not

If we develop a private library witch has a system dependency and deploy it in a private maven repo, there will be some error when maven download dependency.

 

I write a test.jar,

when we set "/xxx/xxx/xx.jar" as "systemPath" in test.pom , on linux it works, even "xx.jar" file does not exist, the test.jar can download correctly.

but same "/xxx/xxx/xx.jar" on windows will cause a warning: "must specify an absolute path but is xxx", and will not download the test.jar. 

 

I think since maven will not require the existence of the system scope jar it depends on when downloading the test.jar, then it can friendly support set "systemPath" as cross-platform  absolute path.