[NPMCLI-156] Jumpstart sets wrong light-modules directory on Windows Created: 30/Jan/18  Updated: 28/Aug/18  Resolved: 16/Feb/18

Status: Closed
Project: Magnolia CLI
Component/s: None
Affects Version/s: 2.2.0
Fix Version/s: 3.0.0, 2.2.1

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Jaroslav Simak
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 10 Pro
java version "9.0.1"
Java(TM) SE Runtime Environment (build 9.0.1+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)
node --version v8.9.4


Issue Links:
Relates
relates to NPMCLI-201 Run automated CI tests for the CLI on... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: CLI v3
Sprint: Kromeriz 134
Story Points: 2

 Description   

Following the tutorial https://documentation.magnolia-cms.com/display/DOCS56/Hello+Magnolia

Description:
Light modules created in the light-modules folder are not being loaded

Steps to reproduce:
1. run mgnl jumpstart
2. got to

{magnolia-home}

\apache-tomcat\webapps\magnoliaAuthor\WEB-INF\config\default
3. open the magnolia.properties
4. Observe the malformed path

  1. The directory to expose file system resources from
    magnolia.resources.dir=${magnolia.home}/..\..\..\light-modules

Workaround:
Change the path to:

magnolia.resources.dir=${magnolia.home}/../../../light-modules


 Comments   
Comment by Benoit Poncelet [ 01/Feb/18 ]

Exact same issue on my Win 10 Corporate PC. I have the same conclusion, the path should be updated to magnolia.resources.dir=${magnolia.home}/../../../light-modules

Comment by Christopher Zimmermann [ 01/Feb/18 ]

Please fix on 2* and 3* versions.

Generated at Mon Feb 12 04:47:04 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.