Details
-
Task
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
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:
- Need to be decided, but preliminarily probably adapting to upstream changes.
- Write new archetype test for 6.2 and possibly other versions, leaving 5.6 test in place (if 5.6 is still supported, otherwise the lowest supported one)
Developer notes
On 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: {}
Checklists
Acceptance criteria