[MGNLUI-4508] Come up with sensible package and artifact naming for the re-structured UI framework Created: 18/Jul/18  Updated: 21/Jan/20  Resolved: 21/Jan/20

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

Type: Task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MGNLUI-5618 Polish newly introduced class names a... Closed
supersession
is superseded by MGNLUI-4832 Node-less I18NAuthoringSupport API mo... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Account:
Epic Link: UI framework: basic features
Story Points: 8

 Description   

Aim at:

  • Reducing overall package depth
  • Eliminating traces of packaging by layer/type (in favor of packaging by feature)
  • Thinking JDK9-proof package split
  • Reviewing module names (both maven and magnolia-wise)
  • Validating "single-dependency" developer experience

Timebox as 8 SP



 Comments   
Comment by Simon Lutz [ 29/Jan/19 ]

Do this after the re-factoring.

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