Michael McCandless wrote:
I think *not* having to maintain back compat of the package private APIs
is very important to keeping our freedom (and sanity!) to continue to
improve Lucene. This is similar to marking a new API as experimental
and subject to suddenly change in the next release: it reserves our
future freedom.
Definitely +1 on this strategy, so long as it's clearly documented.
Example: I'm working on a new version of Luke, where I use some of the
internal and experimental APIs (e.g. the commit points), being aware
that things may break in nasty ways if I upgrade to a different version
of Lucene. I've been forewarned, and I won't complain. :)
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __________________________________
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigram dot com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
