+1
David W. Van Couvering wrote:
> As suggested by many of you, here is a call vote on the overall
> intention for how we want to share code, without bogging down in the
> details. Thanks to Kathey for a very helpful suggested wording.
>
> This vote is to support the overall intention to implement a framework
> to allow code sharing across the Derby product jars that will allow
> Derby jars of the same major version to be loaded in a Java VM without
> having to use specialized classloaders. Forward and backward
> compatibility between jar files within the same major version will be
> implemented using versioning, compatibility tests, and an explicit
> procedure for deprecating internal APIs.
>
> If the major version of the jars loaded in a JVM differ, the user will
> need to separate the two versions by using separate classloaders.
>
> This implementation will not have any significant impact on jar file
> size or otherwise affect product distribution or usage.
>
> The detailed guidelines are being documented and refined on the Derby
> Wiki site at
> http://wiki.apache.org/db-derby/SharedComponentVersioningGuidelines.
>
> Subsequent to approval of this vote, a working implementation of
> shared code using this framework will be submitted for review.
|