Page History

...

• New prototype structure with an expanded choice of prototype options. For a full description see the Prototypes in CLI v3 subpage.
• You can choose which Magnolia webapp you want to install when using the jumpstart command.
• The -V option, which used to display the version information of the installed Magnolia CLI, has been replaced with a more intuitive lower-case variant (-v). The output of the option now also displays the installed version of nodejs.
• Based on user feedback, Magnolia no longer checks for the nearest Tomcat folder when you create a light-modules folder and so the  -f (force) option has been removed from the create-light-module command.

• 
  

...

• Node v 6.10+ is required to run the CLI.
• A new option -c (--cloud) has been added to the jumpstart command. mgnl jumpstart -c downloads and sets up a Magnolia Cloud bundle. It requires enterprise Enterprise credentials to access the Magnolia Nexus repository.
• If no -p option is set when executing the jumpstart command, the magnolia.resources.dir property in the magnolia.properties file is set to a relative path by default: magnolia.resources.dir=${magnolia.home}/../../../light-modules

• When creating a light module with the mgnl create-light-module command, if you specify a path to a light modules folder that does not match the light modules root folder at the nearest Tomcat installation, you get an error. The error warns you that Magnolia cannot observe your module in the location specified. You can use the -f option if you want to force the path to an unobserved folder.

• To help us help you in case you run into an issue, the mgnl -h command now also prints out your node.js version, OS and Magnolia CLI version.
• The mgnl create-component command now generates a component dialog definition yaml file containing label options (instead of the previously used name) for i18n compliance. 

...