OK, feels like hacking but I found that this addition to the POM did the
trick:
```
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>3.1.1</version>
<configuration>
<source>11</source>
<target>11</target>
<sourceFileExcludes>**/module-info.java</sourceFileExcludes>
</configuration>
</plugin>
```
I found this in someone else’s struggles
https://stackoverflow.com/questions/55676341/java-11-12-javadoc-with-maven-results-in-not-generating-javadocs-for-tests
A gist with everything including corresponding nbactions.xml :
https://gist.github.com/dgreen/e1ae4636f311d38758dafdd7b0decf0f (all
built for Group ID: edu.uab.dgreen ArtifactID: fxdemo) source from the
Java Application with Maven using javafx-archetype-simple .
Thanks for the help. There are probably simpler versions and I hope one
can be found to make part of a future NetBeans so that it is easier to
start new projects.
Dave
On 7 Oct 2019, at 17:20, David Green wrote:
I am in this camp (of wanting to generate javadoc formatted pages. I
had been through these references (that you suggested — thanks
though).
I have now discovered that javadoc:javadoc works (either within
NetBeans or at the command line with Maven) if the module-info.java
file does NOT exist but, of course, the rest of my build system wants
it there to define the module.
(Perhaps unrelated but…) Looking at the old Jigsaw project it
appears that the file structure included the module name as a
directory entry right below source which is now visually there in the
NetBeans IDE but the actual directory is src/main/java/….
Dave
On 7 Oct 2019, at 14:13, Geertjan Wielenga wrote:
And also for generating your own, that's a Maven task:
https://maven.apache.org/plugins/maven-javadoc-plugin/
Gj
On Mon, Oct 7, 2019 at 9:11 PM Geertjan Wielenga
<geert...@apache.org>
wrote:
Maybe this:
https://stackoverflow.com/questions/54278159/javafx-11-in-netbeans-10-with-maven-has-no-sources-javadocs
Gj
On Mon, Oct 7, 2019 at 9:01 PM David Green <dgreen...@gmail.com>
wrote:
Thanks.
Any on hints on generating Javadoc?
Dave
On 6 Oct 2019, at 8:59, Geertjan Wielenga wrote:
For debugging, this works:
https://stackoverflow.com/questions/56197372/i-cant-debug-an-application-using-netbeans-11-with-javafx-12
Gj
On Sun, Oct 6, 2019 at 7:05 AM Geertjan Wielenga
<geert...@apache.org>
wrote:
However, take a look at Samples | OpenJFX in 11.1.
Those two samples have the nbactions file that contains the debug
target
too.
Gj
On Sun, Oct 6, 2019 at 6:58 AM Geertjan Wielenga
<geert...@apache.org>
wrote:
Yes, that is my aim too, it will happen, probably not for 11.2.
Gj
On Sun, Oct 6, 2019 at 6:53 AM David Green <dgreen...@gmail.com>
wrote:
Yes.
That would be most useful.
Long term, it would be nice to have this be set up when
selecting a
project type.
Thanks,
Dave
On 5 Oct 2019, at 23:35, Geertjan Wielenga wrote:
So, the project runs as described in:
https://www.youtube.com/watch?v=8xaRwqcKPSI?
You want another YouTube clip just like that showing how to
set up
Debug
and Javadoc goals in NetBeans?
Gj
On Sun, Oct 6, 2019 at 4:12 AM David Green
<dgreen...@gmail.com>
wrote:
Using Netbeans 11.2.beta2 (although same issues seem to apply
to
11.1
release),
Using the example from https://openjfx.io/openjfx-docs/ for
modules
with
Maven and NetBeans which is also highlighted in the video
https://www.youtube.com/watch?v=8xaRwqcKPSI&feature=youtu.be,
this
allows one to run code with openJavaFX quite nicely with Run
Project
but
Debug Project and Generate JavaDoc fail.
It would be nice if these and perhaps a build image of some
sort
were
automatically accomplishable by the base Maven pom. It would
greatly
help folks start using NetBeans for new projects.
I have found a variant of Mathew Dusome’s code
<
