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

Robert Muir commented on LUCENE-3965:
-------------------------------------

basically the overall design here was to rename 'contrib-crawl' to 
'modules-crawl'.
This just excludes the 'core' modules so the build works the same as before:

{noformat}
<fileset dir="." includes="*/build.xml" 
excludes="build/**,core/**,test-framework/**,tools/**"/>
{noformat}

Then after fixing the jar-XXX/contrib-uptodate stuff it was up and going fast.

Other things to fix still:
* modules still bogusly have their "own" build directories, but everything 
should be under lucene/build
* modules still have their own LICENSE.txt/NOTICE.txt/CHANGES.txt, this should 
all be merged. I think we should merge contrib/CHANGES.txt too (thats the only 
reason I didn't nuke that directory yet). In general i think we should have
one CHANGES.txt for each product (lucene, solr) and not tons of them littered 
everywhere.
* intellij/maven need fixing, especially so dist-maven works so we can test 
other packaging stuff.
* dist-patterns etc need fixing (basically: need to build some fake 4.0 
releases and review packaging is REALLY working).
* other nocommits i noted ...

                
> consolidate all api modules in one place and un!@$# packaging for 4.0
> ---------------------------------------------------------------------
>
>                 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
>         Attachments: LUCENE-3965.patch, LUCENE-3965_module_build.patch, 
> LUCENE-3965_module_build_pname.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to