On 05.03.2009 10:36, Mladen Turk wrote:
Rainer Jung wrote:
On 05.03.2009 10:03, Mark Thomas wrote:
Mladen Turk wrote:
Mark Thomas wrote:
I stumbled across some code in trunk for this. I had a poke around and
as far as
I can tell this hasn't been supported for quite some time. What do
people think
about removing it from mod_jk and trunk?
It is already disabled by default. You need a special configure flag
--enable-jni to include it in build.
But I agree, it's unsupported and simply doesn't work.
Any objections to removing it then?
Not from me, I have never seen it used. Would it be good, to anounce
the future removal in the 1.2.28 news and then do it in 1.2.29?
Others?
Yes, mark it as deprecated somehow.
Perhaps a warning during configure and some note in docs.
Also, instead removing it completely just use the empty
stub, so that we don't need to change the makefiles and stuff.
I added
- the word DEPRECATED to the help string of the jni related options in
configure
- a fat warning at the end of the configure run, when enable-jni was chosen
- a log warning to the jni worker factory
- lots of warnings to the docs
- a note to the 1.2.28 news and changelog
and change one jni based example for an unrelated feature in the docs.
So things should be set pretty well for removal of the support in 1.2.29
or 30.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
