[
https://issues.apache.org/jira/browse/LUCENE-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248761#comment-13248761
]
Robert Muir commented on LUCENE-3965:
-------------------------------------
That would also simplify packaging, as modules' currently go out of their way
to make their
own dist/ directories too: e.g. under analyzers/common:
{noformat}
<property name="build.dir" location="../build/common" />
<property name="dist.dir" location="../dist/common" />
{noformat}
Same goes with licensing (they have their own LICENSE.txt/NOTICE.txt's). If the
products
are still going to be lucene/ and solr/ (and i think for simplicity for 4.0,
that's really
what it should be) then we don't need this.
> Move lucene/core to modules/core, same with test-framework, etc
> ---------------------------------------------------------------
>
> Key: LUCENE-3965
> URL: https://issues.apache.org/jira/browse/LUCENE-3965
> Project: Lucene - Java
> Issue Type: Task
> Components: general/build
> Affects Versions: 4.0
> Reporter: Robert Muir
>
> I think users get confused about how svn/source is structured,
> when in fact we are just producing a modular build.
> I think it would be more clear if the lucene stuff was underneath
> modules/, thats where our modular API is.
> we could still package this up as lucene.tar.gz if we want, and even name
> modules/core lucene-core.jar, but i think this would be a lot better
> organized than the current:
> * lucene
> * lucene/contrib
> * modules
> confusion.
--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
