On Wed, 31 Mar 2021 12:47:50 GMT, Aleksei Efimov wrote:
>> Current fix tries to tackle an issue with URL connection referencing
>> non-existing Jar file entries:
>> If an entry that doesn't exist is specified in an URL connection the
>> underlying Jar file is still cached even if an exception i
On Wed, 31 Mar 2021 12:47:50 GMT, Aleksei Efimov wrote:
>> Current fix tries to tackle an issue with URL connection referencing
>> non-existing Jar file entries:
>> If an entry that doesn't exist is specified in an URL connection the
>> underlying Jar file is still cached even if an exception i
> Current fix tries to tackle an issue with URL connection referencing
> non-existing Jar file entries:
> If an entry that doesn't exist is specified in an URL connection the
> underlying Jar file is still cached even if an exception is thrown after
> that. Such behavior prevents the caller, for
On Wed, 31 Mar 2021 11:24:02 GMT, Daniel Fuchs wrote:
>> Current fix tries to tackle an issue with URL connection referencing
>> non-existing Jar file entries:
>> If an entry that doesn't exist is specified in an URL connection the
>> underlying Jar file is still cached even if an exception is
On Tue, 30 Mar 2021 11:30:48 GMT, Aleksei Efimov wrote:
> Current fix tries to tackle an issue with URL connection referencing
> non-existing Jar file entries:
> If an entry that doesn't exist is specified in an URL connection the
> underlying Jar file is still cached even if an exception is th
Current fix tries to tackle an issue with URL connection referencing
non-existing Jar file entries:
If an entry that doesn't exist is specified in an URL connection the underlying
Jar file is still cached even if an exception is thrown after that. Such
behavior prevents the caller, for instance,
