For starters - CartesianPolyFilterBuilder.GetBoxShape() is not an exact
port - do you remember why?
Anyway, if it was never fully ported as you say maybe I'll just go ahead
and complete that
For your reference, here are 2 failing tests which pass in Java Lucene (can
send the java file) -
One more thing - what's the deal with ChainedFilter? I can see a commit by
DIGY on 7/7/2011 but it seems to have been removed since?
On Mon, Apr 23, 2012 at 11:06 AM, Itamar Syn-Hershko ita...@code972.comwrote:
For starters - CartesianPolyFilterBuilder.GetBoxShape() is not an exact
port - do
If anyone is familiar with the CMS, something happened to the download page
(formatting is screwed up), but it's exactly like the other pages. I could use
another pair of eyes on it. ~P
I'll take a look at it.
On Mon, Apr 23, 2012 at 1:28 PM, Prescott Nasser geobmx...@hotmail.comwrote:
If anyone is familiar with the CMS, something happened to the download
page (formatting is screwed up), but it's exactly like the other pages. I
could use another pair of eyes on it. ~P
It's in a weird place. And for the 3.0.3 version, its easiest to find the
code in the tags, rather than branches.
http://svn.apache.org/viewvc/lucene/java/tags/lucene_3_0_3/contrib/misc/src/java/org/apache/lucene/misc/
On Mon, Apr 23, 2012 at 2:20 PM, Prescott Nasser
Hi Andi,
thanks for getting back on this issue.
Lucene 3.6 just got released a few days ago. Apart from your patch, the
PyLucene 3.6 release is ready. I'm about to go offline (email only) for a
week.
Let's revisit this patch then (first week of May). It's not blocking the
release
right
Hi All,
I am pretty new to Lucene and Pylucene. This is a problem when I am using
pylucene to write a customized analyzer, to tokenize text in to bigrams.
The code for analyzer class is:
class BiGramShingleAnalyzer(PythonAnalyzer):
[
https://issues.apache.org/jira/browse/SOLR-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259402#comment-13259402
]
Sami Siren commented on SOLR-3038:
--
bq. Having a java client that reads from an old server
[
https://issues.apache.org/jira/browse/SOLR-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259425#comment-13259425
]
Dawid Weiss commented on SOLR-3161:
---
bq. I swear I ran the tests before committing (which
Andreas W created SOLR-3395:
---
Summary: FieldStreamDataSource should handle null fields
Key: SOLR-3395
URL: https://issues.apache.org/jira/browse/SOLR-3395
Project: Solr
Issue Type: Improvement
Tommaso Teofili created SOLR-3396:
-
Summary: ClientUtils appendMap can suffer NPE
Key: SOLR-3396
URL: https://issues.apache.org/jira/browse/SOLR-3396
Project: Solr
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SOLR-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas W updated SOLR-3395:
Description:
The {{FieldStreamDataSource}} currently throws a {{DataImportHandlerException}}
if a field
[
https://issues.apache.org/jira/browse/SOLR-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated SOLR-3396:
--
Affects Version/s: (was: 3.6)
4.0
ClientUtils appendMap can
[
https://issues.apache.org/jira/browse/SOLR-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-2020:
--
Attachment: SOLR-2020-log-typo.patch
There's a small typo printing CommonsHttpSolrServer in the log
[
https://issues.apache.org/jira/browse/SOLR-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259464#comment-13259464
]
Jan Høydahl commented on SOLR-3394:
---
Good catch. Would you attempt a patch for 3.6.1 ?
Erick Erickson created SOLR-3397:
Summary: Insure that Replication and Solr Cloud are compatible
Key: SOLR-3397
URL: https://issues.apache.org/jira/browse/SOLR-3397
Project: Solr
Issue Type:
[
https://issues.apache.org/jira/browse/SOLR-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259574#comment-13259574
]
Mark Miller commented on SOLR-3397:
---
bq. Since SolrCloud takes this functionality over
[
https://issues.apache.org/jira/browse/SOLR-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259575#comment-13259575
]
Mark Miller commented on SOLR-3038:
---
+1 on changing the default, +1 on keeping XML.
I agree whenever we say not version XXX we ought to provide details
of why (and/or link to the Jira issue).
But, I don't think the output truncation problem (on a slowish
terminal) with ant 1.8.3 motivated putting that not ant 1.8.x in
Solr's README.txt... I'm not sure why it says that.
Mike
Marek Dabrowski created SOLR-3398:
-
Summary: Using solr.UUIDField give - Caused by:
org.apache.solr.common.SolrException: Invalid UUID String: '1'
Key: SOLR-3398
URL:
[
https://issues.apache.org/jira/browse/SOLR-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259581#comment-13259581
]
Erick Erickson commented on SOLR-3397:
--
I phrased it poorly, I'm aware that SolrCloud
On Mon, Apr 23, 2012 at 8:49 AM, Michael McCandless
luc...@mikemccandless.com wrote:
I agree whenever we say not version XXX we ought to provide details
of why (and/or link to the Jira issue).
There's no jira issue, just that users would see ant 1.7, junit 1.7
or whatever and try ant 1.8 and
On Mon, Apr 23, 2012 at 9:00 AM, Robert Muir rcm...@gmail.com wrote:
On Mon, Apr 23, 2012 at 8:49 AM, Michael McCandless
luc...@mikemccandless.com wrote:
I agree whenever we say not version XXX we ought to provide details
of why (and/or link to the Jira issue).
Finally, at least the junit
[
https://issues.apache.org/jira/browse/SOLR-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259585#comment-13259585
]
Steven Rowe commented on SOLR-3161:
---
bq.I used the IntelliJ test runner for all of Solr
[
https://issues.apache.org/jira/browse/LUCENE-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259598#comment-13259598
]
Michael McCandless commented on LUCENE-4010:
Hmm, true.
But I think never
[
https://issues.apache.org/jira/browse/LUCENE-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259599#comment-13259599
]
Michael McCandless commented on LUCENE-4011:
Thanks Robert! So nice to have
Robert Muir created LUCENE-4015:
---
Summary: move icu collation integration to analysis.icu.collation
package
Key: LUCENE-4015
URL: https://issues.apache.org/jira/browse/LUCENE-4015
Project: Lucene -
[
https://issues.apache.org/jira/browse/LUCENE-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259607#comment-13259607
]
Robert Muir commented on LUCENE-4011:
-
Two broken links left and we can kick this one
[
https://issues.apache.org/jira/browse/SOLR-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259609#comment-13259609
]
Shawn Heisey commented on SOLR-3393:
I've been working on this. I've come to realize
[
https://issues.apache.org/jira/browse/LUCENE-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259613#comment-13259613
]
Robert Muir commented on LUCENE-4012:
-
Yeah a sketch (maybe just Term and Boolean or
[
https://issues.apache.org/jira/browse/SOLR-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259618#comment-13259618
]
Claudio R commented on SOLR-3360:
-
Hi Mikhail,
I didn´t apply the SOLR-3360.path. The my
I've had a lingering frustration with the recent blowup due to the
solr-commons-csv Maven artifact (SOLR-3204). We've worked around the
particular issue (we now hide the dependency)...
But in thinking it over, and avoiding rehashing all the technical
details, what bothers me most about what
[
https://issues.apache.org/jira/browse/LUCENE-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4015:
Attachment: LUCENE-4015.patch
patch after 'svn move
[
https://issues.apache.org/jira/browse/SOLR-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas W updated SOLR-3381:
Attachment: (was: FieldStreamDataSource.java)
FieldStreamDataSource should support CLOBs
[
https://issues.apache.org/jira/browse/SOLR-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas W updated SOLR-3381:
Attachment: FieldStreamDataSource.java
FieldStreamDataSource should support CLOBs
I understand your point Rob. But given your point of view, wouldn't it be
sufficient for the README to simply say download Ant 1.7 and… without
explicitly telling the user *not* to use Ant 1.8, which is suggestive of a
particular problem with the newer version? You didn't tell them *not* to
[
https://issues.apache.org/jira/browse/SOLR-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Matheis (steffkes) resolved SOLR-3301.
-
Resolution: Fixed
Committed in r1329263
Migrate
[
https://issues.apache.org/jira/browse/LUCENE-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259639#comment-13259639
]
Robert Muir commented on LUCENE-4011:
-
The last solr broken link (on java7, on java6,
[
https://issues.apache.org/jira/browse/LUCENE-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259644#comment-13259644
]
Robert Muir commented on LUCENE-4011:
-
I added an exclusion for this one, and enabled
[
https://issues.apache.org/jira/browse/LUCENE-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-4011.
-
Resolution: Fixed
Check for broken documentation links in hudson
On Mon, Apr 23, 2012 at 10:37 AM, Smiley, David W. dsmi...@mitre.org wrote:
I understand your point Rob. But given your point of view, wouldn't it be
sufficient for the README to simply say download Ant 1.7 and… without
explicitly telling the user *not* to use Ant 1.8, which is suggestive of
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/13414/
1 tests failed.
REGRESSION:
org.apache.solr.cloud.LeaderElectionIntegrationTest.testSimpleSliceLeaderElection
Error Message:
We didn't find a new leader! 7003 was shutdown, but it's still showing as the
leader
Stack
On Apr 23, 2012, at 11:19 AM, Robert Muir wrote:
On Mon, Apr 23, 2012 at 10:37 AM, Smiley, David W. dsmi...@mitre.org wrote:
I understand your point Rob. But given your point of view, wouldn't it be
sufficient for the README to simply say download Ant 1.7 and… without
explicitly telling
On Mon, Apr 23, 2012 at 11:31 AM, Smiley, David W. dsmi...@mitre.org wrote:
Is there anything preventing Ant 1.8 being the release we advise people to
use? After all, Ant 1.8 was already on my Mac after I had grabbed dev
tools extras; I'm not sure when I last explicitly installed it.
Yes:
[
https://issues.apache.org/jira/browse/LUCENE-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3887:
Attachment: LUCENE-3887.patch
initial patch: just hooks into lucene's 'javadocs-lint' (but also a
On Apr 23, 2012, at 10:14 AM, Michael McCandless wrote:
I think, to fix this, we (the Apache Lucene PMC) should stop
officially posting artifacts to Maven ourselves. I think it's great
if Steve (and/or others) continue to do so, just outside of the Apache
Lucene project and outside of the
Dear Caleb,
Thanks for the sample - as usual code says more than thousand words .-)
The API really looks MUCH simpler than the current lucene facet API (as far as
I can tell from my first steps is quite complex).
With initial tests, the algorithm is about 100 faster in C++ than when
I think, to fix this, we (the Apache Lucene PMC) should stop
officially posting artifacts to Maven ourselves.
-1
I'm not happy that we're having this conversation again.
I personally don't have the resources to set up continuous integration for
this, and I think that's a requirement that
when I see ' viral' in one of these debates, I get frustrated. please
state an actual practical problem, not a scare word.
publishing to central should be a central concern of this pmc, as an
ever-growing multitude uses gradle or ivy or maven or some other
consumer.
if you want a second
I would like to commit SOLR-3361 to 3.6 in case there is a 3.6.1. Should I
start a new 3.6.1 section in changes.txt? Does it just go under 4.0 or 3.0
with a note that it is in the 3.6 branch also (but not released)?
James Dyer
E-Commerce Systems
Ingram Content Group
(615) 213-4311
But in thinking it over, and avoiding rehashing all the technical
details, what bothers me most about what happened is that the Lucene
PMC is/was held accountable for having released code in another
project's namespace, yet, none of us realized we had done so. We are
I don't know how maven
Did I miss adding 3.6.1 sections to any of the CHANGES files? If so,
this was just a mistake.
they should be present in the 3.6.x bugfix branch:
http://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_3_6/
As far as trunk, when backporting bugs to these bugfix branches,
before we've also
That's not what I meant. I meant why don't we test against Ant 1.8 and make
*that* the version we recommend? It is the latest Ant release, after all.
Someone has to do the work, thats all. It would be nice in my opinion,
we would also have some new features available.
For what it's worth
Dawid Weiss created LUCENE-4016:
---
Summary: Check if all the packaging/ development tasks work with
latest Ant 1.8.x and switch to ant 1.8.x as the officially supported build
platform.
Key: LUCENE-4016
URL:
On Apr 23, 2012, at 1:00 PM, Benson Margulies wrote:
when I see ' viral' in one of these debates, I get frustrated. please
state an actual practical problem, not a scare word.
It's not really a scare word - its just the reason I have been against Maven as
part of our core project - I mean
I agree with David. The maven error was not earth shattering --
working within the PMC was a good thing for the community at large.
We made the requested changes within a few days now things are better.
Imagining a parallel world where the PMC was not involved turns out
much worse for many
ok, sorry, I read viral as the classic anti-maven slam. sorry for the noise.
On Apr 23, 2012, at 1:14 PM, Mark Miller markrmil...@gmail.com wrote:
On Apr 23, 2012, at 1:00 PM, Benson Margulies wrote:
when I see ' viral' in one of these debates, I get frustrated. please
state an actual
On Mon, Apr 23, 2012 at 1:10 PM, Dawid Weiss
dawid.we...@cs.put.poznan.pl wrote:
That's not what I meant. I meant why don't we test against Ant 1.8 and
make *that* the version we recommend? It is the latest Ant release, after
all.
Someone has to do the work, thats all. It would be nice in
[
https://issues.apache.org/jira/browse/SOLR-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-398.
Resolution: Fixed
In trunk (4.x), FieldType now returns the interface IndexableField
Thanks for doing some preliminary checks. Like I said, I'm not against
it, in fact I think I have an open issue somewhere to upgrade :)
Damn, I probably filed a duplicate then.
I could also test some platforms and especially packaging.
Not to worry, I can do this -- run a task, change a
On Apr 23, 2012, at 1:00 PM, Benson Margulies wrote:
if you want a second volunteer to care and feed you have me.
I do feel better the more people that are contributing - at the same time that
scares me too ;) The world moves closer and closer to where I *must* eventually
contribute to these
On Mon, Apr 23, 2012 at 1:29 PM, Dawid Weiss
dawid.we...@cs.put.poznan.pl wrote:
Definitely not the early ones because they were buggy. 1.8.3 seems
relatively fresh (February 29th, 2012), so I'd say 1.8.2 (2010-12-20)?
This is a long delay from 1.8.2 to 1.8.3... just peeked at the rel.
notes
[
https://issues.apache.org/jira/browse/SOLR-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer resolved SOLR-3361.
--
Resolution: Fixed
Committed.
Trunk: r1329337
3.6 Branch: r1329351
Also put a note on the wiki that
Ryan McKinley created SOLR-3399:
---
Summary: distribute/assume log4j logging rather then JUL
Key: SOLR-3399
URL: https://issues.apache.org/jira/browse/SOLR-3399
Project: Solr
Issue Type:
[
https://issues.apache.org/jira/browse/SOLR-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Matheis (steffkes) updated SOLR-3367:
Attachment: SOLR-3367.patch
So, how about this one?
The Handling of
Ryan McKinley created SOLR-3400:
---
Summary: Solr needs independent lib folders for solrj and core
Key: SOLR-3400
URL: https://issues.apache.org/jira/browse/SOLR-3400
Project: Solr
Issue Type:
[
https://issues.apache.org/jira/browse/LUCENE-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259762#comment-13259762
]
Michael McCandless commented on LUCENE-3994:
bq. so all the time is spent in
[
https://issues.apache.org/jira/browse/SOLR-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259765#comment-13259765
]
Ryan McKinley commented on SOLR-3400:
-
I made this issue as a followup to SOLR-3358,
Mark,
As penance for my initial snappish response, here is a bit of
additional (I hope) constructive commentary, which may or may not make
you feel any better. As a mere occasional patch contributor I accept
that the decision should reflect the PMC as a whole, not especially my
view.
Publishing
[
https://issues.apache.org/jira/browse/LUCENE-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259774#comment-13259774
]
Michael McCandless commented on LUCENE-4013:
How about simply removing this
On Mon, Apr 23, 2012 at 1:45 PM, Benson Margulies bimargul...@gmail.com wrote:
Publishing artifacts benefits users; I acknowledge that you accept
that, and are weighing it against costs. Taking on this publication
process is like any adding support for any other additional
infrastructure in
How do we handle situations like
https://issues.apache.org/jira/browse/XERCESJ-1257 (open for 5 years,
still not incorporated in a release), without doing hackish things
(releasing someone elses code, sucking their entire codebase into
ours), or relying upon Uwe Schindler to come up with
Jamie Johnson created SOLR-3401:
---
Summary: Solr Core Admin view is not visible unless multiple cores
already exist
Key: SOLR-3401
URL: https://issues.apache.org/jira/browse/SOLR-3401
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jamie Johnson updated SOLR-3401:
Description: The new web gui does not show the Core Admin view unless there
are already multiples
On Mon, Apr 23, 2012 at 2:07 PM, Benson Margulies bimargul...@gmail.com wrote:
How do we handle situations like
https://issues.apache.org/jira/browse/XERCESJ-1257 (open for 5 years,
still not incorporated in a release), without doing hackish things
(releasing someone elses code, sucking their
[
https://issues.apache.org/jira/browse/SOLR-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259794#comment-13259794
]
Ryan McKinley commented on SOLR-3367:
-
better -- some things to consider
* i don't
On Mon, Apr 23, 2012 at 2:10 PM, Robert Muir rcm...@gmail.com wrote:
On Mon, Apr 23, 2012 at 2:07 PM, Benson Margulies bimargul...@gmail.com
wrote:
How do we handle situations like
https://issues.apache.org/jira/browse/XERCESJ-1257 (open for 5 years,
still not incorporated in a release),
On Mon, Apr 23, 2012 at 2:10 PM, Robert Muir rcm...@gmail.com wrote:
On Mon, Apr 23, 2012 at 2:07 PM, Benson Margulies bimargul...@gmail.com
wrote:
How do we handle situations like
https://issues.apache.org/jira/browse/XERCESJ-1257 (open for 5 years,
still not incorporated in a release),
On Mon, Apr 23, 2012 at 11:17 AM, Benson Margulies
bimargul...@gmail.com wrote:
On Mon, Apr 23, 2012 at 2:10 PM, Robert Muir rcm...@gmail.com wrote:
On Mon, Apr 23, 2012 at 2:07 PM, Benson Margulies bimargul...@gmail.com
wrote:
How do we handle situations like
On Mon, Apr 23, 2012 at 2:17 PM, Benson Margulies bimargul...@gmail.com wrote:
If it's a maven project, you do the same thing, patching the pom to
shade to change the packages if you want, or just changing the
coordinates.
You publish the results to central via OSSRH under your coordinates.
On Mon, Apr 23, 2012 at 2:20 PM, Robert Muir rcm...@gmail.com wrote:
On Mon, Apr 23, 2012 at 2:17 PM, Benson Margulies bimargul...@gmail.com
wrote:
If it's a maven project, you do the same thing, patching the pom to
shade to change the packages if you want, or just changing the
coordinates.
On Mon, Apr 23, 2012 at 2:27 PM, Benson Margulies bimargul...@gmail.com wrote:
How do you know it's done 'appropriately' in your scenario? You could
have had just as many board members up your nose by using your
ant/github procedure and depositing the resulting bundle on Apache
'dist' as an
[
https://issues.apache.org/jira/browse/LUCENE-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-4013:
---
Attachment: LUCENE-4013.patch
Patch, just making the IWC set/get package private,
On Mon, Apr 23, 2012 at 2:32 PM, Robert Muir rcm...@gmail.com wrote:
On Mon, Apr 23, 2012 at 2:27 PM, Benson Margulies bimargul...@gmail.com
wrote:
How do you know it's done 'appropriately' in your scenario? You could
have had just as many board members up your nose by using your
ant/github
On Mon, Apr 23, 2012 at 2:40 PM, Benson Margulies bimargul...@gmail.com wrote:
On Mon, Apr 23, 2012 at 2:32 PM, Robert Muir rcm...@gmail.com wrote:
On Mon, Apr 23, 2012 at 2:27 PM, Benson Margulies bimargul...@gmail.com
wrote:
How do you know it's done 'appropriately' in your scenario? You
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/13420/
1 tests failed.
REGRESSION: org.apache.solr.handler.TestReplicationHandler.test
Error Message:
Backup success not detected:?xml version=1.0 encoding=UTF-8? response
lst name=responseHeaderint name=status0/intint
On Mon, Apr 23, 2012 at 2:43 PM, Robert Muir rcm...@gmail.com wrote:
On Mon, Apr 23, 2012 at 2:40 PM, Benson Margulies bimargul...@gmail.com
wrote:
On Mon, Apr 23, 2012 at 2:32 PM, Robert Muir rcm...@gmail.com wrote:
On Mon, Apr 23, 2012 at 2:27 PM, Benson Margulies bimargul...@gmail.com
[
https://issues.apache.org/jira/browse/SOLR-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259843#comment-13259843
]
Mikhail Khludnev commented on SOLR-3360:
Claudio,
patched sources are
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/2314/
1 tests failed.
REGRESSION: org.apache.solr.handler.TestReplicationHandler.test
Error Message:
Backup success not detected:?xml version=1.0 encoding=UTF-8? response
lst name=responseHeaderint name=status0/intint
On Mon, Apr 23, 2012 at 3:02 PM, Benson Margulies bimargul...@gmail.com wrote:
That's right. If you, Rob Muir, just so happen to set up a github
project with a fix to Xerces, and I, Benson Margulies, just happen to
help you publish it to Maven Central, then the PMC, without (much)
fear of
This is a test bug. I am committing a fix...
James Dyer
E-Commerce Systems
Ingram Content Group
(615) 213-4311
-Original Message-
From: Apache Jenkins Server [mailto:jenk...@builds.apache.org]
Sent: Monday, April 23, 2012 2:09 PM
To: dev@lucene.apache.org
Subject: [JENKINS]
[
https://issues.apache.org/jira/browse/LUCENE-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-4013:
---
Attachment: LUCENE-4013.patch
New patch, making a few more classes package
[
https://issues.apache.org/jira/browse/LUCENE-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259856#comment-13259856
]
Robert Muir commented on LUCENE-4013:
-
+1
DWPTpool shouldnt be
On Mon, Apr 23, 2012 at 3:09 PM, Robert Muir rcm...@gmail.com wrote:
On Mon, Apr 23, 2012 at 3:02 PM, Benson Margulies bimargul...@gmail.com
wrote:
That's right. If you, Rob Muir, just so happen to set up a github
project with a fix to Xerces, and I, Benson Margulies, just happen to
help
Yep, sure. You don't need a property, btw., there is a condition for that --
antversion atleast=1.8.2 /
wrap it into a fail and you're set.
D.
On Mon, Apr 23, 2012 at 7:33 PM, Robert Muir rcm...@gmail.com wrote:
On Mon, Apr 23, 2012 at 1:29 PM, Dawid Weiss
dawid.we...@cs.put.poznan.pl
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/13421/
1 tests failed.
FAILED: org.apache.solr.handler.TestReplicationHandler.test
Error Message:
Backup success not detected:?xml version=1.0 encoding=UTF-8? response
lst name=responseHeaderint name=status0/intint
On Mon, Apr 23, 2012 at 3:23 PM, Benson Margulies bimargul...@gmail.com wrote:
Rob, did you mean 'Benson' by 'you' in that sentence? If so, I'm
really sorry if I've given you the impression I think that that
there's anything amiss with 3.6.0. All I meant to say was that, over
the long haul, if
[
https://issues.apache.org/jira/browse/SOLR-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259868#comment-13259868
]
Claudio R commented on SOLR-3360:
-
Hi Mikhail,
I did checkout from:
[
https://issues.apache.org/jira/browse/SOLR-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259868#comment-13259868
]
Claudio R edited comment on SOLR-3360 at 4/23/12 7:42 PM:
--
Hi
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/13422/
1 tests failed.
FAILED: org.apache.solr.handler.TestReplicationHandler.test
Error Message:
Backup success not detected:?xml version=1.0 encoding=UTF-8? response
lst name=responseHeaderint name=status0/intint
1 - 100 of 181 matches
Mail list logo
