OSX El Cap, Apache2, Tomcat 8, Lucee 5

My configuration is in the subject line, and i am SO close to having this
work.

on http://localhost, i get the Apache “It Works!” page.

on http://localhost:8080, i get the default Lucee page, served from:
/usr/local/Cellar/tomcat/8.5.3/libexec/apps/lucee

On http://localhost:8080/manager/html and
http://localhost:8080/host-manager/html, I get the Tomcat admin pages.

I have a directory, /Volumes/Storage/{companyname}/sites/www-test-app/www
that contains index.cfm and index.htm

I have www-test-app set up in my HOSTS file.

I have a host entry in httpd-vhosts.conf for www-test-app

I have an entry in tomcat’s server.xml file:





When i call up www-test-app/index.htm, I get my static test page.

When I call up http://www-test-app/index.cfm I get this error:

HTTP Status 404 -

type Status report

message

description The requested resource is not available.------------------------------
Apache Tomcat/8.5.3

I have stopped and restarted apache and tomcat to make sure config files
are read.

I do not see WEB-INF being created under
/Volumes/Storage/{companyname}/sites/www-test-app/www

My directory permissions are 777 for this directory and all subdirectories:
/Volumes/Storage/{companyname}/sites

I’m not sure if I need to make ownership changes though.

Apache2 was included with El Cap. Apache testconfig yields “syntax OK”.

Tomcat was installed via Homebrew.

Lucee was installed via WAR file per this page:
http://brianflove.com/2015/03/05/lucee-on-mac-os-x-yosemite-quick-start/

I am stuck from here… but oh so close, since the default Lucee page looks
great, including any cfoutput/variables.

Can’t find the disconnect… where do i go from here?

You need to tell apache to send cfm to tomcat to be served/processed.

Look at the bottom block on this page -
http://jhausotter.com/blog/setting-up-lucee-on-mac-os-x-yosemite/

Yep, I already have that in there…

Bump… still can’t fix this. Here’s is a sample from catalina.{date}.log:

13-Jul-2016 12:06:02.381 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server
version: Apache Tomcat/8.5.3
13-Jul-2016 12:06:02.383 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server
built: Jun 9 2016 11:16:29 UTC
13-Jul-2016 12:06:02.383 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server
number: 8.5.3.0
13-Jul-2016 12:06:02.383 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log OS
Name: Mac OS X
13-Jul-2016 12:06:02.383 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log OS
Version: 10.11.5
13-Jul-2016 12:06:02.383 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log
Architecture: x86_64
13-Jul-2016 12:06:02.383 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Java
Home:
/Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home/jre
13-Jul-2016 12:06:02.383 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log JVM
Version: 1.8.0_65-b17
13-Jul-2016 12:06:02.383 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log JVM
Vendor: Oracle Corporation
13-Jul-2016 12:06:02.383 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log
CATALINA_BASE: /usr/local/Cellar/tomcat/8.5.3/libexec
13-Jul-2016 12:06:02.383 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log
CATALINA_HOME: /usr/local/Cellar/tomcat/8.5.3/libexec
13-Jul-2016 12:06:02.384 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument:
-Djava.util.logging.config.file=/usr/local/Cellar/tomcat/8.5.3/libexec/conf/logging.properties
13-Jul-2016 12:06:02.384 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
13-Jul-2016 12:06:02.384 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djdk.tls.ephemeralDHKeySize=2048
13-Jul-2016 12:06:02.384 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Dcatalina.base=/usr/local/Cellar/tomcat/8.5.3/libexec
13-Jul-2016 12:06:02.385 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Dcatalina.home=/usr/local/Cellar/tomcat/8.5.3/libexec
13-Jul-2016 12:06:02.385 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.io.tmpdir=/usr/local/Cellar/tomcat/8.5.3/libexec/temp
13-Jul-2016 12:06:02.385 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based
Apache Tomcat Native library which allows optimal performance in production
environments was not found on the java.library.path:
/Users/marc/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.
13-Jul-2016 12:06:02.578 INFO [main]
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
[“http-nio-8080”]
13-Jul-2016 12:06:02.619 INFO [main]
org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared
selector for servlet write/read
13-Jul-2016 12:06:02.623 INFO [main]
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
[“ajp-nio-8009”]
13-Jul-2016 12:06:02.624 INFO [main]
org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared
selector for servlet write/read
13-Jul-2016 12:06:02.625 INFO [main]
org.apache.catalina.startup.Catalina.load Initialization processed in 702 ms
13-Jul-2016 12:06:02.654 INFO [main]
org.apache.catalina.core.StandardService.startInternal Starting service
Catalina
13-Jul-2016 12:06:02.655 INFO [main]
org.apache.catalina.core.StandardEngine.startInternal Starting Servlet
Engine: Apache Tomcat/8.5.3
13-Jul-2016 12:06:02.665 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDescriptor Deploying
configuration descriptor
/usr/local/Cellar/tomcat/8.5.3/libexec/conf/Catalina/localhost/ROOT.xml
13-Jul-2016 12:06:03.183 INFO [localhost-startStop-1]
org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned
for TLDs yet contained no TLDs. Enable debug logging for this logger for a
complete list of JARs that were scanned but no TLDs were found in them.
Skipping unneeded JARs during scanning can improve startup time and JSP
compilation time.
13-Jul-2016 12:06:08.815 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDescriptor Deployment of
configuration descriptor
/usr/local/Cellar/tomcat/8.5.3/libexec/conf/Catalina/localhost/ROOT.xml has
finished in 6,149 ms
13-Jul-2016 12:06:08.816 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web
application directory /usr/local/Cellar/tomcat/8.5.3/libexec/webapps/docs
13-Jul-2016 12:06:08.837 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web
application directory /usr/local/Cellar/tomcat/8.5.3/libexec/webapps/docs
has finished in 21 ms
13-Jul-2016 12:06:08.837 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web
application directory
/usr/local/Cellar/tomcat/8.5.3/libexec/webapps/examples
13-Jul-2016 12:06:09.079 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web
application directory
/usr/local/Cellar/tomcat/8.5.3/libexec/webapps/examples has finished in 241
ms
13-Jul-2016 12:06:09.079 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web
application directory
/usr/local/Cellar/tomcat/8.5.3/libexec/webapps/host-manager
13-Jul-2016 12:06:09.104 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web
application directory
/usr/local/Cellar/tomcat/8.5.3/libexec/webapps/host-manager has finished in
25 ms
13-Jul-2016 12:06:09.104 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web
application directory /usr/local/Cellar/tomcat/8.5.3/libexec/webapps/manager
13-Jul-2016 12:06:09.123 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web
application directory
/usr/local/Cellar/tomcat/8.5.3/libexec/webapps/manager has finished in 19 ms
13-Jul-2016 12:06:09.157 INFO [www-test-app-startStop-1]
org.apache.catalina.core.ApplicationContext.log Marking servlet CFMLServlet
as unavailable
13-Jul-2016 12:06:09.157 SEVERE [www-test-app-startStop-1]
org.apache.catalina.core.StandardContext.loadOnStartup Servlet
[CFMLServlet] in web application threw load() exception
java.lang.ClassNotFoundException: lucee.loader.servlet.CFMLServlet
at
org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1282)
at
org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1116)
at
org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:520)
at
org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:501)
at
org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:118)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1061)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1000)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4902)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5212)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:152)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1405)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1395)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Am i the only one with this configuration? I cannot use Lucee express
because of the case sensitivity issues. Mac, Apache2, Tomcat and Lucee
shouldn’t be this hard. I’ve documented every single step, if I need to
provide more information.

Right, but the Lucee guide assumes you already have Tomcat running! (Apache
is completely separate.)

As for case-sensitivity, on OSX that’s going to be based on your file
system. If you run “diskutil info /” in Terminal, look to see if “File
System Personality” specifically says “Case-sensitive”. If it doesn’t then
Tomcat will pick up the file regardless of case.On Thursday, July 14, 2016 at 4:18:46 PM UTC-4, Franc Amour wrote:

I can’t use the guide you specified, because Tomcat’s web server is case
sensitive when it comes to filenames, and I have legacy apps that are not
altogether correct with the case of the file references. I need the Mac’s
Apache web server, connected to Tomcat (which does seem to be working
fine), with Lucee running as an app under Tomcat. This is supposed to be
Tomcat’s forte. Instead i just want to eat lead.

These are the guides i’ve followed so far:

http://craiccomputing.blogspot.com/2012/07/installing-apache-tomcat-on-mac-os-x.html

http://brianflove.com/2015/03/05/lucee-on-mac-os-x-yosemite-quick-start/

Just a bit of an idea, instead of using your setup, have you considered
using something like Commandbox and run Lucee through that. I found it
worked very well on my MacBook Pro at home.

hth,
larryOn Wednesday, 13 July 2016 19:37:58 UTC-4, Franc Amour wrote:

Am i the only one with this configuration? I cannot use Lucee express
because of the case sensitivity issues. Mac, Apache2, Tomcat and Lucee
shouldn’t be this hard. I’ve documented every single step, if I need to
provide more information.

Hi Juan,

The only web.xml file I’ve ever edited in this setup is:

/usr/local/Cellar/tomcat/8.5.3/libexec/conf

I see web.xml files for all the tomcat “apps” - docs, host-manager,
manager, and examples - which I have never touched.

And I see a web.xml file in:

/usr/local/Cellar/tomcat/8.5.3/libexec/apps/lucee/WEB-INF

which I also have never touched.

This is what I added to /usr/local/Cellar/tomcat/8.5.3/libexec/conf/web.xml
:

CFMLServlet CFML runtime Engine lucee.loader.servlet.CFMLServlet
    <init-param>
        <param-name>lucee-server-directory</param-name>

/usr/local/Cellar/tomcat/8.5.3/libexec/apps/lucee/

        <description>Lucee Server configuration directory (for 

Server-wide configurations, settings, and libraries)


lucee-web-directory
{web-root-directory}/WEB-INF/lucee/
Lucee Web Directory (for Website-specific
configurations, settings, and libraries)

1

<servlet>
    <servlet-name>RESTServlet</servlet-name>
    <description>Servlet to access REST service</description>
    <servlet-class>lucee.loader.servlet.RestServlet</servlet-class>
    <load-on-startup>2</load-on-startup>
</servlet>

<servlet-mapping>
    <servlet-name>CFMLServlet</servlet-name>
    <url-pattern>*.cfm</url-pattern>
    <url-pattern>*.cfml</url-pattern>
    <url-pattern>*.cfc</url-pattern>
    <url-pattern>/index.cfm/*</url-pattern>
    <url-pattern>/index.cfc/*</url-pattern>
    <url-pattern>/index.cfml/*</url-pattern>
</servlet-mapping>

<servlet-mapping>
    <servlet-name>RESTServlet</servlet-name>
    <url-pattern>/rest/*</url-pattern>
</servlet-mapping>

I can’t use the guide you specified, because Tomcat’s web server is case
sensitive when it comes to filenames, and I have legacy apps that are not
altogether correct with the case of the file references. I need the Mac’s
Apache web server, connected to Tomcat (which does seem to be working
fine), with Lucee running as an app under Tomcat. This is supposed to be
Tomcat’s forte. Instead i just want to eat lead.

These are the guides i’ve followed so far:

http://craiccomputing.blogspot.com/2012/07/installing-apache-tomcat-on-mac-os-x.html

http://brianflove.com/2015/03/05/lucee-on-mac-os-x-yosemite-quick-start/

I would consider anything that provides accurate setup instructions and
does not require case-sensitivity - i am dealing with legacy code with file
references that are not always case accurate, and i have no time to fix old
code that otherwise works. In all the various ways of setting this up, i
just hadn’t come across commandbox and am not currently familiar with it.

However, it would be really great to have my current setup working, since
i’m clearly only one step away, and it would lead to a better understanding
of how these pieces fit together if I could be guided with the best way to
troubleshoot and where to look.On Thursday, July 14, 2016 at 9:08:23 AM UTC-4, Larry C. Lyons wrote:

Just a bit of an idea, instead of using your setup, have you considered
using something like Commandbox and run Lucee through that. I found it
worked very well on my MacBook Pro at home.

hth,
larry

On Wednesday, 13 July 2016 19:37:58 UTC-4, Franc Amour wrote:

Am i the only one with this configuration? I cannot use Lucee express
because of the case sensitivity issues. Mac, Apache2, Tomcat and Lucee
shouldn’t be this hard. I’ve documented every single step, if I need to
provide more information.

I checked and while it says “Journaled HFS+” I can definitely tell you that
the Lucee Express install had an issue with case sensitivity when calling
static resources such as images. Since I do appear to have Apache and
Tomcat running and talking to each other, I’ll backtrack and try the Lucee
guide again.On Thursday, July 14, 2016 at 4:30:52 PM UTC-4, Juan Aguilar wrote:

Right, but the Lucee guide assumes you already have Tomcat running!
(Apache is completely separate.)

As for case-sensitivity, on OSX that’s going to be based on your file
system. If you run “diskutil info /” in Terminal, look to see if “File
System Personality” specifically says “Case-sensitive”. If it doesn’t then
Tomcat will pick up the file regardless of case.

On Thursday, July 14, 2016 at 4:18:46 PM UTC-4, Franc Amour wrote:

I can’t use the guide you specified, because Tomcat’s web server is case
sensitive when it comes to filenames, and I have legacy apps that are not
altogether correct with the case of the file references. I need the Mac’s
Apache web server, connected to Tomcat (which does seem to be working
fine), with Lucee running as an app under Tomcat. This is supposed to be
Tomcat’s forte. Instead i just want to eat lead.

These are the guides i’ve followed so far:

http://craiccomputing.blogspot.com/2012/07/installing-apache-tomcat-on-mac-os-x.html

http://brianflove.com/2015/03/05/lucee-on-mac-os-x-yosemite-quick-start/

But for that to work, the web-inf directory I copy must contain everything
(including lucee-server, etc.), not just the lucee subdirectory… which is
contrary to the production environment, so things are still very wrong.On Thursday, July 14, 2016 at 2:12:09 PM UTC-4, Franc Amour wrote:

update, if this helps…

if i copy

/usr/local/Cellar/tomcat/8.5.3/libexec/apps/lucee/WEB-INF

to

/Volumes/Storage/{companyname}/sites/www-test-app/www

It runs the index.cfm file. So this SEEMS like it’s most likely an issue
with tomcat either not knowing where to place the web-inf file in my
virtual host directory, or not having permissions to do so. I do not know
what user tomcat8 is running under, and i’m not sure where in the
configuration files the directory to write WEB-INF would specified.

Did you edit catalina.properties to point to the Lucee JARs?

See
http://docs.lucee.org/guides/running-lucee/osx/installing-tomcat-and-lucee-on-os-x-using-the-lucee-war-file.html

And, a similar but unrelated issue I worked through last month:

https://groups.google.com/d/topic/lucee/iMrZ3sczx04/discussionOn Thursday, July 14, 2016 at 2:23:23 PM UTC-4, Franc Amour wrote:

But for that to work, the web-inf directory I copy must contain everything
(including lucee-server, etc.), not just the lucee subdirectory… which is
contrary to the production environment, so things are still very wrong.

I’m just confused as all hell now about which directories should be
specified where. I’ve attached all the relevant XML files and a screenshot
of my tomcat directory structure.

web.xml (166 KB)

server.xml (7.42 KB)

catalina.properties (7.1 KB)

Just a wild guess here but does your server’s conf/web.xml define the lucee
servlet (and other config) or are these only configured in your
ROOT/WEB-INF/web.xml?On Thursday, July 14, 2016 at 11:05:09 AM UTC-4, Franc Amour wrote:

I would consider anything that provides accurate setup instructions and
does not require case-sensitivity - i am dealing with legacy code with file
references that are not always case accurate, and i have no time to fix old
code that otherwise works. In all the various ways of setting this up, i
just hadn’t come across commandbox and am not currently familiar with it.

However, it would be really great to have my current setup working, since
i’m clearly only one step away, and it would lead to a better understanding
of how these pieces fit together if I could be guided with the best way to
troubleshoot and where to look.

update, if this helps…

if i copy

/usr/local/Cellar/tomcat/8.5.3/libexec/apps/lucee/WEB-INF

to

/Volumes/Storage/{companyname}/sites/www-test-app/www

It runs the index.cfm file. So this SEEMS like it’s most likely an issue
with tomcat either not knowing where to place the web-inf file in my
virtual host directory, or not having permissions to do so. I do not know
what user tomcat8 is running under, and i’m not sure where in the
configuration files the directory to write WEB-INF would specified.

That doesn’t look altogether correct to me, but I used a different
installation guide. Where it varies from what I’ve done is where you create
the “apps” directory and then the ROOT.xml stuff. Unfortunately, that’s not
something I’m familiar with.

If it’s an option to start over, try the Lucee guide (
http://docs.lucee.org/guides/running-lucee/osx/installing-tomcat-and-lucee-on-os-x-using-the-lucee-war-file.html
http://www.google.com/url?q=http%3A%2F%2Fdocs.lucee.org%2Fguides%2Frunning-lucee%2Fosx%2Finstalling-tomcat-and-lucee-on-os-x-using-the-lucee-war-file.html&sa=D&sntz=1&usg=AFQjCNFLs2FcerbRw1SVHbz_wGkgzCkQlg).
Some of those “//” are incorrect but the idea is to replace the
webapps/ROOT with a webapps/ROOT.war that gets deployed.

Once you’re there, you’ll probably need to modify the conf/web.xml file to
make sure that Tomcat has global servlet, servlet-mapping, etc…
configurations. Then you can tackle server.xml.

I can imagine how frustrating this is. When it works, it just does. When it
doesn’t, it’s pull-your-hair-out time.

Good luck!On Thursday, July 14, 2016 at 3:11:35 PM UTC-4, Franc Amour wrote:

I’m just confused as all hell now about which directories should be
specified where. I’ve attached all the relevant XML files and a screenshot
of my tomcat directory structure.

And i see that lucee-inst.jar doesn’t even exist in the .49 version of the
WAR file… so I’m not sure what to do with the setenv.sh file content
instructions at this point.On Friday, July 15, 2016 at 10:48:24 AM UTC-4, Franc Amour wrote:

Major issue discovered:

The war file specified at:

http://docs.lucee.org/guides/running-lucee/osx/installing-tomcat-and-lucee-on-os-x-using-the-lucee-war-file.html

Points to a crazy, disorganized folder at:
https://bitbucket.org/lucee/lucee/downloads
where the newest WAR file is 5.0.0.49

This is not the newest, which can be found at the ‘main’ Lucee download
page:
http://lucee.org/downloads.html
where the newest WAR file is 5.0.0.252.

And the difference between these two files is HUGE - they appear to have a
completely different archive structure. The newest one CANNOT be used with
the instructions at:

http://docs.lucee.org/guides/running-lucee/osx/installing-tomcat-and-lucee-on-os-x-using-the-lucee-war-file.html
because it doesn’t even contain lucee-inst, which is a file that is part
of the setenv.sh contents to be created in those instructions. There’s
major differences, and we need a new set of instructions if we want to use
the very latest version of Lucee.

No idea how to rewrite the instructions for anyone else, so I guess I’m
stuck using a slightly older WAR file for now.

WELP… I’ve tried everything I can think of. There are currently NO good
instructions
on how to deploy Lucee 5 on a working OSX/Apache/Tomcat8
configuration. The last good instructions appear to be for the Lucee 4.5
WAR file. The Lucee 5 war file is too different.

If anyone has any decent step-by-step instructions, I’m all ears - at this
point, this has pretty much been a wasted week, and the Lucee community
here has been notably silent on the issue overall. I cannot use Lucee 5
express due to the case sensitivity of the tomcat java-based web server,
plus i wish my dev environment to be closer to my production environments
in that regard anyway. I would love to figure this out, not just for me,
but for anyone else wishing to do this in the future. I appear to be stuck
with Lucee 4.5 if I want isolated installs of Apache and Tomcat. Seems a
bit ridiculous, but I guess I’m in the minority at this point.>

Major issue discovered:

The war file specified at:
http://docs.lucee.org/guides/running-lucee/osx/installing-tomcat-and-lucee-on-os-x-using-the-lucee-war-file.html

Points to a crazy, disorganized folder at:
https://bitbucket.org/lucee/lucee/downloads
where the newest WAR file is 5.0.0.49

This is not the newest, which can be found at the ‘main’ Lucee download
page:
http://lucee.org/downloads.html
where the newest WAR file is 5.0.0.252.

And the difference between these two files is HUGE - they appear to have a
completely different archive structure. The newest one CANNOT be used with
the instructions at:
http://docs.lucee.org/guides/running-lucee/osx/installing-tomcat-and-lucee-on-os-x-using-the-lucee-war-file.html
because it doesn’t even contain lucee-inst, which is a file that is part of
the setenv.sh contents to be created in those instructions. There’s major
differences, and we need a new set of instructions if we want to use the
very latest version of Lucee.

No idea how to rewrite the instructions for anyone else, so I guess I’m
stuck using a slightly older WAR file for now.