BTW - looking at the JavaFX archetype resources[1], there's
javafx-maven-plugin configured ...
... which could nicely plug into
https://issues.apache.org/jira/browse/NETBEANS-5394 that will be
probably implemented.
Additional action mappings would be then activated by e.g. plugin
presence in POM. Seems to me quite similar to changing the archetype
itself - but NB IDE would then inject its own actions on the fly, and
the user can customize them.
If looks interesting, share your requirements in NETBEANS-5394.
[1]
https://github.com/openjfx/javafx-maven-archetypes/blob/master/javafx-archetype-simple/src/main/resources/archetype-resources/pom.xml
Dne 21. 04. 21 v 21:21 Ernie Rael napsal(a):
IMHO, NB should
"own" that archetype, publish, and maintain it
Couldn't agree more.
But here's one case study that shows some of the problems that might be
faced.
When I fixed javafx-maven to "run/debug out of the box", I created a
very small independent (not a fork) github project for javafx maven
archetypes, published it to maven central, to replace the ones (from
gluon) used by NetBeans.
I think the PR that used those archetypes was merged somewhat by
accident, since there was immediate objection from some senior PMC
members (it stayed in, probably because there were frequent posts about
it not working; and there's the permission/forgiveness pov). I think the
objections primarily came from a desire to depend more on using 3rd
party stuff and also to encourage bundlers to customize and include
NetBeans.
But using 3rd party maven archetypes is not well supported in NetBeans.
For example see the issue "Extend ArchetypeWizards.definedArchetype to
include optional nbactions"
https://issues.apache.org/jira/browse/NETBEANS-3104. Since I provided
the maven archetype I was able to include an nbactions. BTW, being able
to provide an nbactions.xml is not sufficient; some executions had to be
added to the pom.xml. And then I opened a PR on the the 3rd party
archetypes. The idea was that if the NetBeans issue 3104 was fixed so
that nbactions could be specified *and* the 3rd party had the new
executions added to the pom.xml, then NetBeans could stop using my
archetype. There was some initial discussion and updates to the PR, then
it sat there and was finally merged, as is, after a *year*. And in the
meantime, a profile execution was added to the pom used by NetBeans,
sigh. FYI: https://github.com/openjfx/javafx-maven-archetypes/pull/10
The point is that depending on a 3rd party project for functionality
that NetBeans provides is a problem. But there is push back to provide
even simple maven archetypes. And, at least possibly until now, little
interest in supplying archetypes from NetBeans project.
It's understandable that there's a push to get some support from outside
the project, considering that NetBeans is such a huge project. It seems
it will be years, if ever, that there's a sufficient support team built
to really take care of it through apache. I'm glad there's still new
stuff going in and it's disappointing that [at times] base 8.2 seems
barely supported.
-ernie
On 4/21/2021 10:56 AM, Will Hartung wrote:
I touched on this talking about the EJB new project support and how it's
currently broken.
Fundamental to this is that the IDE relies on the Maven archetype
templating system to generate project artifacts. It also wraps that
process
up in some wizard code, and it may well do some other things, I haven't
gone into it that deeply.
However, the archetype ownership is, to me, a core issue.
It seems untoward for the IDE to have "core" functionality that
depends on
external artifacts.
Simply put, if someone wanted to change the archetype for a project, in
this case, an Apache/NB committer can not do that. The actual owner of
the
archetype has to do that.
It's kind that they share that with the NB community, but IMHO, NB should
"own" that archetype, publish, and maintain it, rather than relying on an
external source.
But I do not know what or if there is a process for accepting these kinds
of artifacts and getting them published to the maven repositories. Many
apache projects certainly publish to Maven Central, I don't know if NB
does
or not (is the Lookup library published, for example?).
I'm hardly an expert on archetype authoring or publishing.
Just curious what others feel about this and what perhaps a path forward
would be.
Regards,
Will Hartung
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
