[MAGNOLIA-7216] Missing Dependencies When Creating Magnolia 5.6 Project From Maven Archetype Created: 05/Dec/17 Updated: 05/Apr/18 Resolved: 05/Apr/18 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Julian Nodarse | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| 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)
|
||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||
| Date of First Response: | |||||||||||||
| Description |
|
Two problems are faced when creating a new empty project with the Maven archetype using Magnolia 5.6. 1) Users have to manually add the dependency for magnolia-module-imaging version 3.4/* in order for the project to run. It won’t run straight out of project creation. 2) If you uncomment the lines for the magnolia.enterprise.releases repository in the project pom.xml (lines 105-113) you are able to run the empty magnolia instance, but when you log in, you get a “Failed to load widgetset” error. I’ve attached a screenshot of the error. Thanks |
| Comments |
| Comment by Zdenek Skodik [ 05/Apr/18 ] |
|
Re 1) using the latest archetype against Magnolia 5.6.3 (pro) doesn't require any manual steps. Re 2) to be addressed by |