> On Jul 25, 2020, at 5:28 PM, Matt Sicker <boa...@gmail.com> wrote:
>
> Exactly. It’s not a general problem, but one specific to various legacy
> APIs still commonly used.
+1
>
>> On Sat, Jul 25, 2020 at 14:56 Bernd Eckenfels <e...@zusammenkunft.net>
>> wrote:
>>
>> It will only cause problems if this is registered as a service/spi/driver
>> like XML, Crypto, JDBC, Authentication and so on. For internal libraries
>> functions which don't have such global state it's fine.
>>
>> Gruss
>> Bernd
>>
>>
>> --
>> http://bernd.eckenfels.net
>> ________________________________
>> Von: Torsten Curdt <tcu...@vafer.org>
>> Gesendet: Saturday, July 25, 2020 8:29:21 PM
>> An: Commons Developers List <dev@commons.apache.org>
>> Betreff: Re: [all] When to update dependencies?
>>
>>>
>>> They’re not the same class and that’s the problem. It’s similar to
>> loading
>>> two versions of the same library in OSGi
>>
>>
>> Let's say you are dealing with
>>
>> org.vafer.Foo
>>
>> the library relocates this as
>>
>> org.apache.commons.compress.internal.org.vafer.Foo
>>
>> The library only deals with
>>
>> org.apache.commons.compress.internal.org.vafer.Foo
>>
>> They cannot get mixed up.
>> Please explain how this will cause problems.
>>
> --
> Matt Sicker <boa...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
