lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Rutherglen" <jason.rutherg...@gmail.com>
Subject Re: serialVersionUID issue between 2.3 and 2.4
Date Tue, 02 Dec 2008 02:18:04 GMT
Hi Mike,

Can you build and release a 2.4 jar using the 2.3 build environment?

> Besides having to remember to change the serialVersionUID, are there any
known downsides to setting it explicitly?

As far as I know it's all good.

Jason

On Mon, Dec 1, 2008 at 6:11 PM, Michael McCandless <
lucene@mikemccandless.com> wrote:

>
> Jason Rutherglen wrote:
>
>  if you don't set serialVersionUID yourself, then java assigns a
>>>
>> rather volatile one for you
>>
>> True however the Java specification defines how the serialVersionUID
>> should
>> be created in the event it's not defined.  The caveat being it's not
>> strictly enforced and so Sun alternative compilers may decide to change
>> how
>> it's created (from what I've read).  Base classes like Term and Query
>> don't
>> change very often so we may want to settle on a serialVersionUID for these
>> top level classes.
>>
>
> Makes sense.  Besides having to remember to change the serialVersionUID,
> are
> there any known downsides to setting it explicitly?
>
> Lucene sets it for 2 sources now (RAMFile & RAMDirectory).
>
>  Was a different compiler used for the 2.4 release compared to 2.3?
>>
>
> Likely, yes (two different people, Michael and Mike (me!), in different
> envs,
> did the releases).
>
> Mike
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

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