My inclination would be to put the javadoc somewhere, anywhere, ideally
netbeans.apache.org/javadoc/9.0 -- we need them to be available as soon as
possible, and if there's a better place for them somewhere else later,
let's do that when the time is right.

Gj

On Fri, Sep 14, 2018 at 12:54 PM, Neil C Smith <[email protected]>
wrote:

> On Fri, 14 Sep 2018 at 08:32, Neil C Smith <[email protected]> wrote:
> > On Fri, 14 Sep 2018, 08:07 Geertjan Wielenga,
> <[email protected]> wrote:
> >>
> >> Great. And your questions should be answerable by Neil who should be
> able
> >> to look at this today.
> >
> >
> > Yes, going to look shortly. I'm thinking of proposing a slightly
> different approach now that control of the domain is here (or about to be)
> >
> > Out of interest, what else is on bits.nb except JavaDoc if anything?
>
> Well, to at least partly answer my own question we've got Maven
> artefacts on there.  Not sure what else?
>
> My thought is given the size of the docs, and difference to how we
> might want to build / host, that we keep the docs separate from the
> main website build entirely.  And as the domain is moving, host as now
> on bits.netbeans.org as soon as feasible.  So, we request another git
> repo (incubator-netbeans-website-bits or
> incubator-netbeans-website-docs) with connected site to be hosted at
> bits.netbeans.org and proxy back to the current Oracle hosted docs for
> 404s - the older docs, Maven, etc. in the same way we've been
> discussing for the main website.  It might also be a good test for
> doing that! :-)
>
> We can start by manually checking in the JavaDoc per release (well,
> for 9.0) then look at automating as a second step?  Need to think
> whether we still want to host dev docs this way.
>
> So, a few questions -
>
> * Does the above sound OK?  Ring any alarm bells?  Should I go talk to
> infra?
> * How does one actually build the JavaDoc for a release?  I seem to be
> missing something about the right parameters here!  It's also missing
> 8.2 in the previous releases.
> * Could the Jenkins build task for releases be adapted to build the
> docs at the same time as sources and binaries?
>
> 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
>
>
>
>

Reply via email to