Hi Darx,
You should check out complete Trunk as Steven said. I tried a coupled hours
ago to check out the source code below and there wasn't any problem.
http://svn.apache.org/repos/asf/lucene/dev/trunk
On Mon, Jan 3, 2011 at 11:19 AM, Darx Oman wrote:
> when I do a checkout I got this error
>
>
when I do a checkout I got this error
REPORT of '/repos/asf/!svn/vcc/default': Could not read response body: An
existing connection was forcibly closed by the remote host.
so i'll try to checkout each folder separately
solr, modules, lucene
Hi Darx,
On 1/3/2001 at 2:15 AM, Darx Oman wrote:
> I checked out source code svn, and applied the patch
> but when I build the source code I've got the following error
>
> C:\trunk\solr\common-build.xml:245: C\trunk\modules\analysis\phonetic
> does not exist.
You have to check out everything
Hi Gora
Thanx for your quick respnse.
I checked out source code svn, and applied the patch
but when I build the source code I've got the following error
C:\trunk\solr\common-build.xml:245: C\trunk\modules\analysis\phonetic does
not exist.
On Mon, Jan 3, 2011 at 10:33 AM, Darx Oman wrote:
> Hi guys
> would someone please explain to me how to apply a patch to solr
> lets say for example "SOLR-2129-version3.patch"
>
> i'm Running Solr Trunk "apache-solr-4.0-2011-01-02_08-06-03"
> on Windows environment
This link, http://wiki.apache.o
: Thanks, but my question here was not about the patch command itself (which I
: already know), but about simpler way (if any) to go about guaranteeing a
: proper patch with the right file revisions needed by the patch.
as i mentioned before, there is no garuntee that you are patching the
exact
You should be ok with the the revision option below. Look for the
highest revision number in the list of files in the patch as
subversion increments revision number on a repo basis not a file basis
so the highest number will represent the current state of all the
files when the patch was ma
Thanks, but my question here was not about the patch command itself (which I
already know), but about simpler way (if any) to go about guaranteeing a
proper patch with the right file revisions needed by the patch.
Michael
Joe Calderon-2 wrote:
>
> patch -p0 < /path/to/field-collapse-5.patch
>
sorry got cut off,
patch, then ant clean dist, will give you the modified solr war file,
if it doesnt apply cleanly (which i dont think is currently the case),
you can go back to the latest revision referenced in the patch,
On Tue, Nov 3, 2009 at 8:17 PM, Joe Calderon wrote:
> patch -p0 < /path/
patch -p0 < /path/to/field-collapse-5.patch
On Tue, Nov 3, 2009 at 7:48 PM, michael8 wrote:
>
> Hmmm, perhaps I jumped the gun. I just looked over the field collapse patch
> for SOLR-236 and each file listed in the patch has its own revision #.
>
> E.g. from field-collapse-5.patch:
> --- src/jav
Hmmm, perhaps I jumped the gun. I just looked over the field collapse patch
for SOLR-236 and each file listed in the patch has its own revision #.
E.g. from field-collapse-5.patch:
--- src/java/org/apache/solr/core/SolrConfig.java (revision 824364)
--- src/solrj/org/apache/solr/client/so
Perfect. This is what I need to know instead of patching 'in the dark'.
Good thing SVN revision cuts across all files like a tag.
Thanks Mike!
Michael
cambridgemike wrote:
>
> You can see what revision the patch was written for at the top of the
> patch,
> it will look like this:
>
> Index
: --- org/apache/solr/handler/MoreLikeThisHandler.java (revision 772437)
: +++ org/apache/solr/handler/MoreLikeThisHandler.java (working copy)
:
: now check out revision 772437 using the --revision switch in svn, patch
: away, and then svn up to make sure everything merges cleanly. This is a
: g
You can see what revision the patch was written for at the top of the patch,
it will look like this:
Index: org/apache/solr/handler/MoreLikeThisHandler.java
===
--- org/apache/solr/handler/MoreLikeThisHandler.java (revision 772437)
++
14 matches
Mail list logo
