[NPMCLI-61] Jumpstart should allow getting bundle without travel demo Created: 12/Jan/17  Updated: 10/Apr/17  Resolved: 10/Apr/17

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

Type: Improvement Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon NPMCLI-120 Jumpstart can download and use webapp... Closed
duplicate
is duplicated by NPMCLI-60 It should be easy to get a bundle wit... 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)
Date of First Response:

 Description   

A Dev should be able to use the CLI to start a real project.
The travel demo will not be part of a real project.
The Travel demo is hard to remove from the bundle.

One solution would be to simply add download ability of bundles without demo.

Another usecase is a partner that wants to get their developers up to speed with their own demo and perhaps their own templating kit. With the downloadJars feature, and the contentImporter they could get close to this - but the installed demo gets in the way.



 Comments   
Comment by Robert Kowalski [ 19/Jan/17 ]

From the CLI perspective this is a quick win, but not sure what is involved in extending the bundling.

fgrilli do you have an idea in which project the bundle creation happens?

Comment by Federico Grilli [ 19/Jan/17 ]

rkowalski the bundles are created in the https://git.magnolia-cms.com/projects/PLATFORM/repos/ce-packs/browse and https://git.magnolia-cms.com/projects/PLATFORM/repos/ee-packs/browse Maven projects. I don't know if you're already familiar with Maven but basically it's a dependency management and build tool. Its pom.xml is kind of the package.json equivalent. Magnolia bundles are essentially zip files containing a slightly customised Tomcat instance with a particular Magnolia flavour which depends on which modules are provided (some modules are EE only).

In the case of this issue we should create two (or possibly three, cause we have two flavours of EE licenses: standard and pro) new bundles: one CE and one or two EE without demo.
Once created and available on Nexus, it'd be indeed trivial to provide them via the CLI. However, the decision about whether to create those bundles is up to Product Management and we cannot do it without their approval (CC czimmermann). One workaround could possibly be assembling those bundles in the CLI itself by removing the travel-demo and related modules ourselves.

Comment by Robert Kowalski [ 09/Mar/17 ]

I think Jan made the suggestion some time ago to just download the war and the official tomcat release and then just apply the changes locally.

Comment by Christopher Zimmermann [ 04/Apr/17 ]

Yes - I have linked to a new ticket to do that - https://jira.magnolia-cms.com/browse/NPMCLI-120

Comment by Christopher Zimmermann [ 10/Apr/17 ]

Redundant of 120.

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