[NPMCLI-93] Jumpstart command does not update magnolia.properties reliably Created: 31/Jan/17  Updated: 27/Mar/17  Resolved: 01/Feb/17

Status: Closed
Project: Magnolia CLI
Component/s: None
Affects Version/s: 2.2.0
Fix Version/s: 2.0

Type: Bug Priority: Blocker
Reporter: Federico Grilli Assignee: Robert Kowalski
Resolution: Fixed Votes: 0
Labels: regression
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to NPMCLI-75 Flaky testsuite: create-page aftereac... 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:
Sprint: Basel 81
Story Points: 2

 Description   

mgnl jumpstart seems to no longer modify magnolia.properties for light development in a reliable way. It looks like sometimes it "misses" some of the values.
E.g.

magnolia.resources.dir=${magnolia.home}/modules
magnolia.develop=true
magnolia.auto.update=false


 Comments   
Comment by Tomáš Gregovský [ 31/Jan/17 ]

I just did mgnl jumpstart (with 1.0.8 snaposhot) and resources dir seems changed but not magnolia.develop

result after update:

magnolia.resources.dir=/Users/tomas/Magnolia/temp/cli-test/light-modules
magnolia.develop=false
magnolia.update.auto=false
Generated at Mon Feb 12 04:46:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.