Is it intentional that the Lucene.NET Jira notifications are being sent to
java-dev instead of lucene-net-dev, or is this just a Jira configuration
cut/paste mistake?
: Date: Sat, 17 Jun 2006 04:34:30 + (GMT+00:00)
: From: AqD (JIRA) [EMAIL PROTECTED]
: Reply-To: java-dev@lucene.apache.org
:
On Saturday 17 June 2006 01:33, markharw00d wrote:
That's a long-winded way of saying -1 unless I hear of any arguments
which are based on something much more substantial than 1.5 makes
coding easier.
As for coding convenience from 1.4: last time I had a look there was
not a single assert
Hi Chris,
I don't think this is intentional. Something is broken in the JIRA setup.
I have posted this email on general@incubator.apache.org to see if folks
there may know what's the problem and fix it.
Thanks for noticing
-- George
-Original Message-
From: Chris Hostetter
Until there is a free java 5 alternative, it would be nice to have a
clean compile in 1.4. We might also consider waiting until gcj does the
1.5 move, since some of us are loving the native binaries, particularly
on x86_64.
How else can you index billions of documents (aside from expensive
I think the problem right now isn't whether we are going to have 1.5
code or not. We will eventually have to have 1.5 code anyways. But
we need a sound plan that will make the transition easy. I believe
the transition from 1.4 to 1.5 is not an over night thing.
Secondly can we specifically
--- Robert Engels [EMAIL PROTECTED] wrote:
I think you should port Lucene to MS-DOS...
If your app can't move beyond MS-DOS, then you stick
with version 1.9 (or
2.0 in this case).
If you can't innovate and move forward, you die.
Java has a GREAT history of supporting prior
versions.
Thanks Hoss.
If this is the case, who ever has the karma to fix this, can you take care
of it?
Also, I can't figure out how to assign, close or even edit a JIRA issue
opened against Lucene.Net. For example, take a look at:
http://issues.apache.org/jira/browse/LUCENENET-6 and I can't see
Tatu Saloranta wrote on 06/17/2006 06:54 AM:
And it's
bit curious as to what the current mad rush regarding
migration is -- beyond the convenience and syntactic
sugar, only the concurrency package seems like a
tempting immediate reason?
The only people who keep bringing up these
Chuck, you nailed it!
This reverse view is really what brings clarity, at least to me. It boils down
to the question Who is loosing what?
Move to 1.5: some people will not have an oportunity to use new cool features
that will come in 2.x versions. So they know the feeling, they cannot use
Hello again,
the discussion went quiet well but there is no solution for the
problem using multiple gdata server instances behind a load balancer.
I will definitely stick to my own token, using the jsession id I will
tie myself to a particular server instance. Not all servers
replicate sessions
10 matches
Mail list logo
