Do you know if there is an issue with the "allow" class approach if
multiple projects adopt that technique? E.g. if Netbeans or Groovy
also have an allow class, will that cause a split package violation or
since it isn't really referenced except for those early JDKs, that we
should be okay? I will
Hello Stefan,
On 26/11/22 11:33 pm, Stefan Bodewig wrote:
On 2022-11-19, Stefan Bodewig wrote:
while running all tests locally I realized
https://github.com/apache/ant/pull/194 introduces a bug when tars have
an encoding set. You can see this with UntarTest failing. A multibyte
encoding like U
Hello Stefan,
On 18/11/22 2:40 pm, Stefan Bodewig wrote:
On 2022-11-16, Jaikiran Pai wrote:
Users can still use the current released Ant version against these
recent Java versions, but they additionally have to set a system
property while launching Ant to allow setting the security
manager. An
Hello ewh,
Thank you for these experiments and reporting the results. This
certainly helped me decide which way to go about it. When I had
initially tried using "allow" as a Java class (as done in NetBeans), I
was unsure if that would be the right way to go. It didn't feel clean
and I thought
