Note that Gluon doesn't want your nbactions.xml file, logically, because their sample projects are applicable to any IDE or non-IDE and nbactions.xml is NetBeans specific. Hence this is something that must be handled on the NetBeans side.
Unless what you're looking to do is to fork the Gluon samples, not sure if that is desirable, would be best for NetBeans to leverage the official Gluon samples and not a fork, so that we can continue benefiting from enhancements made by the Gluon team to the official samples. Gj On Fri, Feb 21, 2020 at 5:41 PM Geertjan Wielenga <[email protected]> wrote: > > https://github.com/openjfx/javafx-maven-archetypes/pull/6 > https://github.com/openjfx/javafx-maven-archetypes/pull/8 > > Gj > > > > On Fri, Feb 21, 2020 at 5:28 PM Ernie Rael <[email protected]> wrote: > >> Currently NewProject>JavaWithMaven>...JavaFXMavenArchetype... creates a >> project that doesn't just work. See >> https://issues.apache.org/jira/browse/NETBEANS-3730 and >> https://issues.apache.org/jira/browse/NETBEANS-3104 . >> >> Generally, the problem is attributed to missing nbactions.xml, but there >> is also the problem that the pom.xml doesn't support running a debugger. >> >> I've modified the gluon archetype generator to provide a nbactions and >> pom that fixes these problems. Run and debug work out of the box. >> >> Can this be published to maven central and used by NB's new project? I >> guess the main issue is finding a home for the source/maven-GroupId >> >> -ernie >> >> >> --------------------------------------------------------------------- >> 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 >> >> >> >>
