tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mladen Turk <>
Subject Re: tcnative API stability/compatibility
Date Fri, 02 Jan 2009 10:57:33 GMT
Rainer Jung wrote:
> On 02.01.2009 08:25, Mladen Turk wrote:
>> Rainer Jung wrote:
>>> a) bundling native and org/apache/tomcat/jni code in one place in svn
>>> and releasing together
>>> or
>>> b) separating only the native implementation
>> Option a) was used cause we didn't have separate tcnative
>> release when it was introduced.
>> Since this is now a separate downloadable bundle we should
>> use the option b) and populate Java classes during
>> download task when building Tomcat.
> I'm not sure I exactly understand this: when using b), the Java classes 
> will be kept where? If we don't change anything, they (copies of them) 
> are already part of TC trunk and TC 6, so need to "populate".

Like now, in connectors/jni/java

> I'm not sure, if the separate release cycles prevent a). My impression 
> is, that the Java API of tcnative (org.apache.tomcat.jni) is pretty 
> stable, so the need for releasing versions of that when releasing a 
> version of Tomcat should not be the regular case.

It doesn't mater if the API is stable or not.
Tomcat will just depend on and use the
pre-compiled .jar
(like any other jakarta-commons component for example)


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

View raw message