[
https://issues.apache.org/jira/browse/SOLR-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062776#comment-13062776
]
Erick Erickson commented on SOLR-2452:
--------------------------------------
What's the right thing to do here in terms of a patch against the old file
structure? Is it reasonable to check out fresh code, hack the patch file to
reflect the new paths and apply it to the new structure or must I re-edit the
source?
And is SVN merge smart enough to deal when merging from trunk to 3x when 3x
hasn't been changed, or is it better to just wait on it all until the back-port
is done?
The patch I'm trying to apply is 2535, it's pretty small so manually
reproducing it isn't a problem.
I get a little nervous in situations like this <G>....
> rewrite solr build system
> -------------------------
>
> Key: SOLR-2452
> URL: https://issues.apache.org/jira/browse/SOLR-2452
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Assignee: Steven Rowe
> Fix For: 3.4, 4.0
>
> Attachments: SOLR-2452-post-reshuffling.patch,
> SOLR-2452-post-reshuffling.patch, SOLR-2452-post-reshuffling.patch,
> SOLR-2452.diffSource.py.patch.zip, SOLR-2452.dir.reshuffle.sh,
> SOLR-2452.dir.reshuffle.sh
>
>
> As discussed some in SOLR-2002 (but that issue is long and hard to follow), I
> think we should rewrite the solr build system.
> Its slow, cumbersome, and messy, and makes it hard for us to improve things.
--
This message is automatically generated by JIRA.
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]
