[NPMCLI-213] Reflect product renaming on the CLI Created: 02/Apr/19  Updated: 20/Jun/19  Resolved: 11/Jun/19

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

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.25d
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLEE-569 Re-work dx-core artifact names: group... Closed
is depended upon by NPMCLI-214 DOC: Update "Magnolia CLI v3" Closed
is depended upon by NPMCLI-216 DOC: Update "How to get and adapt a b... Closed
is depended upon by NPMCLI-221 DOC: Document the release of CLI 3.1 Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Documentation update required:
Yes
Date of First Response:
Epic Link: DX Core
Sprint: Features 13
Story Points: 5

 Description   

Result:

Context

With Magnolia 6.1 - we will release the new DX core artifacts replacing enterprise standard, enterprise pro and cloud artifacts.

The mgnl CLI tools should reflect these changes.

Accepance criteria

Minimal

  • The jumpstart command offers the new DX core webapp artifacts.
  • "Help texts" are adapted accordingly (e.g. in npm-cli/lib/locales).
  • Specifying no version: latest DX Core
  • Specifying version in command: ability to chose previous versions before DX Core
  • more???

Sophisticated

  • CLI "knows" which artifacts can be downloaded for which Magnolia version and interacts gracefully with the user. 

The new artifact names

See DX Core module reshuffling



 Comments   
Comment by Christopher Zimmermann [ 06/May/19 ]

What about "cloud-dev"?

How do I work on a "cloud standard" project locally?

Relates to :https://jira.magnolia-cms.com/browse/DEV-1160

Comment by Christopher Zimmermann [ 05/Jun/19 ]

With 6.1 and dx-core, no "cloud dev" is needed - see: https://wiki.magnolia-cms.com/display/DEV/DX+Core+module+reshuffling?focusedCommentId=194483199#comment-194483199

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