tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <>
Subject Re: Branching connectors/jni for Tomcat Native
Date Fri, 03 Oct 2008 14:46:03 GMT
Mladen Turk schrieb:
> Hi,
> I'd like to create a branch of connectors
> for native component so it depends on the
> new APR 1.3.x API
> The new API offers some essential features targeted
> explicitly for pool issues usage in
> high level languages like Java.
> So, my idea is to branch the current trunk
> as connectors/branches/other/native/1.1.x
> and continue development in trunk with
> APR 1.3.x as minimum version required.
> This would be 1.3.x version of tomcat-native
> (to match the required APR version)
> dist-source target in dist.xml to include
> Any further 1.1.x release for Tomcat 6 would
> in that case be released out of that branch.
> Also inside tomcat/6.0.x branch
> we have svn:external 'native' pointing to
> connector:
> This would either be changed to point to that new branch or
> get completely removed now when we have tomcat-native releases.
> Comments?

Branching sounds good.

The native external is used in the dist.xml build file in order to
include the tcnative sources in the TC src release. So either we need to
adjust this part of TC build process, or simply switch the external for
TC 6.0.x to the 1.1 branch (and keep TC trunk native external pointing
to connectors trunk).

I expect you plan to branch all of connectors and not only jni/native?

Whenever that native trunk gets released the first time, we should
rethink the versioning though. I guess 1.2.x would make more sense than
1.3.x. We are now at 1.1.x, which is based on APR 1.2.x (and might work
with 0.9 too), so expressing any direct version dependency could be



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

View raw message