[MAGNOLIA-1201] tools: make a develop module Created: 10/Nov/06  Updated: 03/Dec/13  Resolved: 03/Dec/13

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

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-2496 Ability to switch workspace in JCR br... 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)
Date of First Response:

 Description   

we should put together the tools into one optional module:

  • jcr browser
  • developement
  • deploy
    ...

during startup of this module we would start: MAGNOLIA-1200



 Comments   
Comment by Philipp Bracher [ 17/Nov/06 ]

show log: tail logs in the browser ( errors, activation, ..)

Comment by Philipp Bärfuss [ 03/Dec/13 ]

Hi,

Thanks for reporting and/or commenting on this issue. We are currently reviewing issues that have had no or minimal activity for several years. Magnolia has evolved tremendously since this issue was reported; in order to focus our work, we are closing such issues.

We realize that some of these might still be valid today - and we ask for your cooperation here. In some cases, we will be linking to overarching stories, or simply more up-to-date similar issues. If you believe this issue is still relevant today, please leave a comment below and we will get back to you.

Cheers,

Generated at Mon Feb 12 03:24:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.