[NPMCLI-283] Make magnolia_control optional Created: 30/Aug/23  Updated: 31/Aug/23

Status: Open
Project: Magnolia CLI
Component/s: None
Affects Version/s: None
Fix Version/s: None

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

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
Date of First Response:

 Description   

Steps to reproduce

  1. Try to download tomcat server from Tomcat official page
  2. Unpack it
  3. Try to fire it up with mgnl start command

Expected results

CLI runs startup script if no magnolia_control is foundĀ 

Actual results

CLI throws error:

...\apache-tomcat-9.0.11\bin\magnolia_control.bat does not exist. Can't start up Magnolia.

Workaround

Development notes

Whole point of this step is to bind public instance if it not exists already. Many frontend developers don't setup public instances for simplicity/perfomance/speed reasons. CLI should not block usage of the plain Tomcat.


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