[MGNLUI-4285] Widgetset dependencies should be marked as provided Created: 06/Sep/17  Updated: 16/Oct/17  Resolved: 12/Oct/17

Status: Closed
Project: Magnolia UI
Component/s: widgetset
Affects Version/s: 5.5.6
Fix Version/s: 5.4.14, 5.5.7, 5.6

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
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:
Sprint: Saigon 117

 Description   

magnolia-vaadin-widgetset 5.5.6 is dependent on pages-editor-widget-5.5.5
while widgetset-pro 5.5.6 is dependent on pages-editor-widget-5.5.6

this creates a situation where both versions end up in the libs folder



 Comments   
Comment by Richard Gange [ 06/Sep/17 ]

See https://nexus.magnolia-cms.com/content/repositories/magnolia.public.releases/info/magnolia/widgetset/magnolia-vaadin-widgetset/5.5.6/magnolia-vaadin-widgetset-5.5.6.pom

Comment by Mikaël Geljić [ 06/Sep/17 ]

widgetset dependency to older pages versions would not be an issue, if webapp/bundle dependencies were getting page-editor transitively through pages-app (not through the widgetset)

As the widgetsets only use these deps upon compilation, they don't need them at runtime (but the UI & apps do). So we should mark them as provided (and let pages-app, ui-framework, content-editor and the likes bring those).

Generated at Mon Feb 12 09:15:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.