[PAGES-288] Adding SPA dependency doesn't bring jboss dependencies Created: 08/Apr/20  Updated: 23/Aug/22

Status: Open
Project: Magnolia pages module
Component/s: None
Affects Version/s: 6.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Unresolved 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Team: AuthorX

 Description   

To reproduce:

  • add pages-app-compatibility to empty webapp
  • build and install
  • access the instance
  • 500 error due to a missing jboss library 

It might take some time to realise what the real issue is and why pages app needs jboss libraries.
The underlying problem is that pages-app-compatibility has dependency to pages-spa. Surprising but not a big issue as it's a "deprecated" artifact.
But pages-spa explicitly excludes jboss libraries.
 
Caused by https://git.magnolia-cms.com/projects/MODULES/repos/pages/pull-requests/182/diff#magnolia-spa-rendering/pom.xml


Generated at Mon Feb 12 06:17:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.