lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anshum <ansh...@gmail.com>
Subject Re: Reg two versions of lucene on the same machine
Date Wed, 19 Nov 2008 07:02:11 GMT
Hi Shireesha,
I'm not sure as to what is it that you have been using, but 'm kinda sure
that you'd have to check for deprecated things as well as improved ones
while upgrading.. 1.2 to 2.4 is a huge jump certainly, with compound index
structure etc. coming into place.
You would have to try it and check if your code works the same(I doubt it
would though).
About having 2 versions of lucene on the same machine, ofcourse yes, it is
as good as having 2 (or more) java jars.
I am presuming that you place your lucene core jar in the project library
directory and not in the jre/lib/ext directory, in which case you would have
issues placing the 2 jars.
It would be better of you completely remove lucene jars from the implicit
included library dir, and place them in a different folder (and include that
in your classpath).

Hope that solves a bit of your doubt (atleast) !
--
Anshum Gupta
Naukri Labs!
http://ai-cafe.blogspot.com

The facts expressed here belong to everybody, the opinions to me. The
distinction is yours to draw............


On Wed, Nov 19, 2008 at 11:57 AM, <Shireesha.Katkoor@cognizant.com> wrote:

>
> Hi,
>
>
>
> I am trying to upgrade the version of Lucene from 1.2 to 2.4. Can we do
> this directly?
>
>  Is it possible to have two versions of Lucene on the same machine.?
>
>
>
> Shireesha
>
>
>
>
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Any unauthorized review, use, disclosure, dissemination, forwarding,
> printing or copying of this email or any action taken in reliance on this
> e-mail is strictly prohibited and may be unlawful.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message