[ https://issues.apache.org/jira/browse/IGNITE-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vyacheslav Koptilin updated IGNITE-16598: ----------------------------------------- Description: 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. was: 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. > 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 > Priority: Critical > Labels: ignite-3, ignite-3-cli-tool > > 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)