[MGNLUI-1093] Sass compilation must be performed in individual modules Created: 11/Apr/13  Updated: 25/Jun/13  Resolved: 11/Apr/13

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0

Type: Bug Priority: Blocker
Reporter: Tobias Mattsson Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLUI-706 Add Sass compilation as a Maven goal Closed
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

 Description   

Having the entire Sass compilation in widgetset module requires that the groovy maven plugin there pulls in magnolia-ui-vaadin-theme. However, it can only pull it in from the local or a remote repository. When building the project, the full reactor build, the newly created theme jar will not have been placed there when the project is built with mvn package or mvn release:prepare. Commonly the plugin does get hold of a theme jar from the local or a remote repository, this is always an older jar from a previous build.

Instead, each module must compile its own scss files.


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