If I understand Dragans point right, the warning comes when analyzing the code.
Not just running Ivy.
So the normal user won't see the warning. Maybe we should implement a warning?
Jan
> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai [mailto:jaiki...@apache.org]
> Gesendet: Mittwoch, 10. O
I agree with Stefan, at the moment I recommend ignoring those warnings.
There isn't anything else we can do (other than removing support for
pack200, which isn't a good option).
-Jaikiran
On 10/10/18 9:56 AM, Stefan Bodewig wrote:
> Hi Krzysztof
>
> I'm not actively working on Ivy so take my res
Hi Krzysztof
I'm not actively working on Ivy so take my response with a grain of
salt.
On 2018-10-09, Dragan, Krzysztof wrote:
> Hi,
> scanning latest version of Apache Ivy(2.5.0-rc-1) using jdeprscan on
> jdk11 I noticed two problems with this jar.
> These two methods using internal jdk marke
Hi,
scanning latest version of Apache Ivy(2.5.0-rc-1) using jdeprscan on jdk11 I
noticed two problems with this jar.
These two methods using internal jdk marked for removal and will be deleted:
* class org/apache/ivy/util/FileUtil uses deprecated class
java/util/jar/Pack200$Unpacker (forRem
