In light of suggested process use mailing list. (I'll assume the
original was lost (or maybe too lighthearted), I'll resend and add some
supporting info). I know profiling got some lovin', but to be thorough
and practice this process...
An aside to NetCAT, while creating a maven project,
On 4/7/2020 2:46 PM, Glenn Holmer wrote:
On 4/7/20 3:37 PM, Jiří Kovalský wrote:
NetBeans 12.0 brings quite some nice features in Java editing
area which nobody officially tested and signed off so far. That's why
I would like to ask if there are some kind people here who could
dedicate
On 4/6/2020 8:55 AM, Glenn Holmer wrote:
On 4/6/20 10:46 AM, Ernie Rael wrote:
It looks like you didn't use
"github.com/betanzos/javafx-maven-plugin.git" (note the 'betanzos') to
build/install the snapshot.
cenbe@greyhand:~ > history | grep "git clone"
63 2020-0
On 4/6/2020 8:28 AM, Glenn Holmer wrote:
On 4/4/20 12:24 PM, Ernie Rael wrote:
If you want to try the profiler on a javafx project, it's simple to
setup. See below. Note that the eventual solution (nbactions/pom) may
look somewhat different.
so close...
It looks like you didn't use
On 4/6/2020 11:46 AM, Glenn Holmer wrote:
On 4/6/20 11:25 AM, Ernie Rael wrote:
PS I'm putting together a solution that works with the currently
release javafx-maven-plugin, let's hope it's accepted for 12.0.
Excellent, it would be great to have FX projects fully working out of
the box
On 4/2/2020 6:31 AM, Geertjan Wielenga wrote:
Hi all,
I propose we keep things short and sweet for JavaFX in NetCAT 12.0:
https://netbeans-vm.apache.org/synergy/client/app/#/specification/452
What do we think about the above -- now that we have Ernie's great work
done on the OpenJFX
Status:
* openjfx team member betanzos has created a fix,
https://github.com/openjfx/javafx-maven-plugin/pull/76, waiting to
get PR approved. And would still need a subsequent release.
* I'm investigating a NetBeans fix that works with the current, 0.0.4,
javafx-maven-plugin
If you
With 12.0beta2,
NewProject > Java with Maven > [FXML|Simple] JavaFX Maven Archetype
(Gluon)
use hacked archetypes that include
* pom.xml with debug executions
* nbactions.xml
So the run/debug buttons work out of the box.
There is a limitation on running NetBeans on jdk1.8 and working
On 4/2/2020 8:44 AM, Glenn Holmer wrote:
On 4/2/20 9:45 AM, Ernie Rael wrote:
On 4/2/2020 7:25 AM, Glenn Holmer wrote:
On 4/2/20 9:08 AM, Ernie Rael wrote:
On 4/2/2020 6:31 AM, Geertjan Wielenga wrote:
I propose we keep things short and sweet for JavaFX in NetCAT 12.0:
https://netbeans
On 4/2/2020 8:44 AM, Glenn Holmer wrote:
On 4/2/20 9:45 AM, Ernie Rael wrote:
On 4/2/2020 7:25 AM, Glenn Holmer wrote:
On 4/2/20 9:08 AM, Ernie Rael wrote:
On 4/2/2020 6:31 AM, Geertjan Wielenga wrote:
I propose we keep things short and sweet for JavaFX in NetCAT 12.0:
https://netbeans
On 4/2/2020 11:20 PM, Ernie Rael wrote:
On 4/2/2020 8:44 AM, Glenn Holmer wrote:
After a profiling attempt, nbactions.xml has javafx: targets for run and
debug, while profile has org.codehaus.mojo:exec-maven-plugin. That's
like what run and debug originally had that didn't work, isn't
I did a PR, https://github.com/apache/netbeans/pull/2053, last night
that fixes a couple problems with the "new maven project" dialog (an
exception and a newly created project with a syntax error). I think the
PR has the wrong parent (my bad); it's parent probably should be
upstrem/master.
On 4/2/2020 7:25 AM, Glenn Holmer wrote:
On 4/2/20 9:08 AM, Ernie Rael wrote:
On 4/2/2020 6:31 AM, Geertjan Wielenga wrote:
I propose we keep things short and sweet for JavaFX in NetCAT 12.0:
https://netbeans-vm.apache.org/synergy/client/app/#/specification/452
There are four cases: IDE-JDK
In NB-16-rc, there's a PR: "Dialog parent should not be null"
https://github.com/apache/netbeans/pull/4739
Any test/feedback of changed dialogs' behavior, and observations for
dialogs that are misplaced, appreciated.
Before this change, these dialogs would show up in the center of Java's
14 matches
Mail list logo
