[
https://issues.apache.org/jira/browse/SOLR-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062811#comment-13062811
]
Steven Rowe commented on SOLR-2452:
-----------------------------------
bq. 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?
I'm working on a script to automatically hack patch files against the old file
structure. When it's ready, I'll attach it to this issue.
bq. 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?
AFAIK, SVN merge is not smart enough. I should be able to finish the backport
in a day or two, though, so waiting shouldn't be too bad.
You don't need to wait for these things, and for small patches it may be
feasible to manually manage the patch hacking and the 3.x merging. But for
larger patches, the effort should be much smaller when the patch hacking script
is available and the 3.x backport is finished.
> 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]
