On Fri, 28 Feb 2025 at 09:18, Michael Bien wrote:
>
> On 24.02.25 10:43, Neil C Smith wrote:
> > On Sun, 23 Feb 2025 at 01:35, Michael Bien wrote:
> >> On 22.02.25 18:23, Jerome Lelasseux wrote:
> >>> Is it the problem mentionned in the release notes "Windows/ARM is
> >>> currently not a fully s
On 24.02.25 10:43, Neil C Smith wrote:
> On Sun, 23 Feb 2025 at 01:35, Michael Bien wrote:
>> On 22.02.25 18:23, Jerome Lelasseux wrote:
>>> Is it the problem mentionned in the release notes "Windows/ARM is currently
>>> not a fully supported platform" ? BTW this message is really too vague to
>
On Sun, 23 Feb 2025 at 01:35, Michael Bien wrote:
> On 22.02.25 18:23, Jerome Lelasseux wrote:
> > Is it the problem mentionned in the release notes "Windows/ARM is currently
> > not a fully supported platform" ? BTW this message is really too vague to
> > be useful...
>
> it is intentionally ke
Hi,
On 22.02.25 18:23, Jerome Lelasseux wrote:
> Hi,
>
> Just updated POM with RELEASE250, it was
> working fine with 240.
>
> App shuts down during init procedure with no error, except the new INFO
> messages related to SecurityManager, see below.
set ||-DTopSecurityManager.disable=true (#8169
Hi,
Just updated POM with RELEASE250, it was
working fine with 240.
App shuts down during init procedure with no error, except the new INFO
messages related to SecurityManager, see below.
Is it the problem mentionned in the release notes "Windows/ARM is currently not
a fully supported platform
