See http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/8/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/LUCENE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476527
]
Dan Zivkovic commented on LUCENE-819:
-
The workaround is not practical. It would force me to handle the null case
[
https://issues.apache.org/jira/browse/LUCENE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476522
]
Hoss Man commented on LUCENE-819:
-
i agree with Yonik ... the javadocs for Term don't make it clear that text
can't
[
https://issues.apache.org/jira/browse/LUCENE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476506
]
Yonik Seeley commented on LUCENE-819:
-
I'm not sure it's a good idea adding extra checks for things that may be u
[
https://issues.apache.org/jira/browse/LUCENE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476496
]
Steven Parkes commented on LUCENE-819:
--
Can you say anymore about why it was impossible? What if Term checked fo
[
https://issues.apache.org/jira/browse/LUCENE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476484
]
Dan Zivkovic commented on LUCENE-819:
-
p.s. How do I delete attachment #2?
> NullPointerException in Term.compar
[
https://issues.apache.org/jira/browse/LUCENE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476483
]
Dan Zivkovic commented on LUCENE-819:
-
We use Lucene on content that is often strange and exciting, and we get al
[
https://issues.apache.org/jira/browse/LUCENE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Zivkovic updated LUCENE-819:
Attachment: TestTerm.java
Unit test class.
> NullPointerException in Term.compareTo()
> --
[
https://issues.apache.org/jira/browse/LUCENE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Zivkovic updated LUCENE-819:
Attachment: lucene-819.patch
Added unit test.
> NullPointerException in Term.compareTo()
> ---
[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-794:
---
Attachment: spanhighlighter2.patch
Patch version 2
Changed to correct build.xml, removed some unneed
Hi,
I am wondering about the exposure (or not) of FieldCache in the
documentation. FieldCache is used by Lucene, internally, for sort purposes.
Being an interface, it is also exposed as public API, but there seems to be
no pointers/documentation suggesting to use it. Well, except for a brief
ment
[
https://issues.apache.org/jira/browse/LUCENE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-812.
---
Resolution: Fixed
Fix Version/s: 2.2
> Unable to set LockFactory implementatio
[
https://issues.apache.org/jira/browse/LUCENE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476386
]
Michael McCandless commented on LUCENE-818:
---
I'm planning on adding o.a.l.store.AlreadyClosedException.
B
[
https://issues.apache.org/jira/browse/LUCENE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476373
]
Steven Parkes commented on LUCENE-818:
--
Shades of LUCENE-686. It'd be nice to agree on that one, too (though it'
[
https://issues.apache.org/jira/browse/LUCENE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476360
]
Michael McCandless commented on LUCENE-818:
---
I see, so IndexInput indeed does not track isClosed. It's not
[
https://issues.apache.org/jira/browse/LUCENE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen resolved LUCENE-813.
Resolution: Fixed
Fix Version/s: 2.2
Lucene Fields: [Patch Available] (was: [Patch Avail
[
https://issues.apache.org/jira/browse/LUCENE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476315
]
Hoss Man commented on LUCENE-819:
-
Dan: can you elaborate on how you encountered this NPE? ... Terms shouldn't
typic
[
https://issues.apache.org/jira/browse/LUCENE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476312
]
Steven Parkes commented on LUCENE-819:
--
H ... this patch makes Term#compareTo support Terms with null text.
"Doug Cutting" <[EMAIL PROTECTED]> wrote:
> Michael McCandless wrote:
> > "Steven Parkes" <[EMAIL PROTECTED]> wrote:
> >> Is the idea that resolved issues are also closed at release?
> >
> > Good point, I think that is right?
>
> Yes, that is the convention I use.
OK I will go make that bulk c
Michael McCandless wrote:
"Steven Parkes" <[EMAIL PROTECTED]> wrote:
Is the idea that resolved issues are also closed at release?
Good point, I think that is right?
Also, this is, to my mind, the motivating case for Jira's bulk edit
feature, and in particular, its option to inhibit the send
Michael McCandless wrote:
"Steven Parkes" <[EMAIL PROTECTED]> wrote:
Is the idea that resolved issues are also closed at release?
Good point, I think that is right?
Yes, that is the convention I use.
Doug
-
To unsubscribe,
"Steven Parkes" <[EMAIL PROTECTED]> wrote:
> Is the idea that resolved issues are also closed at release?
Good point, I think that is right?
I think this means getting all issues with Status=Resolved
and "Fix For"=2.1 (I see 41 such issues) and then doing a
bulk-change to close them?
Mike
[
https://issues.apache.org/jira/browse/LUCENE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476240
]
Grant Ingersoll commented on LUCENE-818:
FWIW: Some of the other Readers (actually, IndexInput) are undefined
Is the idea that resolved issues are also closed at release?
-Original Message-
From: Michael McCandless [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 27, 2007 9:01 AM
To: java-dev@lucene.apache.org
Subject: Re: making 2.1 a "Released Version" in JIRA?
"Yonik Seeley" <[EMAIL PROTEC
"Yonik Seeley" <[EMAIL PROTECTED]> wrote:
> On 2/27/07, Michael McCandless <[EMAIL PROTECTED]> wrote:
> > The issues are LUCENE-814, LUCENE-796, LUCENE-510 and LUCENE-372.
> >
> > Are there any objections to bumping the fix versions of these to 2.2?
> > (I can also choose to "ignore" the 4 issues
[
https://issues.apache.org/jira/browse/LUCENE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-372:
--
Fix Version/s: (was: 2.1)
2.2
> Unmatched right parentheses trun
[
https://issues.apache.org/jira/browse/LUCENE-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-510:
--
Fix Version/s: (was: 2.1)
2.2
> IndexOutput.writeString() should
[
https://issues.apache.org/jira/browse/LUCENE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-814:
--
Fix Version/s: (was: 2.1)
2.2
> javacc on Win32 (cygwin) creates
[
https://issues.apache.org/jira/browse/LUCENE-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-796:
--
Fix Version/s: (was: 2.1)
2.2
> Change Visibility of fields[] in
On 2/27/07, Michael McCandless <[EMAIL PROTECTED]> wrote:
The issues are LUCENE-814, LUCENE-796, LUCENE-510 and LUCENE-372.
Are there any objections to bumping the fix versions of these to 2.2?
(I can also choose to "ignore" the 4 issues but I think we should move
to 2.2 instead).
Sounds fine.
[
https://issues.apache.org/jira/browse/LUCENE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Zivkovic updated LUCENE-819:
Attachment: lucene-819.patch
This is an "svn diff" describing the fix for bug #819.
> NullPointerE
NullPointerException in Term.compareTo()
Key: LUCENE-819
URL: https://issues.apache.org/jira/browse/LUCENE-819
Project: Lucene - Java
Issue Type: Bug
Components: Index
Environment:
I noticed in JIRA that "2.1" is still listed under "Unreleased
Versions".
I think it's simple to fix; we just have to "Release" it on the
Administration page for project Lucene:
http://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12310110
So I started down this path, but, it
[
https://issues.apache.org/jira/browse/LUCENE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-811.
---
Resolution: Fixed
Fix Version/s: 2.2
This is resolved. If we do a 2.1.1 then
[
https://issues.apache.org/jira/browse/LUCENE-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alastair Maw updated LUCENE-551:
Only the 1.9.1 release is still broken:
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/a
[
https://issues.apache.org/jira/browse/LUCENE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476091
]
Hoss Man commented on LUCENE-814:
-
i *think* the right solution is to leave the .jj and .java files with
svn:eol-sty
36 matches
Mail list logo
