CLI always generates project in the same directory (depending on template)

[tomas-langer]

I was expecting the directory to be same as Project name I entered in helidon init, but it is always the same as the template (such as bare-se)

[romain-grecourt]

What version of the CLI are you using ?

[danielkec]

Same here

kec@vulcan:~/tmp/native$ helidon version
build.date              2020-10-16 14:51:33 PDT
build.version           2.1.2
build.revision          0b672147
latest.helidon.version  2.2.1

kec@vulcan:~/tmp/native$ helidon init
Using Helidon version 2.2.1
Helidon flavor
  (1) SE 
  (2) MP 
Enter selection (Default: 1): 
Select archetype
  (1) bare | Minimal Helidon SE project suitable to start from scratch 
  (2) quickstart | Sample Helidon SE project that includes multiple REST operations 
  (3) database | Helidon SE application that uses the dbclient API with an in-memory H2 database 
Enter selection (Default: 1): 
Project name (Default: bare-se): streaming-sasl
Project groupId (Default: me.kec-helidon): 
Project artifactId (Default: bare-se): streaming-sasl
Project version (Default: 1.0-SNAPSHOT): 
Java package name (Default: me.kec.se.bare): 
Project "bare-se" already exists, generating unique name
Switch directory to /home/kec/tmp/native/bare-se-2 to use CLI

Start development loop? (Default: n): 

[fco-code-org]

I have reported the same issue to Tomas quite recently. Quite disturbing but it should be easy to fix that.

Remember that, for a customer, the first impression should be good ;-)

[barchetta]

Workaround is to use the --name option:

init --name my-project