Page History

...

Released in February 2018.

What has changed?

• Prototypes:
  • New prototype structure with an expanded choice of prototype options.
   
  • Prototypes allow the creation of additional custom files in any directory of the light module.
  • Prototype variants to create component or page template
  which include
  • with a JavaScript model.
  • Prototype variants to create a light module.
  • Prototypes to create blocks.
  • Prototypes to create a virtual URI mapping.
• 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.
• jumpstart
  • You can choose which Magnolia webapp you want to install when using the jumpstart command.
  • You can choose the latest SNAPSHOT of the selected webapp.
  • Jumpstart does not set wrong light-modules directory on Windows anymore.
• mgnl-cli.json no longer contains  
  • Does no longer contain the lightDevFoldersInModule property. The folder structure of a light module created with the CLI is defined in the prototypes.
  The mgnl-cli.json file now
  • Now contains the webapps property 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 more intuitive lower-case variant (-v). The output now also displays the version of Node.js installed

  .

  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.

...