Re: Release Tomcat Native 1.1.23
> > Nope, will tag later today or over the weekend (depends on weather > conditions :) > Ok, I'll grab a SVN copy for now.
Re: Release Tomcat Native 1.1.23
On 02/24/2012 11:12 AM, Henri Gomez wrote: I just notice this 'release' Did you release a source tarball ? Nope, will tag later today or over the weekend (depends on weather conditions :) Cheers -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Release Tomcat Native 1.1.23
I just notice this 'release' Did you release a source tarball ? 2012/2/23 Costin Manolache > Thanks, I'll try it. > > Costin > > On Thu, Feb 23, 2012 at 11:53 AM, Mladen Turk wrote: > > > On 02/22/2012 07:22 PM, Costin Manolache wrote: > > > >> On Wed, Feb 22, 2012 at 9:12 AM, Mladen Turk wrote: > >> > >> > >> I'm trying to provide a way for people to build "libtcnative-2.so" so it > >> can be installed on > >> those systems along with the existing apr, openssl and libtcnative-1, > >> without requiring the installation of 2 versions of openssl, apr. > >> > >> > > Just committed a brief howto inside native/BUILDING > > See the last paragraph and check if it works for you. > > > > No need for cmake and stuff. The only needed thing is to > > comment or remove two lines from libapr-1.la file before > > building tomcat-native. > > > > > > > > Regards > > > > -- > > ^TM > > > > --**--**- > > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.**org< > dev-unsubscr...@tomcat.apache.org> > > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > >
Re: Release Tomcat Native 1.1.23
Thanks, I'll try it. Costin On Thu, Feb 23, 2012 at 11:53 AM, Mladen Turk wrote: > On 02/22/2012 07:22 PM, Costin Manolache wrote: > >> On Wed, Feb 22, 2012 at 9:12 AM, Mladen Turk wrote: >> >> >> I'm trying to provide a way for people to build "libtcnative-2.so" so it >> can be installed on >> those systems along with the existing apr, openssl and libtcnative-1, >> without requiring the installation of 2 versions of openssl, apr. >> >> > Just committed a brief howto inside native/BUILDING > See the last paragraph and check if it works for you. > > No need for cmake and stuff. The only needed thing is to > comment or remove two lines from libapr-1.la file before > building tomcat-native. > > > > Regards > > -- > ^TM > > --**--**- > To unsubscribe, e-mail: > dev-unsubscribe@tomcat.apache.**org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: Release Tomcat Native 1.1.23
On 02/22/2012 07:22 PM, Costin Manolache wrote: On Wed, Feb 22, 2012 at 9:12 AM, Mladen Turk wrote: I'm trying to provide a way for people to build "libtcnative-2.so" so it can be installed on those systems along with the existing apr, openssl and libtcnative-1, without requiring the installation of 2 versions of openssl, apr. Just committed a brief howto inside native/BUILDING See the last paragraph and check if it works for you. No need for cmake and stuff. The only needed thing is to comment or remove two lines from libapr-1.la file before building tomcat-native. Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Release Tomcat Native 1.1.23
On 02/22/2012 07:22 PM, Costin Manolache wrote: On Wed, Feb 22, 2012 at 9:12 AM, Mladen Turk wrote: However, not sure why you wish to do that. Many distros already provide tomcat-native so there's no real point for doing that, especially since we should not distribute unix binaries. Yes, distros provide tomcat-native, apr and openssl - with the 'stable' releases. I'm trying to provide a way for people to build "libtcnative-2.so" so it can be installed on those systems along with the existing apr, openssl and libtcnative-1, without requiring the installation of 2 versions of openssl, apr. Right if its --with-apr-static --with-openssl-static it could be a valid solution for someone that needs such specific deployments. It seems to work for me on linux ( using cmake ) - I get a tcnative.so with all the openssl/apr code linked in, without dependencies to libapr.so ( no SONAME ). No need for cmake. This can be done with gnu tools. I'll enable that when I catch some time. Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Release Tomcat Native 1.1.23
On Wed, Feb 22, 2012 at 9:12 AM, Mladen Turk wrote: > On 02/22/2012 05:47 PM, Costin Manolache wrote: > >> On Wed, Feb 22, 2012 at 8:13 AM, Mladen Turk wrote: >> >> One thing I would appreciate help with: I would like to have an option to >> statically link >> openssl and apr into the tc-native .so - I mean use openssl.a, apr.a. >> >> > You mean for unixes? > The solution would be to create stub libssl.so and libcrypto.so > so that libtcnative don't carry their SONAME and link to system so.x... > > Static linkage is not a good idea I'm afraid. > > > The reason is to avoid the system libraries which will probably have the >> wrong version. >> >> > Right. Having stubs, libtcnative will always link to libssl.so which > is usually symlink on any system. > At runtime we can check for SSL_version and fail in case it has wrong ABI. > > However, not sure why you wish to do that. Many distros already provide > tomcat-native so there's no real point for doing that, especially since > we should not distribute unix binaries. > Yes, distros provide tomcat-native, apr and openssl - with the 'stable' releases. I'm trying to provide a way for people to build "libtcnative-2.so" so it can be installed on those systems along with the existing apr, openssl and libtcnative-1, without requiring the installation of 2 versions of openssl, apr. It seems to work for me on linux ( using cmake ) - I get a tcnative.so with all the openssl/apr code linked in, without dependencies to libapr.so ( no SONAME ). So basically someone ( distros, users ) could build and deploy the new library along with the stable ones. I don't think we can require to upgrade the platform openssl or apr. The alternative would be to have the new openssl/apr .so in some /usr/local/ location. Costin > > > Regards. > > -- > ^TM > > --**--**- > To unsubscribe, e-mail: > dev-unsubscribe@tomcat.apache.**org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: Release Tomcat Native 1.1.23
On 02/22/2012 05:47 PM, Costin Manolache wrote: On Wed, Feb 22, 2012 at 8:13 AM, Mladen Turk wrote: One thing I would appreciate help with: I would like to have an option to statically link openssl and apr into the tc-native .so - I mean use openssl.a, apr.a. You mean for unixes? The solution would be to create stub libssl.so and libcrypto.so so that libtcnative don't carry their SONAME and link to system so.x... Static linkage is not a good idea I'm afraid. The reason is to avoid the system libraries which will probably have the wrong version. Right. Having stubs, libtcnative will always link to libssl.so which is usually symlink on any system. At runtime we can check for SSL_version and fail in case it has wrong ABI. However, not sure why you wish to do that. Many distros already provide tomcat-native so there's no real point for doing that, especially since we should not distribute unix binaries. Regards. -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Release Tomcat Native 1.1.23
On Wed, Feb 22, 2012 at 8:13 AM, Mladen Turk wrote: > On 02/22/2012 03:54 PM, Costin Manolache wrote: > >> On Tue, Feb 21, 2012 at 11:11 PM, Mladen Turk wrote: >> >>> Well I personally would not merge that into 1.1.x branch. >>> It would be a bit weird to have 1.1.22 as is, and 1.1.23 with >>> whole bunch of new features and API's. >>> That's not why we introduced branches at the first place. >>> >>> >>> That's right, I agree. >> >> > OK, so 1.1.x stays as is. > > > >> I see no problem with that. >>> It requires apr-1.4.x so this might be a solution for >>> that sslext code instead porting that back to 1.1.x >>> >>> >> sslext works best with openssl 1.0.1 beta 2 ( i.e. latest ) - to get npn >> working with older ssl it needs a patch ( nodejs, chrome do this ). >> But it compiles and just lacks the npn feature without the patch. >> >> So for me a 1.2.x with recent apr and openssl would be best. >> >> > Cool, lets then cleanup the code in trunk and go for 1.2.x > release after we cut 1.1.23. OK? > 1.1.x would be in feature freeze state after we release 1.2.x. > > I'd like we make 1.2.x mandatory for tomcat8 together with removing > all the code that checks for missing API. > > And finally after APR-2.0 gets released we can create 1.2.x branch > and make trunk as 2.0.x since with APR-2 abi will change. > > +1 One thing I would appreciate help with: I would like to have an option to statically link openssl and apr into the tc-native .so - I mean use openssl.a, apr.a. The reason is to avoid the system libraries which will probably have the wrong version. Right now there is the 'cmake' file in trunk that does this for linux64 - I'm sure it's not the right way :-), but couldn't figure how to do it with libtool. openssl/apr needs to be compiled with 'shared' option - otherwise they won't have pic/etc - and libtool seems to pick the .so over .a with all flags I tried ( it did work if I manually removed the .so). ( or if cmake or any of the other build tools is acceptable - will need to be made portable. I guess gyp would be easiest since there is already an openssl build file, but not for apr ). Costin > > Regards > -- > ^TM > > --**--**- > To unsubscribe, e-mail: > dev-unsubscribe@tomcat.apache.**org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: Release Tomcat Native 1.1.23
On 02/22/2012 03:54 PM, Costin Manolache wrote: On Tue, Feb 21, 2012 at 11:11 PM, Mladen Turk wrote: Well I personally would not merge that into 1.1.x branch. It would be a bit weird to have 1.1.22 as is, and 1.1.23 with whole bunch of new features and API's. That's not why we introduced branches at the first place. That's right, I agree. OK, so 1.1.x stays as is. I see no problem with that. It requires apr-1.4.x so this might be a solution for that sslext code instead porting that back to 1.1.x sslext works best with openssl 1.0.1 beta 2 ( i.e. latest ) - to get npn working with older ssl it needs a patch ( nodejs, chrome do this ). But it compiles and just lacks the npn feature without the patch. So for me a 1.2.x with recent apr and openssl would be best. Cool, lets then cleanup the code in trunk and go for 1.2.x release after we cut 1.1.23. OK? 1.1.x would be in feature freeze state after we release 1.2.x. I'd like we make 1.2.x mandatory for tomcat8 together with removing all the code that checks for missing API. And finally after APR-2.0 gets released we can create 1.2.x branch and make trunk as 2.0.x since with APR-2 abi will change. Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Release Tomcat Native 1.1.23
On Tue, Feb 21, 2012 at 11:11 PM, Mladen Turk wrote: > On 02/22/2012 06:17 AM, Costin Manolache wrote: > >> Mladen: please let me know if you want to further review the change or >> should I merge it to the branch. >> >> > Well I personally would not merge that into 1.1.x branch. > It would be a bit weird to have 1.1.22 as is, and 1.1.23 with > whole bunch of new features and API's. > That's not why we introduced branches at the first place. > > That's right, I agree. > > I also noticed there are few other diffs - in particular the 'interrupt' >> stuff in poll, few others. >> Any plans to merge them too ? >> > > Nope. Not to the 1.1.x branch > > > What's the plan with the trunk ? >> >> > We can release 1.2.0 from trunk. > That was my question - I didn't see any releases out of trunk, I assumed it's used for development and after some 'soak' merged back into 1.1.x > I see no problem with that. > It requires apr-1.4.x so this might be a solution for > that sslext code instead porting that back to 1.1.x > sslext works best with openssl 1.0.1 beta 2 ( i.e. latest ) - to get npn working with older ssl it needs a patch ( nodejs, chrome do this ). But it compiles and just lacks the npn feature without the patch. So for me a 1.2.x with recent apr and openssl would be best. > We can require 1.2.x for tomcat8 and actually use that > new API's without worrying on backward compatibility. I'm also interested in using the jni code 'standalone', so a native release without tomcat8 would also be nice. But no hurry - I was confused on the trunk->release branch policy. The main problem with jni is getting it compiled and installed on users machines. Costin > > > > > Regards > -- > ^TM > > --**--**- > To unsubscribe, e-mail: > dev-unsubscribe@tomcat.apache.**org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: Release Tomcat Native 1.1.23
On 02/22/2012 06:17 AM, Costin Manolache wrote: Mladen: please let me know if you want to further review the change or should I merge it to the branch. Well I personally would not merge that into 1.1.x branch. It would be a bit weird to have 1.1.22 as is, and 1.1.23 with whole bunch of new features and API's. That's not why we introduced branches at the first place. I also noticed there are few other diffs - in particular the 'interrupt' stuff in poll, few others. Any plans to merge them too ? Nope. Not to the 1.1.x branch What's the plan with the trunk ? We can release 1.2.0 from trunk. I see no problem with that. It requires apr-1.4.x so this might be a solution for that sslext code instead porting that back to 1.1.x We can require 1.2.x for tomcat8 and actually use that new API's without worrying on backward compatibility. Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Release Tomcat Native 1.1.23
Mladen: please let me know if you want to further review the change or
should I merge it to the branch.
I also noticed there are few other diffs - in particular the 'interrupt'
stuff in poll, few others.
Any plans to merge them too ? What's the plan with the trunk ?
Costin
On Tue, Feb 21, 2012 at 3:29 PM, Mladen Turk wrote:
> On 02/21/2012 09:56 PM, Costin Manolache wrote:
>
>> On Tue, Feb 21, 2012 at 12:51 PM, Rainer Jung**
>> wrote:
>>
>> On 21.02.2012 21:30, Costin Manolache wrote:
>>>
>>> Is this going to be from head ? How can I get the NPN ( sslext.c )
included
?
>>> Mladen is aiming for 1.1.23, so he will be releasing from the 1.1.x
>>> branch.
>>>
>>>
>> What's the process for backporting ? The main change is adding a file, so
>> it should be pretty safe.
>>
>>
> Not sure if that code is safe and I doubt it'll compile on all platforms,
> E.g
> TCN_IMPLEMENT_CALL(jint, SSLExt, setSessionData)(TCN_STDARGS, jlong
> tcsock, jbyteArray buf, jint len)
> {
> unsigned char bytes[len];
> ^^^
>
> This is not valid C code, although some compiler might allow it.
> You would need to use malloc for that buffer since the 'len' is not known
> in advance.
> BTW, what's the purpose of this code? Seems it requires java API as well,
> so
> not sure if that's present in all tomcat versions 1.1.23 is supposed to
> run.
> However if not used I don't care ;)
>
>
>
> Regards
> --
> ^TM
>
> --**--**-
> To unsubscribe, e-mail:
> dev-unsubscribe@tomcat.apache.**org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>
Re: Release Tomcat Native 1.1.23
On Tue, Feb 21, 2012 at 3:29 PM, Mladen Turk wrote:
> On 02/21/2012 09:56 PM, Costin Manolache wrote:
>
>> On Tue, Feb 21, 2012 at 12:51 PM, Rainer Jung**
>> wrote:
>>
>> On 21.02.2012 21:30, Costin Manolache wrote:
>>>
>>> Is this going to be from head ? How can I get the NPN ( sslext.c )
included
?
>>> Mladen is aiming for 1.1.23, so he will be releasing from the 1.1.x
>>> branch.
>>>
>>>
>> What's the process for backporting ? The main change is adding a file, so
>> it should be pretty safe.
>>
>>
> Not sure if that code is safe and I doubt it'll compile on all platforms,
> E.g
> TCN_IMPLEMENT_CALL(jint, SSLExt, setSessionData)(TCN_STDARGS, jlong
> tcsock, jbyteArray buf, jint len)
> {
> unsigned char bytes[len];
> ^^^
>
> This is not valid C code, although some compiler might allow it.
>
Fixed. Let me know if there is anything else.
> You would need to use malloc for that buffer since the 'len' is not known
> in advance.
> BTW, what's the purpose of this code?
The purpose is to allow use of few TLS extensions - 'next protocol
negotiation' is the main one for SPDY. Also to allow some optimizations -
like reusing sessions ( with a distributed cache or with no server-side
storage ).
> Seems it requires java API as well, so
> not sure if that's present in all tomcat versions 1.1.23 is supposed to
> run.
>
Java APIs are in trunk - and could use the native library independent of
tomcat version.
> However if not used I don't care ;)
As long as it doesn't break the build I suppose :-)
Costin
>
>
>
> Regards
> --
> ^TM
>
> --**--**-
> To unsubscribe, e-mail:
> dev-unsubscribe@tomcat.apache.**org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>
Re: Release Tomcat Native 1.1.23
On 02/21/2012 09:56 PM, Costin Manolache wrote:
On Tue, Feb 21, 2012 at 12:51 PM, Rainer Jungwrote:
On 21.02.2012 21:30, Costin Manolache wrote:
Is this going to be from head ? How can I get the NPN ( sslext.c )
included
?
Mladen is aiming for 1.1.23, so he will be releasing from the 1.1.x branch.
What's the process for backporting ? The main change is adding a file, so
it should be pretty safe.
Not sure if that code is safe and I doubt it'll compile on all platforms,
E.g
TCN_IMPLEMENT_CALL(jint, SSLExt, setSessionData)(TCN_STDARGS, jlong tcsock,
jbyteArray buf, jint len)
{
unsigned char bytes[len];
^^^
This is not valid C code, although some compiler might allow it.
You would need to use malloc for that buffer since the 'len' is not known in
advance.
BTW, what's the purpose of this code? Seems it requires java API as well, so
not sure if that's present in all tomcat versions 1.1.23 is supposed to run.
However if not used I don't care ;)
Regards
--
^TM
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Release Tomcat Native 1.1.23
Will do it tonight ( it's already in the trunk ) Costin On Tue, Feb 21, 2012 at 1:25 PM, Rainer Jung wrote: > On 21.02.2012 21:56, Costin Manolache wrote: > >> On Tue, Feb 21, 2012 at 12:51 PM, Rainer Jung** >> wrote: >> >> On 21.02.2012 21:30, Costin Manolache wrote: >>> >>> Is this going to be from head ? How can I get the NPN ( sslext.c ) included ? >>> > AFAIR 1.1.x is CTR. So you just add it and try to not break 1.1 :) > > If you think the same should be in trunk, add it first there and then > backport directly to 1.1.x. IMHO noone really uses the STATUS file for > tcnative. > > Regards, > > Rainer > > > > --**--**- > To unsubscribe, e-mail: > dev-unsubscribe@tomcat.apache.**org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: Release Tomcat Native 1.1.23
On 21.02.2012 21:56, Costin Manolache wrote: On Tue, Feb 21, 2012 at 12:51 PM, Rainer Jungwrote: On 21.02.2012 21:30, Costin Manolache wrote: Is this going to be from head ? How can I get the NPN ( sslext.c ) included ? AFAIR 1.1.x is CTR. So you just add it and try to not break 1.1 :) If you think the same should be in trunk, add it first there and then backport directly to 1.1.x. IMHO noone really uses the STATUS file for tcnative. Regards, Rainer - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Release Tomcat Native 1.1.23
On Tue, Feb 21, 2012 at 12:51 PM, Rainer Jung wrote: > On 21.02.2012 21:30, Costin Manolache wrote: > >> Is this going to be from head ? How can I get the NPN ( sslext.c ) >> included >> ? >> > > Mladen is aiming for 1.1.23, so he will be releasing from the 1.1.x branch. > What's the process for backporting ? The main change is adding a file, so it should be pretty safe. Costin > Regards, > > Rainer > > > On Tue, Feb 21, 2012 at 9:41 AM, Mladen Turk wrote: >> >> On 02/21/2012 06:05 PM, Christopher Schultz wrote: >>> >>> Mladen, On 2/21/12 11:30 AM, Mladen Turk wrote: We have couple of bugs fixed and its been quite a while since 1.1.22. > There is also few trivial bugs and patches in BZ which I plan to solve. > I volunteer as RM for 1.1.23. > > Objections, comments? > > I'd certainly like a release: the first release of the native component for FIPS support is in there. Exactly. I'd like to test the BZ45392 and see if we can add >>> OCSP support as well. I'll check how the patch correlates with >>> the current mod_ssl which also has OCSP support and apply it >>> but with compile time on/off so we can exclude any instability. >>> >>> >>> >>> Regards >>> -- >>> ^TM >>> >> > --**--**- > To unsubscribe, e-mail: > dev-unsubscribe@tomcat.apache.**org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: Release Tomcat Native 1.1.23
On 21.02.2012 21:30, Costin Manolache wrote: Is this going to be from head ? How can I get the NPN ( sslext.c ) included ? Mladen is aiming for 1.1.23, so he will be releasing from the 1.1.x branch. Regards, Rainer On Tue, Feb 21, 2012 at 9:41 AM, Mladen Turk wrote: On 02/21/2012 06:05 PM, Christopher Schultz wrote: Mladen, On 2/21/12 11:30 AM, Mladen Turk wrote: We have couple of bugs fixed and its been quite a while since 1.1.22. There is also few trivial bugs and patches in BZ which I plan to solve. I volunteer as RM for 1.1.23. Objections, comments? I'd certainly like a release: the first release of the native component for FIPS support is in there. Exactly. I'd like to test the BZ45392 and see if we can add OCSP support as well. I'll check how the patch correlates with the current mod_ssl which also has OCSP support and apply it but with compile time on/off so we can exclude any instability. Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Release Tomcat Native 1.1.23
Is this going to be from head ? How can I get the NPN ( sslext.c ) included ? Costin On Tue, Feb 21, 2012 at 9:41 AM, Mladen Turk wrote: > On 02/21/2012 06:05 PM, Christopher Schultz wrote: > >> Mladen, >> >> On 2/21/12 11:30 AM, Mladen Turk wrote: >> >>> We have couple of bugs fixed and its been quite a while since 1.1.22. >>> There is also few trivial bugs and patches in BZ which I plan to solve. >>> I volunteer as RM for 1.1.23. >>> >>> Objections, comments? >>> >> >> I'd certainly like a release: the first release of the native component >> for FIPS support is in there. >> >> > Exactly. I'd like to test the BZ45392 and see if we can add > OCSP support as well. I'll check how the patch correlates with > the current mod_ssl which also has OCSP support and apply it > but with compile time on/off so we can exclude any instability. > > > > Regards > -- > ^TM > > --**--**- > To unsubscribe, e-mail: > dev-unsubscribe@tomcat.apache.**org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: Release Tomcat Native 1.1.23
On 02/21/2012 06:05 PM, Christopher Schultz wrote: Mladen, On 2/21/12 11:30 AM, Mladen Turk wrote: We have couple of bugs fixed and its been quite a while since 1.1.22. There is also few trivial bugs and patches in BZ which I plan to solve. I volunteer as RM for 1.1.23. Objections, comments? I'd certainly like a release: the first release of the native component for FIPS support is in there. Exactly. I'd like to test the BZ45392 and see if we can add OCSP support as well. I'll check how the patch correlates with the current mod_ssl which also has OCSP support and apply it but with compile time on/off so we can exclude any instability. Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Release Tomcat Native 1.1.23
Mladen, On 2/21/12 11:30 AM, Mladen Turk wrote: > We have couple of bugs fixed and its been quite a while since 1.1.22. > There is also few trivial bugs and patches in BZ which I plan to solve. > I volunteer as RM for 1.1.23. > > Objections, comments? I'd certainly like a release: the first release of the native component for FIPS support is in there. Thanks, -chris signature.asc Description: OpenPGP digital signature
Release Tomcat Native 1.1.23
Hi, We have couple of bugs fixed and its been quite a while since 1.1.22. There is also few trivial bugs and patches in BZ which I plan to solve. I volunteer as RM for 1.1.23. Objections, comments? Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
