db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-590) How to integrate Derby with Lucene API?
Date Wed, 26 Mar 2014 22:50:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948591#comment-13948591
] 

Rick Hillegas commented on DERBY-590:
-------------------------------------

Here is a proposal for where to include the optional code in the source tree:

{noformat}
java/
  build/
    ...
  client/
    ...
  demo/
    ...
  drda/
    ...
  engine/
    ...
  optional/
    org/
      apache/
        derby/
          optional/
            api/
            lucene/
        
  shared/
    ...
  storeless/
    ...
  stubs/
    ...
  testing/
    ...
  tools/
    ...
{noformat}

The derbyOptionalTools.jar file would hold the classes under java/optional/org/apache/derby/optional.
Select classes in org.apache.derby.optional.api would go into the public api.

What are your thoughts?

Thanks,
-Rick


> How to integrate Derby with Lucene API?
> ---------------------------------------
>
>                 Key: DERBY-590
>                 URL: https://issues.apache.org/jira/browse/DERBY-590
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation, SQL
>            Reporter: Abhijeet Mahesh
>              Labels: derby_triage10_11
>         Attachments: derby-590-01-ag-publicAccessToLuceneRoutines.diff, derby-590-01-ah-publicAccessToLuceneRoutines.diff,
derby-590-01-am-publicAccessToLuceneRoutines.diff, derby-590-02-aa-cleanupFindbugsErrors.diff,
derby-590-03-aa-removeTestingDiagnostic.diff, derby-590-04-aa-removeIDFromListIndexes.diff,
derby-590-05-aa-accessDeclaredMembers.diff, derby-590-06-aa-suppressAccessChecks.diff, lucene_demo.diff,
lucene_demo_2.diff
>
>
> In order to use derby with lucene API what should be the steps to be taken? 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message