[MGNLEE-236] Remove magnolia-demo-project from enterprise webapp pom Created: 11/Jun/12  Updated: 11/Jun/12  Resolved: 11/Jun/12

Status: Closed
Project: Magnolia DX Core
Component/s: None
Affects Version/s: 4.4.6
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Tomas Brimor Assignee: Jan Haderka
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

Why would an enterprise webapp want or need demo content?...



 Comments   
Comment by Jan Haderka [ 11/Jun/12 ]

As http://documentation.magnolia-cms.com/usermanual4/demoprojectwebsite documentation page explains, Demo project is fully functional Magnolia project.
Enterprise webapp show cases what you can do with Magnolia using this project.
If you are building your own deployment based on Magnolia, ideally you start with empty webapp and add all modules you need (including enterprise ones in case you are an enterprise user). If you decide that you plan to use majority of the modules that are included in the Enterprise webapp, you are free to use it as a base for your deployment and add additional modules you need or remove existing ones that you don't plan to use, such as demo-project. Either way you should build the war file that you plan to release on your server.
Please see more on how to build your own webapp on http://dev.magnolia-cms.com/~gjoseph/dont-build-magnolia-build-your-projects

Comment by Tomas Brimor [ 11/Jun/12 ]

This does mean that you have to track versions on the enterprise modules yourself. Why is there no pom for an enterprise war? I thought this was what the enterprise webapp pom was for.

Comment by Jan Haderka [ 11/Jun/12 ]

As I said above, if you plan to use most of the enterprise modules, you can base your project on enterprise webapp pom directly and just exclude modules you don't want. However in that case you will also get automatically all modules that will be added to the enterprise webapp which might not be always desirable.
Building your war file on top of empty webapp gives you greater degree of control over what will be included in your final assembly.

Generated at Mon Feb 12 05:28:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.