[ARCH-72] Adapt to changes in newer BLOSSOM and test against different bundles Created: 27/Apr/20 Updated: 24/Mar/22 |
|
| Status: | Open |
| Project: | Archetypes |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Šimon Demočko | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoR: |
Empty
|
||||
| Date of First Response: | |||||
| Epic Link: | Support | ||||
| Description |
|
Currently, blossom archetype references classes that no logner exist in blossom module. Specifically e.g. **JspTemplateViewRenderer in JspRenderingConfiguration.java When using magnolia-bundle-version 6.2, there are other classes missing too. Acceptance criteria:
Developer notesOn tests: https://www.marosmars.com/blog/maven-archetype-tutorial listed out nicely testing steps. Basically just copy the existing basic folder, rename to 5.6 and modify contents to reflect new blossom version and a different bundle Issues with deployment (6.2.2)2020-08-21 11:36:04,723 ERROR lia.module.blossom.render.BlossomDispatcherServlet: Context initialization failed org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'freemarkerTemplateViewResolver' defined in class path resource [com/efigence/magnolia/config/SiteAwareFreemarkerRenderingConfiguration.class]: Unsatisfied dependency expressed through method 'freemarkerTemplateViewResolver' parameter 0; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'info.magnolia.module.blossom.view.SiteAwareFreemarkerTemplateViewRenderer' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {} |