Uploaded image for project: 'Magnolia CLI'
  1. Magnolia CLI
  2. NPMCLI-45

mgnl-cli.json config.outputPath and magnolia.resources.dir should be the same and correspond

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Obsolete
    • Neutral
    • None
    • None
    • None

    Description

      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.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                cmeier Christoph Meier
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD