You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Fedor Malchikov (Jira)" <ji...@apache.org> on 2022/02/21 10:18:00 UTC

[jira] [Created] (IGNITE-16598) CLI ignores an incorrect repository passed via --repo

Fedor Malchikov  created IGNITE-16598:
-----------------------------------------

             Summary: CLI ignores an incorrect repository passed via --repo
                 Key: IGNITE-16598
                 URL: https://issues.apache.org/jira/browse/IGNITE-16598
             Project: Ignite
          Issue Type: Bug
    Affects Versions: 3.0.0-alpha4
            Reporter: Fedor Malchikov 


prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test
ls: cannot access '/home/prom1se/temp/test': No such file or directory
prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init --repo=file:~/temp/test
Creating directories... Done!
+--------------------+----------------------------------------------------------------+
| Binaries Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin    |
+--------------------+----------------------------------------------------------------+
| Work Directory     | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work   |
+--------------------+----------------------------------------------------------------+
| Config Directory   | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config |
+--------------------+----------------------------------------------------------------+
| Log Directory      | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log    |
+--------------------+----------------------------------------------------------------+

Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT...
|=====>                                                                                        |  6%^C


No errors or warnings, the cli immediately started initialization from the local maven cache.
It seems to me that this behavior is incorrect, and the utility should stop working in case of an incorrectly passed repo parameter. Otherwise, the user may get the wrong version of the product that he expects.





--
This message was sent by Atlassian Jira
(v8.20.1#820001)