[magnolia-dev] [JIRA] (NPMCLI-45) mgnl-cli.json config.outputPath and magnolia.resources.dir should be the same and correspond

[JIRA (on behalf of Christoph Meier)]

Title: Message Title

Christoph Meier created an issue   Magnolia CLI npm module / NPMCLI-45 mgnl-cli.json config.outputPath and magnolia.resources.dir should be the same and correspond Issue Type: Improvement Assignee: Unassigned Created: 11/Aug/16 5:56 PM Priority: Neutral Reporter: Christoph Meier When running the jumpstart, during execution the commands writes into magnolia.properties file(s), which is nice. When running the jumpstart command without the -p option, a light-modules folder is created in the current directory. All fine. When running the jumpstart command with, lets say the -p /Users/jdoe/dev/lightmodules magnolia.properties will contain this property: magnolia.resources.dir=/Users/jdoe/dev/lightmodules - which is fine too. But running the mgnl build command copies the npm packages (with the keyword "magnolia-light-module") into the folder which is defined in mgnl-cli.json:config.outputPath. And if outputPath and magnolia.resources.dir are not identical, something is fishy The observed directory - de facto defined in magnolia.properties and the outputPath should be the same! It should not be possible to end up in a situation where these to "variables" differ. Add Comment   This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------