There's https://github.com/errael/javafx-maven-archetypes. And I
deployed a SNAPSHOT so you can use it manually, not through NB (unless
NB has a "create project from random archetype" action), as per
instructions except use -DarchetypeVersion=0.0.4-SNAPSHOT. From the
README.md:
|mvn archetype:generate \ -DarchetypeGroupId=com.raelity.jfx \
-DarchetypeArtifactId=javafx-archetype-simple \ -DarchetypeVersion=0.0.4
\ -DgroupId=groupid \ -DartifactId=artifactId \ -Dversion=version|
Create a project with the archetype, open it with NetBeans, run/debug.
What to reference from the archetype defn pom is open along with what
groupid to use. That root pom.xml in github needs review, comments and
recommendations. The archetype is licensed with BSD-3, so I think that
means there's lots of flexibility on how to structure this.
-ernie
On 2/21/2020 11:07 AM, Geertjan Wielenga wrote:
OK, I agree: until the official OpenJFX samples work out of the box in
NetBeans, we should fork our own perfectly fitted for NetBeans solution.
Gj
On Fri, 21 Feb 2020 at 19:53, Ernie Rael <[email protected]> wrote:
On 2/21/2020 10:46 AM, Geertjan Wielenga wrote:
Yes, if there is more activity in those pull request discussions, we can
get it done the right way.
Gj
On Fri, 21 Feb 2020 at 19:36, Ernie Rael <[email protected]> wrote:
Do you see getting Gluon to change there stuff *and* implementing the
API change as possible for NB-12?
-ernie
What about the NB API change?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
