[infinispan-dev] Separating FluentTypes into a separate file?

Dan Berindei dan.berindei at gmail.com
Wed Oct 12 12:27:24 EDT 2011


> On 12 October 2011 17:14, Dan Berindei <dan.berindei at gmail.com> wrote:
>> Making a non-public type public preserves binary compatibility,
>> according to http://wiki.eclipse.org/Evolving_Java-based_APIs_2#Achieving_API_Binary_Compatibility
>
> I don't think that's related with Galder's question is it? Why do we
> need binary compatibility? I think he's referring to APIs. Anyway the
> classname is changing as well as it was a nested class so I don't
> think it's preserving binary compatibility.
>

The FluentTypes interface is already top-level, it's just defined in
FluentConfiguration.java so it can't be public.
So making it public won't break compatibility, it won't even require
the recompilation of client classes.

Cheers
Dan


More information about the infinispan-dev mailing list