[MGNLUI-548] Create adminInterface legacy module Created: 14/Jan/13  Updated: 03/Dec/13  Resolved: 25/Jan/13

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

Type: Task Priority: Neutral
Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-211 Remove dependency on adminInterace Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLUI-549 Fix VersionCommandTest to use new Met... Sub-task Closed Jozef Chocholacek  
MGNLUI-554 Add bootstrap files to the legacy module Sub-task Closed Jozef Chocholacek  
MGNLUI-560 Add an installation task that will de... Sub-task Closed Jozef Chocholacek  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   
  1. create infrastructure for the module (maven module in magnolia_ui)
  2. move commands sources from the 4.5.x magnolia_main to the new module


 Comments   
Comment by Jozef Chocholacek [ 21/Jan/13 ]

Stopping the progress. There will be no Legacy module, just a Legacy library (JAR file).

Comment by Eric Hechinger [ 23/Jan/13 ]

ActivationCommandTest.java Remove @version $Id$ on comments.

139 //todo: refactor and test other scenarios
140 // - recursive
141 // - with siblings before and after in the list

Could you do this or create a related ticket for improving these tests.
---------

On Module descriptor, clean the dependency.

----------

As this is a new module, could you remove on classes comments all unrelevant tags like
@author jackie $Id$
@version $Id$

Comment by Eric Hechinger [ 25/Jan/13 ]

Ok, as there will be no Legacy modulke, just simple JAR and the commands will be moved to a different places, these actions have to take place at this time (time of the refactoring).

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