Catch error scenario when user tries to start a server with a WEB-INF

Description

If you try to start a given cf engine in a folder that also has a WEB-INF if causes errors because runwar tries to load its jars as well. If we can't work around this in Runwar, then just catch the scenario and throw an error so the user knows that the heck is going on.

Usually the error looks something like:

Starting - port:59089 stop-port:60984 warpath:file:/C:/Users/tonyj/Desktop/websites/lineage/
context: / - version: 3.4.5
web-dirs: C:\Users\tonyj\Desktop\websites\lineage
Log Directory: C:\Users\tonyj\.CommandBox\server\1FF9103FF4CF3F6EDC70E0521DFF2617-lineage\lucee-4.5.2.018\logs
******************************************************************************
Exception in thread "main" java.lang.NullPointerException
at runwar.Server.getJarList(Server.java:702)
at runwar.Server.startServer(Server.java:273)
at runwar.Start.main(Start.java:12)

  •  

    •  

      • stopping server

      • server did not appear to be running

Gliffy Diagrams

Activity

Show:

Brad Wood October 3, 2016 at 4:57 PM

Submitted a pull request to Runwar to try and fix this:
https://github.com/cfmlprojects/runwar/pull/35

Brad Wood October 3, 2016 at 3:45 PM

This needs to be fixed on the Runwar side. I've spoken with about it a few times via Slack, but today I entered this ticket so it wouldn't get forgotten about.

https://github.com/cfmlprojects/runwar/issues/34

Thomas Rotter August 16, 2016 at 10:52 AM

+1 - took me hours to figure out

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Fix versions

Priority

Sentry

Created June 14, 2016 at 5:14 PM
Updated October 5, 2016 at 2:43 AM
Resolved October 5, 2016 at 2:43 AM