On 4/5/2020 9:52 PM, Ernie Rael wrote:
On 4/5/2020 11:21 AM, Kenneth Fogel wrote:
should not the Run command be effectively identical to Run Maven but
with a goal from nbactions.xml?
... experimentation would indicate that the defaultGoal is not needed
for javafx. I'd hazard to guess that improvements in maven and/or NB
over the last years have helped smooth out some of the rough edges,
like with populating the repository.
I think I was a bit optimistic. The answer seems to be: behavior depend
on the maven project, in particular its pom.xml. The "Run command" is
really not related to "Run Maven".
Creating "NewProject > JavaWithMaven > Java Application" gives you an
essentially empty pom and no nbactions. Then "Project > properties >
Actions; Actions: Run project" shows you what NB does by default for its
run button/action; any changes or additions made in this properties
dialog are reflected/saved in nbactions.xml. I guess the mapping of
NetBeans buttons/menu-items to items in "Actions" is supposed to be
intuitive.
This note was prompted because while looking at some other issues, I ran
across a change that was made to javafx-maven-plugin a month ago, this
line was added for jlink
@Execute(phase = LifecyclePhase.PROCESS_CLASSES)
Which causes download/compilation first for jlink. (this was already
present for javafx:run)
-ernie
IMHO, if a project created through "Project > NewProject > ..." didn't
populate the repository with dependencies as needed, then an issue
should be filed.
-ernie
Behaviour is a little different for web applications where Run Maven
is still needed followed by NB Run to deploy.
Ken Fogel
---------------------------------------------------------------------
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
