I agree. I don't think this can be made optional. We want to deliver the
javadocs whenever a merge is performed against master, right?
Building javadoc in my box takes about 30 minutes, but this is so
because you need to build the IDE before generating the javadocs (that's
why I thought it would be a good idea to add it to
incubator-netbeans-linux job, immediately after the build finishes).
If nobody oposes I'll add this by the end of the day to the job, try it
out, and then report here how longer the build is.
Cheers,
Antonio
El 10/12/2018 a las 12:35, Neil C Smith escribió:
On Mon, 10 Dec 2018, 11:00 Geertjan Wielenga
<[email protected] wrote:
Sounds great. Does that add a lot of time to the build, could it be run
optionally i.e., not part of the standard automated run, assuming it takes
a long time?
I'm not sure optional is an option given the plan for using this. Be good
to keep an eye on times and be prepared to revert for a plan B though, but
the bulk of the time for generating Javadoc from scratch appears to be
tasks already done in the build task.
Ideally this should also go in the release build task? We need to ship the
Javadoc zip alongside source and convenience binaries for NB10.
Best wishes,
Neil
---------------------------------------------------------------------
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
