[NPMCLI-232] Vaadin 8 support in CLI create-app and create-content-type commands Created: 17/Dec/19  Updated: 22/Jan/20  Resolved: 22/Jan/20

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

Type: Task Priority: Neutral
Reporter: Martin Drápela Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLUI-4912 Power Vaadin 8-based app descriptors ... Closed
is causing NPMCLI-233 DOC: Vaadin 8 support in mgnl CLI thr... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

MGNLUI-4912 introduces the !content-type-v8.

 

!content-type-m5 prefix.

for use in mgnl 6.1 and below 

 (https://git.magnolia-cms.com/users/jsimak/repos/ui/commits/b56b1c5eff2e3c26f7875c8336892be8936e164c#magnolia-ui-framework-compatibility/src/main/java/info/magnolia/ui/framework/app/contenttypes/AppWithContentType.java)

 

This should be implemented also in the create-app and create-content-type commands of the mgnl CLI:

https://documentation.magnolia-cms.com/display/DOCS62/Magnolia+CLI+v3#MagnoliaCLIv3-create-app

https://documentation.magnolia-cms.com/display/DOCS62/Magnolia+CLI+v3#MagnoliaCLIv3-create-content-type

 

 



 Comments   
Comment by Mikaël Geljić [ 22/Jan/20 ]

Can be closed as "Nothing to do"

Content types don't change in 6.2, and the app "prototype" (a one-liner), keeps using the !content-type directive—which will simply generate apps for the new UI Framework, instead of the old one. No need to support "creating compatibility" apps, the compatibility directive is for migrating existing ones.

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