Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Wed, 18 Apr 2012 13:56:23 +0000 (UTC)
From: "Robert Muir (Created) (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <841031844.855.1334757383612.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (LUCENE-3997) join module should not depend on
 grouping module
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

join module should not depend on grouping module
------------------------------------------------

                 Key: LUCENE-3997
                 URL: https://issues.apache.org/jira/browse/LUCENE-3997
             Project: Lucene - Java
          Issue Type: Task
    Affects Versions: 4.0
            Reporter: Robert Muir
             Fix For: 4.0


I think TopGroups/GroupDocs should simply be in core? 

Both grouping and join modules use these trivial classes, but join depends on grouping just for them.

I think its better that we try to minimize these inter-module dependencies.
Of course, another option is to combine grouping and join into one module, but
last time i brought that up nobody could agree on a name. 

Anyway I think the change is pretty clean: its similar to having basic stuff like Analyzer.java in core,
so other things can work with Analyzer without depending on any specific implementing modules.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org