igine-
De : Jean-Marc Borer
Envoyé : jeudi 22 septembre 2022 11:57
À : dev@netbeans.apache.org
Objet : Re: Bringing apidoc back
Hi Eric,
Thank you for the job.
There is one thing that I am unsure to have properly understood. As a NBP
advanced user, I often refer and use the Javadoc of pr
ans-website/pull/607
>
>
> Best Regards
> Eric
>
> -Message d'origine-
> De : Jaroslav Tulach
> Envoyé : samedi 13 août 2022 12:57
> À : dev
> Objet : Re: Bringing apidoc back
>
> Amazing! Thank you for fixing the broken links.
> -jt
>
>
>
have former links via webarchive on our website.
https://github.com/apache/netbeans-website/pull/608
https://github.com/apache/netbeans-website/pull/607
Best Regards
Eric
-Message d'origine-
De : Jaroslav Tulach
Envoyé : samedi 13 août 2022 12:57
À : dev
Objet : Re: Bringing apidoc
Amazing! Thank you for fixing the broken links.
-jt
Dne po 8. 8. 2022 19:51 uživatel Eric Barboni napsal:
> Hi folks,
>
> I started a PR to clean up the api doc. The main goal is that we need
> javadoc to success with failonerror set to true. Because if it fails only
> architecture and api chan
etbeans-website/pull/608
>
> We could later reexport content if we want,
> Otherwise we can cut links from apidoc.
>
> Eric
> -Message d'origine-
> De : antonio <>
> Envoyé : lundi 8 août 2022 20:19
> À : dev@netbeans.apache.org
> Objet : Re: Bringing
content if we want,
Otherwise we can cut links from apidoc.
Eric
-Message d'origine-
De : antonio <>
Envoyé : lundi 8 août 2022 20:19
À : dev@netbeans.apache.org
Objet : Re: Bringing apidoc back
Hi Eric,
Great job!
El 8/8/22 a las 19:51, Eric Barboni escribió:
> 3) Copy from
Hi Eric,
Great job!
El 8/8/22 a las 19:51, Eric Barboni escribió:
3) Copy from webarchive to our site but I'm unsure of the copyright here.
4) other idea
4) Update the content from webarchive, rewriting/summarizing it to match
current NetBeans (for instance, many content from lexer.netbeans.
Hi folks,
I started a PR to clean up the api doc. The main goal is that we need javadoc
to success with failonerror set to true. Because if it fails only architecture
and api change are generated but not the javadoc.
The most important issue is the following :
On the master it’s currently not
