I'm using different directories for CATALINA_HOME and CATALINA_BASE
without copying the bin directory to BASE. Never had an issue with it.
Be sure to have the full path of tomcat-juli.jar in the Java Classpath
setting. That's what matters to Java. You can place the Jar file
anywhere you want as long as the Classpath points to it and the user
that runs Tomcat has read privileges to that file. But obviously the
easiest thing is to leave it in %CATALINA_HOME%/bin.
I've done that both on Windows and *nix systems.
Igal Sapir
Lucee Core Developer
Lucee.org <http://lucee.org/>
On 3/24/2017 9:06 AM, Jeffrey Janner wrote:
I was re-reading the RUNNING.txt to see why I had to copy tomcat-juli.jar to
the CATALINA_BASE/bin directory instead of just having it run out of
CATALINA_HOME/bin.
It seemed annoying to me to have to copy it to all my CATALINA_BASE instances
every time I upgraded, but I thought I ran into problems not having it there.
Then I ran into this bit of documentation:
In CATALINA_BASE:
* bin - Only the following files:
* setenv.sh (*nix) or setenv.bat (Windows),
* tomcat-juli.jar
....
In CATALINA_BASE:
* bin - Only the following files:
* setenv.sh (*nix) or setenv.bat (Windows),
* tomcat-juli.jar
So I guess my question is, can I really just leave it out of my CATALINA_BASE
directory without causing any issues?
I want to say I had issues with it not being there, but cannot recall what they
were.
And if there is no difference, why make the suggestion in the RUNNING.txt file
at all?
Jeff
