[NPMCLI-159] create-light-module: remove check about nearest tomcat and light-module dir Created: 07/Feb/18  Updated: 22/Feb/18  Resolved: 21/Feb/18

Status: Closed
Project: Magnolia CLI
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0.0, 2.2.1

Type: Task Priority: Major
Reporter: Federico Grilli Assignee: Evzen Fochr
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by NPMCLI-103 create-light-module: warn if nearest ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: CLI v3
Sprint: Kromeriz 134, Kromeriz 135
Story Points: 2

 Description   

"The incorrect assumption is that the place where a user is creating a light module should be the place where a mgnl start would work. But this is often not the case.
We could refine this check to only report a problem WHEN the system does find a tomcat upstream. But the best approach is to remove the check entirely based on the experiences of several users."



 Comments   
Comment by Christopher Zimmermann [ 20/Feb/18 ]

Please backport to version 2 series. People will still use version 2 for a little bit, and it reduces confusion.

Comment by Christopher Zimmermann [ 20/Feb/18 ]

re-opened just to accomodate fixing on version 2.

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