tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <>
Subject Re: tcnative API stability/compatibility
Date Fri, 02 Jan 2009 09:24:13 GMT
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".

>> Do we want to delete the copies of org/apache/tomcat/jni in TC trunk
>> and 6.0.x and use instead ones downloaded from a tcnative release or
>> an svn external to the new tcnative svn location?
>> I tend to suggest a) and also getting rid of the redundant copies of
>> the classes in TC trunk and 6, but I'm not sure if I noticed all
>> implications.
> We cannot use that option because of separate release cycles.
> I was trying to keep them together, but other folks didn't agree with
> that, so now we'll have to choose the option b), which is fine
> as well. It needs some build process changes, but that shouldn't
> be a problem.

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.



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

View raw message