[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. |
| 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. |