commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "simon.kitching@chello.at" <simon.kitch...@chello.at>
Subject Re: [lang] Java 5
Date Thu, 12 Jun 2008 15:30:01 GMT
Ralph Goers schrieb:
>
>
> James Carman wrote:
>> On Thu, Jun 12, 2008 at 10:45 AM, Ralph Goers
>> <Ralph.Goers@dslextreme.com> wrote:
>>
>>  
>>> This confuses me. Doesn't the fact that since the code will no
>>> longer run on
>>> a pre-1.5 JDK mean that compatibility is broken, even if not a
>>> single line
>>> of code changes? (Yes - I know that we technically only release
>>> source so in
>>> that case it could be recompiled, but I work with Maven). In any
>>> case, I
>>> expect that the code will only compile with a 1.5 compiler anyway.
>>>
>>>     
>>
>> Just because the new Commons Lang is compiled against 1.5 doesn't mean
>> that older code that depends on it won't be able to use it.
>>
>>   
> It does if that older code is trying to run in a 1.4 or 1.3 JVM. 

There are two kinds of compatibility:
 (a) being able to drop a new lib into an existing system without
changing anything
 (b) being able to write a new app combining existing libs

(a) is called a bugfix release. We're not talking about that. And for
anything other than a bugfix release, people should expect to need to
update other bits of their system (including upgrading to a new Java
release) if they want to upgrade to a new lib.

(b) is what we are talking about here. There are cases where people are
left with absolutely *no* possible way of combining a set of libraries
into a single application. This can happen if lib A works *only* with
lang x.x and lib B works *only* with lang y.y, and the two lang versions
have the same package name.

Regards,
Simon



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message