[MGNLRESTUI-86] Turn the project into a reactor Created: 10/Aug/23  Updated: 10/Aug/23

Status: Open
Project: Magnolia REST Client UI
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

We realised when releasing 1.0.6 of the module that it wasn't a reactor. Although that isn't a problem in itself, this was enough to fail our release workflow because every single other module included in bundles actually is a reactor (even if just 1-module reactor). Which is actually a good practice, as per Andrés' TEA session on dependency management.

Rather than add complexity to our release workflow for this module exclusively, we suggest refactoring it into a reactor. This can be done completely transparently.


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