Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added JIRA links to the 2.2.0 release history

...

  • 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 credentials to access the Magnolia Nexus repository. NPMCLI-138
  • 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 NPMCLI-129
  • 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. NPMCLI-103

  • 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. NPMCLI-128
  • 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. NPMCLI-105
Expand
titleClick here to see the list of issues resolved in version 2.2.0

Jira
serverMagnolia - Issue tracker
columnskey,summary,type,created,status
maximumIssues20
jqlQueryproject=NPMCLI AND fixVersion=2.2.0
serverId500b06a6-e204-3125-b989-2d75b973d05f

...