tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Funk <>
Date Thu, 09 Feb 2006 14:34:09 GMT
I see the point of the native dir. Once my sysadmin sees this (whose not much 
of a java guy) - he'd be confused in seeing a bin dir with jar, bat, sh, and 
so files in it. Maybe itstime to reorg the the bin package dir. Possibly 
something along the lines of:

bin/ <-- All the sh and bat files
lib/jar <-- all the jar files for the system classloader. The scripts can 
also be made smart enough to iterate throug this dir and append them instead 
of hardcoding.
lib/native/{platform}/ <!-- any needed .so, or dll files

Where platform can be some standard prefix based on OS and architecture. That 
way, if a binary is retrieved - the user knows immediately if the .so is not 
binary compatible.

Of course the above has many issues with respect to how to dyncamically pull 
in {platform} in the startup scripts. (Allowing a CATALINA_NATIVE would of 
course be nice as an override).

Personally - I'm indifferent to the whole thing because I'm swamped with my 
day job and don't have time to help with such a reorg. But I thought I'd 
throw it out as an idea.


Remy Maucherat wrote:

> Mladen Turk wrote:
>> Hi,
>> Any objections for committing this patch?
>> It sets LD_LIBRARY_PATH to include CATALINA_HOME/native
>> if CATALINA_HOME/native/ is present.
> Why not using the "bin" folder ?

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message