Thanks for the update. We have some workarounds in the Groovy codebase too.
I'll try to tidy them up too once this has settled.
Thanks again, Paul.
On Mon, May 15, 2023 at 10:08 PM Jaikiran Pai wrote:
> Hello Paul,
>
> On 12/12/22 5:30 am, Paul King wrote:
> > Do you know if there is an issue
Hello Paul,
On 12/12/22 5:30 am, Paul King wrote:
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
On 2022-12-11, Jaikiran Pai wrote:
> On 26/11/22 11:33 pm, Stefan Bodewig wrote:
>> On 2022-11-19, Stefan Bodewig wrote:
>> Finding A solution was a nice puzzle, but that doesn't mean we have to
>> use it.
> I had a look at that commit and the PR discussion where the initial
> fix was made. I
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
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.
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 UTF16 may contain NUL bytes inside of the "normal"
Hello Stefan,
On 19/11/22 10:41 pm, Stefan Bodewig wrote:
On 2022-11-18, Stefan Bodewig wrote:
On my personal TODO list there are a few minor things like Java 20
removing another target option that we may want to tell users
about. Nothing of this is critical AFAIR and shouldn't hold up a
On 2022-11-18, Stefan Bodewig wrote:
> On my personal TODO list there are a few minor things like Java 20
> removing another target option that we may want to tell users
> about. Nothing of this is critical AFAIR and shouldn't hold up a release
> if I don't get to them soon enough.
I'm through
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. Ant's mainline code has changes where it does the
Hello everyone,
We last released Ant more than a year back. During that period we have
had some good amount of bug fixes and changes that have gone in. Plus,
Java 18 and beyond was released in the meantime where setting the
security manager isn't allowed by default (Ant sets it). Users can
11 matches
Mail list logo
