[jira] [Created] (IGNITE-14574) Ignite command-line tool cannot download a maven artifact from local repository on Windows platform

["Vyacheslav Koptilin (Jira)" <ji...@apache.org>]

Vyacheslav Koptilin created IGNITE-14574:
--------------------------------------------

             Summary: Ignite command-line tool cannot download a maven artifact from local repository on Windows platform
                 Key: IGNITE-14574
                 URL: https://issues.apache.org/jira/browse/IGNITE-14574
             Project: Ignite
          Issue Type: Bug
            Reporter: Vyacheslav Koptilin


Ignite command-line tool cannot download a maven artifact from local repository on Windows platform

{code:java}
PS C:\projects\ignite-3\modules\cli\target> ./ignite.exe init
Creating directories... Done!
+--------------------+-------------------------------------------------------+
| Binaries Directory | C:\projects\ignite-3\modules\cli\target\ignite-bin    |
+--------------------+-------------------------------------------------------+
| Work Directory     | C:\projects\ignite-3\modules\cli\target\ignite-work   |
+--------------------+-------------------------------------------------------+
| Config Directory   | C:\projects\ignite-3\modules\cli\target\ignite-config |
+--------------------+-------------------------------------------------------+
| Log Directory      | C:\projects\ignite-3\modules\cli\target\ignite-log    |
+--------------------+-------------------------------------------------------+

file://C:\Users\user\.m2\repository
Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT...
|>                                                                                             |  1%
[unresolved dependency: org.apache.ignite#ignite-runner;3.0.0-SNAPSHOT: not found]
{code}

It seems, that the root cause of the issue is the file URI schema:

{code:java|title:MavenArtifactResolver.java}
private Ivy ivyInstance(List<URL> repositories) {
    ...
    locBr.setRoot("file://" + pathRslvr.osHomeDirectoryPath().resolve(".m2").resolve("repository/"));
}
    ...
{code}

Perhaps, the proper fix is to change "file://" to "file:///"



--
This message was sent by Atlassian Jira
(v8.3.4#803005)