https://bz.apache.org/bugzilla/show_bug.cgi?id=66110
Jaikiran Pai <jaiki...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #2 from Jaikiran Pai <jaiki...@apache.org> ---
Hello Ralf, this need not necessarily be an Ant issue. The error message
doesn't currently tell which jar in the classpath is having such an entry. A
fix has been recently made in Java upstream (19 version which hasn't yet been
released) where that jar name will be printed in cases like these. Until then,
you might have to experiment with the classpath to figure out which jar is
causing this issue. What would be interesting is whether such a jar was
generated by Ant in first place. If not, then I think this is more to do with
the jar itself than Ant.
If you aren't able to narrow down the jar which causes this problem, perhaps
you could provide us a (simplified) reproducer/build instructions which might
help us reproduce this issue?
--
You are receiving this mail because:
You are the assignee for the bug.
