Den tors 30 dec. 2021 kl 18:11 skrev Neil C Smith :
> Can you reproduce the effect of removing html4j from the platform app
> fixing it?
>
>
Sorry Neil, I missed that.
Not really sure of the best way to remove html4j I ended up adding the
following (including templatesui) to the platform
On Sun, 26 Dec 2021 at 16:43, Patrik Karlström wrote:
> Can anyone else reproduce this by testing on the "new project template"
> with RELEASE113 and RELEASE126 against JDKs with and without JavaFX?
As stated in earlier reply, I can reproduce your described problem.
Can you reproduce the effect
On Fri, 24 Dec 2021 at 16:04, Laszlo Kishalmi wrote:
> I can create a Snap filtering the extra cluster out, but would that be
> really right?
Yes. I was trying to work out why you're getting different output, as
the default cluster config should be correct. Then noticed the Snap
build uses the
Thank you Laszlo,
I have now tested the edge snap, and verified that the former FX components
are gone.
And it works, sometimes...
A pattern is appearing and it looks to me that the problem indeed started
with the platform maven version RELEASE120(-1/-u1) upto and including
RELEASE126
in
Just uploaded a new package to the edge channel of Snapcraft. Please
test that one.
It is built from the same source as the previous one, just removed the
extra cluster from the packaging.
On 12/23/21 09:16, Patrik Karlström wrote:
Den tors 23 dec. 2021 kl 17:19 skrev Neil C Smith :
On
Well, the whole extra cluster is now the platform dependent JavaFx
libraries.
Also it is referenced as dependency of both the java and the nb cluster,
so the Snap contains the libraries that are defined in the build.
I can create a Snap filtering the extra cluster out, but would that be
Strange, let me check why that extra stuff is there!
On 12/23/21 09:32, Neil C Smith wrote:
On Thu, 23 Dec 2021 at 17:17, Patrik Karlström wrote:
Den tors 23 dec. 2021 kl 17:19 skrev Neil C Smith :
That's concerning! As an ASF provided binary that should not have
JavaFX pre-installed, or
On Thu, 23 Dec 2021 at 16:17, Neil C Smith wrote:
> > I have had this problem ever since in each NetBeans session when running
> > platform applications.
> > And today I had enough so I have been poking around for hours and made some
> > progress.
> > I was able to track it down to the enablement
On Thu, 23 Dec 2021 at 17:17, Patrik Karlström wrote:
> Den tors 23 dec. 2021 kl 17:19 skrev Neil C Smith :
> > That's concerning! As an ASF provided binary that should not have
> > JavaFX pre-installed, or non-disable-able. What was the directory
> > diff?
> >
> >
> The diff was large to to
Den tors 23 dec. 2021 kl 17:19 skrev Neil C Smith :
> On Thu, 23 Dec 2021 at 13:12, Patrik Karlström wrote:
> > Being a SNAP user I got his plugin unknowingly activated by default,
> > noticed this after doing a directory diff against the 12.6 binary zip.
> > I'm not able to disable it from the
On Thu, 23 Dec 2021 at 13:12, Patrik Karlström wrote:
> Bringing this one back to life after 18 months :)
:-)
> I have had this problem ever since in each NetBeans session when running
> platform applications.
> And today I had enough so I have been poking around for hours and made some
>
Bringing this one back to life after 18 months :)
I have had this problem ever since in each NetBeans session when running
platform applications.
And today I had enough so I have been poking around for hours and made some
progress.
I was able to track it down to the enablement of the plugin
12 matches
Mail list logo
