Mailing-List: contact general-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Mime-Version: 1.0 (Apple Message framework v734)
In-Reply-To: <200509132102.08978.paul.elschot@xs4all.nl>
References: <D9FE5C58-7025-48D5-9EBE-5BBE791F0EE7@apache.org>
 <200509132102.08978.paul.elschot@xs4all.nl>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <84558AD4-00DF-46B8-AAFF-8F2275EEBAB2@ehatchersolutions.com>
Content-Transfer-Encoding: 7bit
From: Erik Hatcher <erik@ehatchersolutions.com>
Subject: Re: Lucene issue tracker moved to JIRA; LUCENE-352 not patched;
 cannot create lucene issue.
Date: Tue, 13 Sep 2005 15:35:33 -0400
To: general@lucene.apache.org


On Sep 13, 2005, at 3:02 PM, Paul Elschot wrote:
> On Tuesday 13 September 2005 14:45, Erik Hatcher wrote:
>
>> cross-posting to all the Lucene e-mail lists
>>
>> The Lucene issue tracking system has migrated from Bugzilla to JIRA.
>> Please use the new system for all issue tracking activities from this
>> point forward:
>>
>>      http://issues.apache.org/jira/browse/LUCENE
>>
>
> I'd like to raise an issue for lucene, but the lucene is not listed  
> as a
> project in the 'addressing' list for creating issues.
> (lucene4c is listed there.)

It's actually there, but listed as "Java Lucene", not just "Lucene".

> The issue is that this patch SpanNotQuery has not been applied:
> http://issues.apache.org/jira/browse/LUCENE-352
>
> Should I raise another issue to the JIRA maintainers that no Lucene
> issue can be raised? When so, how do I do that?

Perhaps we should get "Java Lucene" renamed to "Lucene - Java" on  
JIRA to that it sorts properly with Lucene4c.  I'll see how feasible  
that is.

     Erik