One idea for whoever takes this on is we could link from our website to https://www.javadoc.io/ when we start creating maven artefacts, and we just have to deploy the javadocs to https://search.maven.org/
Regards John On Thu, 23 Aug 2018 at 13:30, Geertjan Wielenga <[email protected]> wrote: > Does someone want to take on this task and propose a solution and publish > the javadoc? > > https://issues.apache.org/jira/browse/NETBEANS-1176 > > Thanks, > > Gj > > On Thu, Aug 9, 2018 at 4:28 AM, Antonio Vieiro <[email protected]> wrote: > > > What about > > https://github.com/apache/incubator-netbeans-website/ > > tree/master/bits.netbeans.org > > ? > > > > We have a basic setup there. > > > > I think we should try to keep the existing bits.netbeans.org domain. > > > > We can host the api documentation wherever we want, not in > > bits.netbeans.org > > necessarily, (say in foobar.netbeans.apache.org) but even if we choose > > that > > other domain, the bits.netbeans.org domain should exist and redirect to > > the > > new one. > > > > Cheers, > > Antonio > > > > > > El El mar, 7 ago 2018 a las 13:35, Geertjan Wielenga > > <[email protected]> escribió: > > > > > Hi all, > > > > > > We need to think about where to put our javadoc: > > > > > > http://bits.netbeans.org/dev/javadoc/ > > > > > > This is how to build it: > > > > > > ant -buildjavadoc > > > > > > All the javadoc is already donated, since it comes from the donated > > source > > > files. > > > > > > One of the ZIPs generated from the above consists of HTML files. > > > > > > Where/how/when can/shall we publish these? > > > > > > And this should be a standard part of the release cycle. > > > > > > Thanks, > > > > > > Gj > > > > > >
