Mladen Turk wrote:
jean-frederic clere wrote:
Mark Thomas wrote:
jean-frederic clere wrote:
I think that is all working around the fact that tcnative is not
mandatory module for Tomcat and it is somehow independent from tomcat.
tcnative builds contain cryptosoftware (openssl) and that means they
may not be available for download in the ASF site. But that doesn't
prevent us from releasing tcnative sources.
tcnative is not very visible and I am +1 for changing this.
(updating site and tc build).
This is my preferred option. There would also need to be a release
vote for all the src distros on a.o/dist.
And we should remove any of the files that doesn't get voted.
If there is some show stopper issue with releasing native separately
that I haven't seen, then I am happy as the svn solution as an
alternative.
I am now working on arranging trunk to use a separated tcnative. Part
of the logic is already in the actual code.
I can only tell you that I'll vote -1 on any attempt
to make the tomcat native connector as separate product.
We should better remove it altogether from the Tomcat distribution
until we either find a way to build it together with Tomcat
or just forget about it.
What is in the tomcat tarball is very hard to use it requires
automake/autoconf stuff.
Cheers
Jean-Frederic
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
