[BLOSSOM-254] Magnolia throws Exception after Blossom Module 3.2.2-SNAPSHOT installed Created: 14/May/19  Updated: 22/Aug/19  Resolved: 22/Aug/19

Status: Closed
Project: Blossom
Component/s: None
Affects Version/s: 3.2.1
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: gügü Assignee: Robert Šiška
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Eclipse IDE, Tomcat 9, mySQL, Windows 10 Home


Attachments: Text File magnolia-blossom-module-3.2.2-SNAPSHOT.log    
Issue Links:
Relates
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:
Epic Link: Support
Sprint: SPA Editor 4
Story Points: 2

 Description   

Here is a snapshot of the file



 Comments   
Comment by Simon Lutz [ 23/May/19 ]

Hi gügü, thanks for creating the ticket and informing us about your findings. We will have a look at it and keep your informed over this channel.

Cheers,
Simon

Comment by Robert Šiška [ 19/Aug/19 ]

It appears that the Spring libraries are not found in the classpath.

In case you installed blossom module by a jar file, make sure you include also the Spring Core dependency in at least version 3.2.0 RELEASE.

Alternatively, installing the module through Maven will resolve all dependencies automatically.

Please refer to the documentation, or take a look at the sample webapp in BLOSSOM/samples repository

Generated at Sun Feb 11 23:31:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.