Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added 3.0.1 Release history entry (hidden)

...

Anchor
release-3.0.0
release-3.0.0

Hide block

3.0.1

Released on 8 June 2018.

What has changed?

Solved an issue with the `jumpstart` command caused by a regression introduced by adm-zip dependency. See details at 

Jira
serverMagnolia - Issue tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId500b06a6-e204-3125-b989-2d75b973d05f
keyNPMCLI-182

3.0.0

Released on 12 March 2018.

What has changed?

  • New command create-blocks to create blocksNPMCLI-132
  • New command create-virtual-uri to create a virtual URI mappingNPMCLI-135
  • Prototypes:
    • New prototype structure with an expanded choice of prototype options. NPMCLI-119
    • Prototypes allow the creation of additional custom files in any directory of the light module. NPMCLI-86
    • Prototype variants to create component or page templates with a JavaScript modelNPMCLI-137
    • Prototype variants to create a light module. NPMCLI-148
    • Prototypes to create blocks with the new command create-block
    • Prototypes to create a virtual URI mapping with the new command create-virtual-uri.
  • 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. NPMCLI-159
  • jumpstart:
    • You can choose which Magnolia webapp you want to install when using the jumpstart command. NPMCLI-120
    • You can choose the latest SNAPSHOT of the selected webapp. NPMCLI-144
    • Jumpstart does not set the wrong light-modules directory on Windows anymore. NPMCLI-156
    • Jumpstart stores downloaded artifacts in a separate folder to reuse them later. This also fixes a bug where -e and -c options where ignored due to already existing artifact with a generic filename. NPMCLI-100
  • mgnl-cli.json:
    • No longer contains the lightDevFoldersInModule property. The folder structure of a light module created with the CLI is defined in the prototypes.
    • The webapps property is used to define the list of possible webapps you can choose from from when running the jumpstart command.
  • The -V option, which used to display the version information of the installed Magnolia CLI, has been replaced with a lower-case option (-v). The output now also displays the version of Node.js installed. NPMCLI-133

...

Released on 18 January 2018.

What has changed?

  • 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 repositoryNPMCLI-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

...

Released on 17 March 2017.

What has changed?

  • Two new commands have been added:
    • search - helps find light modules on npm. NPMCLI-99
    • install - installs a light module from the registry into your light modules folder. NPMCLI-98
  • In the prototype dialog template, the image alt attribute uses the caption property. NPMCLI-31
  • The placeholder __lightDevModuleFolder__ for the name of the corresponding light module can be used in all prototypes files for page and component templates (in mgnl-cli-prototypes/page/* and mgnl-cli-prototypes/component). NPMCLI-84
  • The tab-completion install command, if completed successfully, also displays the files (together with their paths) to which the autocompletion script has been appended. NPMCLI-107
  • All CLI i18n messages are served from a single location ( lib/locales/ ). The messages in English are located in the en subfolder. NPMCLI-91
  • This release also fixes a few bugfixes. A complete list of the issues which have been resolved in version 2.1.0 is available via the following link:

...

Released on 27 February 2017.

What has changed?

This version contains many improvements and bugfixes. Here is an incomplete list of the new or changed features:

...