I'd just put comments at the top of the classes in the javadocs, maybe
just at the main entry points.
-Grant
On Jul 12, 2008, at 12:43 AM, Noble Paul നോബിള്
नोब्ळ् wrote:
How to make it mark as experimental? in Jira?
On Sat, Jul 12, 2008 at 3:19 AM, Grant Ingersoll
<[EMAIL PROTECTED]> wrote:
On Jul 10, 2008, at 1:57 PM, Noble Paul നോബിള്
नोब्ळ् wrote:
The contrib patch is already committed. So DIH must be going into
contrib. DIH will be an extra jar in the distro.
Yes, that is my plan.
If new features/fixes come up later the new jar can be dropped in
and
nothing else must break.
Yeah, I think we can put in DIH and mark it as experimental for this
release, and not be so concerned about backwards compatibility. I
have some
use cases that I don't think fit with the current implementation, but
haven't had time to work on them. Most of them have to do with
dealing with
lighter weight "on the fly" configurations. I think it is perfectly
reasonable to want send in a select statement and have it
executed. I also
think there may be an issue with JDBC drivers being present when
doing
configuration, but that is minor. I'm also not sure on the
connection
handling code, but these are discussions for the issue, not this
thread.
If someone can go through and mark it as experimental on the patch
(if it
hasn't been done already) that would be good. Something to the
effect that
the DIH APIs are subject to change in the next release. Caveat
Emptor.
If all the the external interfaces/(API & XML) are fine, any other
changes that might come up later should be OK
We have had some discussion on the use of interfaces versus abstract
classes. I need to revisit it and have a look again.
-Grant
--
--Noble Paul
--------------------------
Grant Ingersoll
http://www.lucidimagination.com
Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ
