[
https://issues.apache.org/jira/browse/LUCENE-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201317#comment-13201317
]
Robert Muir commented on LUCENE-3753:
-------------------------------------
Can't say I object to the patch if it has a script to fix old patches, will go
back to 3x too, and if it will speed up the build system?
(Note: I didn't dig into LUCENE-3754, but its my impression that it would?)
My only suggestions (more like personal requests actually):
* can 'ant test-core' be an alias for 'test' inside lucene/core? And same with
javadocs-core? It might work
already in the patch (I didnt test), but I noticed this trips me up for solr
as well... just used to typing it i guess.
* can we give a heads up to the list first? i know i have a bunch of old
checkouts where if i ran 'svn up'
i'd have to deal with a hellacious merge conflict, but dumping out to a
patch, upgrading that patch with the tool,
and then applying that to a new checkout with patch --merge would probably be
easier (I'd only have to deal with
the "real" conflicts then)
> Restructure the Lucene build system
> -----------------------------------
>
> Key: LUCENE-3753
> URL: https://issues.apache.org/jira/browse/LUCENE-3753
> Project: Lucene - Java
> Issue Type: Improvement
> Components: general/build
> Affects Versions: 3.6, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Attachments: LUCENE-3753.patch
>
>
> Split out separate core/, test-framework/, and tools/ modules, each with its
> own build.xml, under the lucene/ directory, similar to the Solr restructuring
> done in SOLR-2452.
--
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]
