You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Antonio <an...@vieiro.net> on 2018/09/28 19:07:09 UTC
Options, options (was Re: NetBeans javadoc at Apache)
Hi all,
I'm re-reading the thread and that suggests netbeans.apache.org, but the
Confluence page suggests bits.netbeans.org. I'm confused, don't know if
we have an agreement on this. Have we?
Options are:
1- netbeans.apache.org/javadoc/[dev|9.0|10.0]
This will require a jenkins job.
2- http://bits.netbeans.org/dev/javadoc/index.html
Requires the DNS stuff being in Apache, setting up a repo and a
gitpubsub, will lose previous (5.0-8.2) javadocs.
3- http://bits.netbeans.apache.org/[dev|9.0|10.0]
New Apache subdomain, will require a repo + gitpubsub, won't lose
previous (5.0-8.2) javadocs, can then replace bits.netbeans.org
Thanks,
Antonio
On 17/09/18 14:28, Neil C Smith wrote:
> On Fri, 14 Sep 2018 at 15:22, Neil C Smith <ne...@apache.org> wrote:
>> ... and speaking of which, I have a branch of NB90 checked out, but
>> what's the magic invocation required to make a release version of the
>> JavaDoc?
>
> I put up the wiki page requested -
> https://cwiki.apache.org/confluence/display/NETBEANS/Javadoc+hosting
>
> But, with no response on the query above, not been able to work out
> doing a release version of the docs. I'm probably going to have to
> pass the baton on this one, at least with the immediate download - a
> couple more work days then no access to a computer for 10 days.
>
> Can also follow up the repo / gitpubsub query with infra if there's
> some consensus we're going that route?
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Antonio <an...@vieiro.net>.
On 03/10/18 00:10, Antonio wrote:
> Hi all,
>
> We now have https://netbeans.apache.org/javadoc/dev/index.html
>
[...]
> - Update the current jbake website jenkins job to avoid removing the
> "javadoc" directory whenever a change is published (pushing to the
> website will remove javadocs right now).
[...]
Done: we can now publish to the website as usual, by submitting PRs
against http://github.com/apache/incubator-netbeans-website
Cheers,
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Neil C Smith <ne...@apache.org>.
On Sun, 7 Oct 2018 at 10:58, Neil C Smith <ne...@apache.org> wrote:
> How about a compromise? Let's pull this and manage it in the asf-site
> branch directly as and until we have an automated approach ready?
OK, pulled to asf-site. I realise that was suggested in the PR, and
we know it at least needs to be in there. We can figure out other
branching strategies later! ;-)
I've also put in a ticket to infra -
https://issues.apache.org/jira/browse/INFRA-17114
Any concerns, please pipe up.
Geertjan, or anyone else, can you double check I've mentioned all that
is on that domain at Oracle - old Javadoc and Maven repos. Anything
else that infra should be aware of that might impact proxying?
Thanks and best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Neil C Smith <ne...@apache.org>.
Hi,
On Sun, 7 Oct 2018 at 07:32, Antonio <an...@vieiro.net> wrote:
> On 10/7/18 12:22 AM, Neil C Smith wrote:
> > I was really
> > going for the simplest and quickest approach here for immediate needs.
>
> The idea is to avoid having too many files in the master branch.
OK, I understand what you're getting at.
> If each
> release delivers about 12k files and we have 10 releases then that would
> mean having 120k files in the master branch. That's going burn my SSD.
I don't expect us to get there. This is about the simple, manual
approach for a couple of releases only. Once we have this automated
via the release process then I wouldn't expect us to have *any*
Javadoc in the master branch, just the relevant tooling - eg. a
Jenkins task to unzip the artefact(s) and push to asf-site. The
Javadocs for people to download should be in the mirror system.
How about a compromise? Let's pull this and manage it in the asf-site
branch directly as and until we have an automated approach ready?
> OTOH I understand it's easier for ASF Infra to hold the javadoc on a git
> repo, but I don't like that. I'd rather have a directory where the
> javadoc is uploaded and then published.
Yes, me too! I like the git deployment process in principle, but none
of the other things I use here currently involves pushing the build
*output* through git. In fact, I'm inclined to have two repositories
in that case - one for the build files, one only for pushing
deployment artefacts. It would stop the build output swelling the
size of the git clone for branches that are not intended to be used
locally at all.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Antonio <an...@vieiro.net>.
On 10/7/18 12:22 AM, Neil C Smith wrote:
> Hi,
>
> On Sat, 6 Oct 2018, 21:16 Antonio Vieiro, <an...@vieiro.net> wrote:
>
>> For 9.0 we could use a branch named "9.0-vc3" (same as the tag in
>> incubator-netbeans).
>
>
> I'm not sure I understand the reasoning for branching like that? Surely we
> could just as easily tag master? What's your thoughts behind it? It might
> make sense if the docs were at the root in all branches except asf-site I
> guess, but I personally dislike unrelated branches like that. I was really
> going for the simplest and quickest approach here for immediate needs.
The idea is to avoid having too many files in the master branch. If each
release delivers about 12k files and we have 10 releases then that would
mean having 120k files in the master branch. That's going burn my SSD.
I'd rather have 10 branches with 12k files each than a single master
branch with 120k files.
Of course, the asf-site will have to have 120k files, but you don't
usually checkout that branch (jenkins does that instead for publishing).
OTOH I understand it's easier for ASF Infra to hold the javadoc on a git
repo, but I don't like that. I'd rather have a directory where the
javadoc is uploaded and then published.
>
> It also reminds me, we should really have a 9.0 tag for that 9.0-vc3 commit
> in the main repo too.
>
> In fact we could update the jenkins release job
>> to push the javadoc to this new repo as well. And so on with the rest
>> of releases.
>>
>
> That's the next step I believe. But at the moment I'm not sure the
> templates are set up for that. I'd really like to understand better how
> release Javadocs were done before. IMO we should do this manually for 9 and
> 10, and then have another look.
Agreed.
Kind regards,
Antonio
>
> Best wishes,
>
> Neil
>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 4 Oct 2018 at 20:32, Geertjan Wielenga
<ge...@googlemail.com.invalid> wrote:
>
> If we want mentors to do something we need to start a new thread with
> Mentors in the subject line.
I added it to the subject line, but it seems that might not be
registering as a new thread. OK, will take 2!
Thanks,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
If we want mentors to do something we need to start a new thread with
Mentors in the subject line.
Great we’re making progress on the javadoc!
Gj
On Thursday, October 4, 2018, Neil C Smith <ne...@apache.org> wrote:
> On Thu, 4 Oct 2018 at 19:29, Neil C Smith <ne...@apache.org> wrote:
> >
> > On Thu, 4 Oct 2018 at 19:19, Antonio <an...@vieiro.net> wrote:
> > >
> > > Yep. infra.chat is awesome. You can have things solved within the
> minute!
> > >
> >
> > Hi, yes, just about to. But I was confused because according to the
> > wiki edits, infra told you to use self-serve?!
> >
>
> OK, this is something we need a mentor to action for now. Unlike the
> wiki says we can't use self-serve to create repositories.
>
> So, would it be possible to have a new repository at
> incubator-netbeans-docs? This is for the purpose of gitpubsub of
> Javadoc, on bits.netbeans.org at least initially.
>
> Thanks and best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
[Mentors] Re: NetBeans javadoc at Apache (Re: Options, options (was
Re: NetBeans javadoc at Apache))
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 4 Oct 2018 at 19:29, Neil C Smith <ne...@apache.org> wrote:
>
> On Thu, 4 Oct 2018 at 19:19, Antonio <an...@vieiro.net> wrote:
> >
> > Yep. infra.chat is awesome. You can have things solved within the minute!
> >
>
> Hi, yes, just about to. But I was confused because according to the
> wiki edits, infra told you to use self-serve?!
>
OK, this is something we need a mentor to action for now. Unlike the
wiki says we can't use self-serve to create repositories.
So, would it be possible to have a new repository at
incubator-netbeans-docs? This is for the purpose of gitpubsub of
Javadoc, on bits.netbeans.org at least initially.
Thanks and best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Neil C Smith <ne...@apache.org>.
Hi,
On Sat, 6 Oct 2018, 21:16 Antonio Vieiro, <an...@vieiro.net> wrote:
> For 9.0 we could use a branch named "9.0-vc3" (same as the tag in
> incubator-netbeans).
I'm not sure I understand the reasoning for branching like that? Surely we
could just as easily tag master? What's your thoughts behind it? It might
make sense if the docs were at the root in all branches except asf-site I
guess, but I personally dislike unrelated branches like that. I was really
going for the simplest and quickest approach here for immediate needs.
It also reminds me, we should really have a 9.0 tag for that 9.0-vc3 commit
in the main repo too.
In fact we could update the jenkins release job
> to push the javadoc to this new repo as well. And so on with the rest
> of releases.
>
That's the next step I believe. But at the moment I'm not sure the
templates are set up for that. I'd really like to understand better how
release Javadocs were done before. IMO we should do this manually for 9 and
10, and then have another look.
Best wishes,
Neil
>
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Antonio Vieiro <an...@vieiro.net>.
I was thinking we could merge to another branch instead of to master.
For 9.0 we could use a branch named "9.0-vc3" (same as the tag in
incubator-netbeans). In fact we could update the jenkins release job
to push the javadoc to this new repo as well. And so on with the rest
of releases.
We then could merge all these into asf-site for publishing.
What say?
Cheers,
Antonio
El sáb., 6 oct. 2018 a las 14:06, Neil C Smith
(<ne...@apache.org>) escribió:
>
> > On **GitHub**, Antonio <an...@vieiro.net> wrote:
> > Do we want to merge this into master? Or asf-site instead? How is web publishing set up? Can we discuss in the mailing list?
>
> OK, bringing that discussion onto the mailing list (although I do need
> to fix where the GitHub notifications are going, so may be here
> anyway! ;-) Know how to do that?)
>
> My plan was to merge to master, and then merge from there to asf-site
> when we're ready to publish. Gitpubsub is not set up for this
> repository yet - that's the next step with infra, but that also
> requires things being configured for the bits.netbeans.org domain.
>
> In the short term, I was planning on manual publishing via merge to
> asf-site after collecting to master, now and for NB10, but that may
> change if we do go with dev snapshots of the Javadoc too. We'll
> probably need a better approach to that if it monopolises the
> gitpubsub node for half an hour though. I'd rather experiment in this
> repo than the website one too - that's already grown rather a lot in
> size! And once we have the domain configured we can easily get
> existing links to snapshots working.
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Neil C Smith <ne...@apache.org>.
> On **GitHub**, Antonio <an...@vieiro.net> wrote:
> Do we want to merge this into master? Or asf-site instead? How is web publishing set up? Can we discuss in the mailing list?
OK, bringing that discussion onto the mailing list (although I do need
to fix where the GitHub notifications are going, so may be here
anyway! ;-) Know how to do that?)
My plan was to merge to master, and then merge from there to asf-site
when we're ready to publish. Gitpubsub is not set up for this
repository yet - that's the next step with infra, but that also
requires things being configured for the bits.netbeans.org domain.
In the short term, I was planning on manual publishing via merge to
asf-site after collecting to master, now and for NB10, but that may
change if we do go with dev snapshots of the Javadoc too. We'll
probably need a better approach to that if it monopolises the
gitpubsub node for half an hour though. I'd rather experiment in this
repo than the website one too - that's already grown rather a lot in
size! And once we have the domain configured we can easily get
existing links to snapshots working.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 4 Oct 2018 at 19:19, Antonio <an...@vieiro.net> wrote:
>
> Yep. infra.chat is awesome. You can have things solved within the minute!
>
Hi, yes, just about to. But I was confused because according to the
wiki edits, infra told you to use self-serve?!
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Laszlo Kishalmi <la...@gmail.com>.
Yes indeed! I'm big fan of it as well.
On 10/04/2018 11:19 AM, Antonio wrote:
> Yep. infra.chat is awesome. You can have things solved within the minute!
>
> On 04/10/18 15:16, Geertjan Wielenga wrote:
>> Any questions re infrastructure, and permissions, just pop over to
>> infra.chat and check there.
>>
>> Gj
>>
>> On Thu, Oct 4, 2018 at 3:05 PM Neil C Smith <ne...@apache.org>
>> wrote:
>>
>>> On Wed, 3 Oct 2018 at 12:44, Antonio <an...@vieiro.net> wrote:
>>>> I think it's worth exploring this path. Let me know if I can be of
>>>> help
>>>> on this.
>>>
>>> OK, looked at setting up the repo for this via self-serve as you
>>> mentioned from an earlier infra chat, but looks like we don't have
>>> permission to do that ourselves?!
>>>
>>> Best wishes,
>>>
>>> Neil
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Antonio <an...@vieiro.net>.
Yep. infra.chat is awesome. You can have things solved within the minute!
On 04/10/18 15:16, Geertjan Wielenga wrote:
> Any questions re infrastructure, and permissions, just pop over to
> infra.chat and check there.
>
> Gj
>
> On Thu, Oct 4, 2018 at 3:05 PM Neil C Smith <ne...@apache.org> wrote:
>
>> On Wed, 3 Oct 2018 at 12:44, Antonio <an...@vieiro.net> wrote:
>>> I think it's worth exploring this path. Let me know if I can be of help
>>> on this.
>>
>> OK, looked at setting up the repo for this via self-serve as you
>> mentioned from an earlier infra chat, but looks like we don't have
>> permission to do that ourselves?!
>>
>> Best wishes,
>>
>> Neil
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Any questions re infrastructure, and permissions, just pop over to
infra.chat and check there.
Gj
On Thu, Oct 4, 2018 at 3:05 PM Neil C Smith <ne...@apache.org> wrote:
> On Wed, 3 Oct 2018 at 12:44, Antonio <an...@vieiro.net> wrote:
> > I think it's worth exploring this path. Let me know if I can be of help
> > on this.
>
> OK, looked at setting up the repo for this via self-serve as you
> mentioned from an earlier infra chat, but looks like we don't have
> permission to do that ourselves?!
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Neil C Smith <ne...@apache.org>.
On Wed, 3 Oct 2018 at 12:44, Antonio <an...@vieiro.net> wrote:
> I think it's worth exploring this path. Let me know if I can be of help
> on this.
OK, looked at setting up the repo for this via self-serve as you
mentioned from an earlier infra chat, but looks like we don't have
permission to do that ourselves?!
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Antonio <an...@vieiro.net>.
Hi Neil,
I think it's worth exploring this path. Let me know if I can be of help
on this.
Cheers,
Antonio
El 03/10/2018 a las 8:38, Neil C Smith escribió:
> Hi,
>
> On Tue, 2 Oct 2018 at 23:11, Antonio <an...@vieiro.net> wrote:
>> We now have https://netbeans.apache.org/javadoc/dev/index.html
>> ...
>> Jenkins job is at
>> https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-website-javadoc/
>> the initial commit [3] is quite big: more than 13000 files and 3.3
>> million changes.
>
> OK, back at a computer and catching up! Thanks for looking at this.
> I have to say, this is exactly what I was proposing we didn't do
> though! I was suggesting a separate repository / gitpubsub process
> exactly to work around these issues, and so we didn't experiment on
> the main website. This seems to add a lot of overhead to the
> repository and the gitpubsub process for the website. And it adds the
> JBake conflict you mention. Either we need to alter the JBake build
> to not wipe this out, or we add the copying process into JBake (which
> has the benefit of working offline).
>
> I also suggested using bits.netbeans,org with proxying for this as a
> stopgap replicating the existing structure while we decided on a
> longer term plan.
>
> I was going to manually build the 9.0 Javadocs (after making a few
> release changes to the overview) and check those in, as well as
> publish the zip alongside the downloads in the mirror. Then we need
> to look at something like adding the build-javadoc into the main
> Jenkins IDE release task, so the Javadoc zip is added to the release
> files for 10, and we can then manually check into the hosting (or
> automate if we think it's worth it).
>
> If we need to host the dev Javadoc (with 3-month releases do we really
> need to *host* them??), then surely it would be better to add
> build-javadocs into other tasks that are already building the IDE, and
> then trigger a copy into the gitpubsub system. This is checking out
> and building the Javadoc on the website Jenkins node? Something tells
> me that monopolising that for half an hour at a time won't make us
> popular! :-)
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Antonio <an...@vieiro.net>.
Hi,
Adding 9.0 will require checking out the 9.0 branch, building javadoc
and publishing it. I don't think it's worth building a jenkins for this,
but it would be good having it for future NetBeans releases.
I think it's worth exploring the proxy approach Neil was talking about
in another thread. In order to do that we should know how the DNS
transfer is going.
Cheers,
Antonio
On 03/10/18 05:23, Geertjan Wielenga wrote:
> Awesome, this is great to see. If this works and is not problematic, let’s
> do it. Re adding 9.0, what is needed to do that?
>
> Gj
>
> On Wednesday, October 3, 2018, Antonio <an...@vieiro.net> wrote:
>
>> Hi all,
>>
>> We now have https://netbeans.apache.org/javadoc/dev/index.html
>>
>> This is experimental. Things may be still syncing (if you see a 404 please
>> retry). Note that we're uploading .zip files for each module ([1], [2]) as
>> well.
>>
>> Jenkins job is at https://builds.apache.org/view
>> /Incubator%20Projects/job/incubator-netbeans-website-javadoc/ the initial
>> commit [3] is quite big: more than 13000 files and 3.3 million changes.
>> Subsequent commits should be smaller now that we have moved timestamps from
>> each HTML to the CSS.
>>
>> I'm not sure we decided the order of directories, I've used javadoc/dev
>> and not dev/javadoc as in bits.netbeans.org. I think we can use the
>> "javadoc" top directory to add information about javadoc itself (for
>> instance, the definitions of API stability, that right now point to
>> wiki.netbeans.org).
>>
>> Pending stuff and questions:
>>
>> - Continue with the "proxy" alternative Neil was talking about on another
>> thread (something similar to bits.netbeans.org).
>> - Update the current jbake website jenkins job to avoid removing the
>> "javadoc" directory whenever a change is published (pushing to the website
>> will remove javadocs right now).
>> - Update nbbuild/build.xml information with a "build-javadoc" entry.
>> - Update/review the misleading message ("build-javadoc is deprecated")
>> when "ant build-javadoc" is run on a pristine clone.
>> - Inform apache infra about build length to see if this is a problem
>> (there's a single node for building all Apache websites, and ours takes
>> almost half an hour).
>> - Generate and publish 9.0 javadoc (?)
>> - See how big commits are when javadoc is regenerated (see if the
>> timestamp fix is enough or if we need to improve it).
>> - Add a hook to regenerate javadoc when something is merged to
>> incubator-netbeans#master (?)
>> - Update the javadoc initial page (overview-summary.html) to add some
>> entries to Apache 9.0 javadoc? Also change links to FAQ and mailing lists.
>>
>> Cheers,
>> Antonio
>>
>>
>> [1] An example in Apache
>> https://netbeans.apache.org/javadoc/dev/org-netbeans-lib-v8debug.zip
>>
>> [2] Same in bits.netbeans.org
>> https://bits.netbeans.org/dev/javadoc/org-netbeans-lib-v8debug.zip
>>
>> [3]
>> https://github.com/apache/incubator-netbeans-website/commit/
>> 03c1e9d2c924168ccfcaf46b968c63921aef71bb
>>
>> On 30/09/18 18:29, Antonio wrote:
>>
>>> Hi Gj,
>>>
>>> You may want to take a look at PR#930 [1], with a small fix to avoid
>>> adding timestamp to _all_ generated HTML files. This moves the timestamp
>>> info to javadoc.css instead. By doing so we will hopefully avoid adding
>>> 11349 files to each new commit when regenerating the javadoc.
>>>
>>> Note that timestamps are still included in some other files (those
>>> generated with the XSLT stylesheets), but these are just a few (as many as
>>> modules) and I think we can handle these in a future JIRA ticket.
>>>
>>> I'll try to create a Jenkins job in the coming days and continue with the
>>> javadoc demo.
>>>
>>> Kind regards,
>>> Antonio
>>>
>>> [1]
>>> https://github.com/apache/incubator-netbeans/pull/930
>>>
>>> On 30/09/18 12:46, Geertjan Wielenga wrote:
>>>
>>>> That sounds great. If I can help in some way let me know, really keen to
>>>> have our javadoc published in one way or another.
>>>>
>>>> Gj
>>>>
>>>>
>>>> On Saturday, September 29, 2018, Antonio <an...@vieiro.net> wrote:
>>>>
>>>> Ok. Let's go for the demo.
>>>>>
>>>>> First let's add the timestamp on the javadocs inside the css only (with
>>>>> a
>>>>> footnote:before { content: "${TODAY}"} or something like that), and not
>>>>> on
>>>>> every HTML.
>>>>>
>>>>> Then the new jenkins job. Monday-tuesday could be a preliminar target
>>>>> for
>>>>> the demo.
>>>>>
>>>>> Regarding javadoc.io I think they require uploading the javadoc to
>>>>> Maven
>>>>> Central first, so that'll have to wait a little until we have the Maven
>>>>> artifacts in place with the new domain.
>>>>>
>>>>> Cheers,
>>>>> Antonio
>>>>>
>>>>> On 29/09/18 10:14, Geertjan Wielenga wrote:
>>>>>
>>>>> Well, let's see that demo first, with your Jenkins job, especially since
>>>>>> you can do it quickly. Based on that, we can decide if we like that
>>>>>> approach or not, once we see it in action, and then discuss
>>>>>> alternatives
>>>>>> if
>>>>>> needed at that stage.
>>>>>>
>>>>>> Gj
>>>>>>
>>>>>> On Sat, Sep 29, 2018 at 10:00 AM Antonio <an...@vieiro.net> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On 28/09/18 22:00, Neil C Smith wrote:
>>>>>>>
>>>>>>> On Fri, 28 Sep 2018, 20:07 Antonio, <an...@vieiro.net> wrote:
>>>>>>>>
>>>>>>>> 2- http://bits.netbeans.org/dev/javadoc/index.html
>>>>>>>>
>>>>>>>>> Requires the DNS stuff being in Apache, setting up a repo and a
>>>>>>>>> gitpubsub, will lose previous (5.0-8.2) javadocs.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> No it won't. The idea is to redirect 404s back to Oracle, same as
>>>>>>>> already
>>>>>>>> discussed with infra about the main website.
>>>>>>>>
>>>>>>>>
>>>>>>> Ah, I see, so we need Oracle to set up a "legacy.bits.netbeans.org"
>>>>>>> website with the current content, right? So that all 404s that reach
>>>>>>> bits.netbeans.org end up in legacy.bits.netbeans.org. Wasn't that the
>>>>>>> plan?
>>>>>>>
>>>>>>> I recall talking something about a proxy to make the whole thing
>>>>>>> transparent to the users, but I don't know the details. Maybe you want
>>>>>>> to lead this after wednesday?
>>>>>>>
>>>>>>>
>>>>>>> And possibly not /dev to start with, just /9.0 and /10.0?
>>>>>>>>
>>>>>>>> I suggested earlier not hosting the Javadocs under
>>>>>>>> netbeans.apache.org
>>>>>>>>
>>>>>>>> at
>>>>>>>
>>>>>>> least for now. We could rethink that later, but I think keeping it
>>>>>>>> away
>>>>>>>> from JBake would be a very good idea!
>>>>>>>>
>>>>>>>>
>>>>>>> There's a misunderstanding here, I think.
>>>>>>>
>>>>>>> Hosting the javadocs at netbeans.apache.org does not require JBake at
>>>>>>> all. It's just copying the generated javadocs in a directory inside
>>>>>>> the
>>>>>>> "content" directory in the "asf-site" branch:
>>>>>>>
>>>>>>> https://github.com/apache/incubator-netbeans-website/tree/
>>>>>>> asf-site/content
>>>>>>>
>>>>>>> Adding stuff to a directory there and pushing to the "asf-site" branch
>>>>>>> should be good enough. I can set up a Jenkins job for this quickly if
>>>>>>> you want to see a demo.
>>>>>>>
>>>>>>> Anyway, shall we run a voting on the approach, including the
>>>>>>> javadocs.io
>>>>>>> idea from John?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Antonio
>>>>>>>
>>>>>>>
>>>>>>> But, yes, is there consensus / disagreement to that approach?
>>>>>>>>
>>>>>>>> Best wishes,
>>>>>>>>
>>>>>>>> Neil
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>> ------------------------------------------------------------
>>>>>>> ---------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>>>>>> For additional commands, e-mail: dev-help@netbeans.incubator.
>>>>>>> apache.org
>>>>>>>
>>>>>>> For further information about the NetBeans mailing lists, visit:
>>>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>>>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>>>>
>>>>> For further information about the NetBeans mailing lists, visit:
>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Awesome, this is great to see. If this works and is not problematic, let’s
do it. Re adding 9.0, what is needed to do that?
Gj
On Wednesday, October 3, 2018, Antonio <an...@vieiro.net> wrote:
> Hi all,
>
> We now have https://netbeans.apache.org/javadoc/dev/index.html
>
> This is experimental. Things may be still syncing (if you see a 404 please
> retry). Note that we're uploading .zip files for each module ([1], [2]) as
> well.
>
> Jenkins job is at https://builds.apache.org/view
> /Incubator%20Projects/job/incubator-netbeans-website-javadoc/ the initial
> commit [3] is quite big: more than 13000 files and 3.3 million changes.
> Subsequent commits should be smaller now that we have moved timestamps from
> each HTML to the CSS.
>
> I'm not sure we decided the order of directories, I've used javadoc/dev
> and not dev/javadoc as in bits.netbeans.org. I think we can use the
> "javadoc" top directory to add information about javadoc itself (for
> instance, the definitions of API stability, that right now point to
> wiki.netbeans.org).
>
> Pending stuff and questions:
>
> - Continue with the "proxy" alternative Neil was talking about on another
> thread (something similar to bits.netbeans.org).
> - Update the current jbake website jenkins job to avoid removing the
> "javadoc" directory whenever a change is published (pushing to the website
> will remove javadocs right now).
> - Update nbbuild/build.xml information with a "build-javadoc" entry.
> - Update/review the misleading message ("build-javadoc is deprecated")
> when "ant build-javadoc" is run on a pristine clone.
> - Inform apache infra about build length to see if this is a problem
> (there's a single node for building all Apache websites, and ours takes
> almost half an hour).
> - Generate and publish 9.0 javadoc (?)
> - See how big commits are when javadoc is regenerated (see if the
> timestamp fix is enough or if we need to improve it).
> - Add a hook to regenerate javadoc when something is merged to
> incubator-netbeans#master (?)
> - Update the javadoc initial page (overview-summary.html) to add some
> entries to Apache 9.0 javadoc? Also change links to FAQ and mailing lists.
>
> Cheers,
> Antonio
>
>
> [1] An example in Apache
> https://netbeans.apache.org/javadoc/dev/org-netbeans-lib-v8debug.zip
>
> [2] Same in bits.netbeans.org
> https://bits.netbeans.org/dev/javadoc/org-netbeans-lib-v8debug.zip
>
> [3]
> https://github.com/apache/incubator-netbeans-website/commit/
> 03c1e9d2c924168ccfcaf46b968c63921aef71bb
>
> On 30/09/18 18:29, Antonio wrote:
>
>> Hi Gj,
>>
>> You may want to take a look at PR#930 [1], with a small fix to avoid
>> adding timestamp to _all_ generated HTML files. This moves the timestamp
>> info to javadoc.css instead. By doing so we will hopefully avoid adding
>> 11349 files to each new commit when regenerating the javadoc.
>>
>> Note that timestamps are still included in some other files (those
>> generated with the XSLT stylesheets), but these are just a few (as many as
>> modules) and I think we can handle these in a future JIRA ticket.
>>
>> I'll try to create a Jenkins job in the coming days and continue with the
>> javadoc demo.
>>
>> Kind regards,
>> Antonio
>>
>> [1]
>> https://github.com/apache/incubator-netbeans/pull/930
>>
>> On 30/09/18 12:46, Geertjan Wielenga wrote:
>>
>>> That sounds great. If I can help in some way let me know, really keen to
>>> have our javadoc published in one way or another.
>>>
>>> Gj
>>>
>>>
>>> On Saturday, September 29, 2018, Antonio <an...@vieiro.net> wrote:
>>>
>>> Ok. Let's go for the demo.
>>>>
>>>> First let's add the timestamp on the javadocs inside the css only (with
>>>> a
>>>> footnote:before { content: "${TODAY}"} or something like that), and not
>>>> on
>>>> every HTML.
>>>>
>>>> Then the new jenkins job. Monday-tuesday could be a preliminar target
>>>> for
>>>> the demo.
>>>>
>>>> Regarding javadoc.io I think they require uploading the javadoc to
>>>> Maven
>>>> Central first, so that'll have to wait a little until we have the Maven
>>>> artifacts in place with the new domain.
>>>>
>>>> Cheers,
>>>> Antonio
>>>>
>>>> On 29/09/18 10:14, Geertjan Wielenga wrote:
>>>>
>>>> Well, let's see that demo first, with your Jenkins job, especially since
>>>>> you can do it quickly. Based on that, we can decide if we like that
>>>>> approach or not, once we see it in action, and then discuss
>>>>> alternatives
>>>>> if
>>>>> needed at that stage.
>>>>>
>>>>> Gj
>>>>>
>>>>> On Sat, Sep 29, 2018 at 10:00 AM Antonio <an...@vieiro.net> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> On 28/09/18 22:00, Neil C Smith wrote:
>>>>>>
>>>>>> On Fri, 28 Sep 2018, 20:07 Antonio, <an...@vieiro.net> wrote:
>>>>>>>
>>>>>>> 2- http://bits.netbeans.org/dev/javadoc/index.html
>>>>>>>
>>>>>>>> Requires the DNS stuff being in Apache, setting up a repo and a
>>>>>>>> gitpubsub, will lose previous (5.0-8.2) javadocs.
>>>>>>>>
>>>>>>>>
>>>>>>>> No it won't. The idea is to redirect 404s back to Oracle, same as
>>>>>>> already
>>>>>>> discussed with infra about the main website.
>>>>>>>
>>>>>>>
>>>>>> Ah, I see, so we need Oracle to set up a "legacy.bits.netbeans.org"
>>>>>> website with the current content, right? So that all 404s that reach
>>>>>> bits.netbeans.org end up in legacy.bits.netbeans.org. Wasn't that the
>>>>>> plan?
>>>>>>
>>>>>> I recall talking something about a proxy to make the whole thing
>>>>>> transparent to the users, but I don't know the details. Maybe you want
>>>>>> to lead this after wednesday?
>>>>>>
>>>>>>
>>>>>> And possibly not /dev to start with, just /9.0 and /10.0?
>>>>>>>
>>>>>>> I suggested earlier not hosting the Javadocs under
>>>>>>> netbeans.apache.org
>>>>>>>
>>>>>>> at
>>>>>>
>>>>>> least for now. We could rethink that later, but I think keeping it
>>>>>>> away
>>>>>>> from JBake would be a very good idea!
>>>>>>>
>>>>>>>
>>>>>> There's a misunderstanding here, I think.
>>>>>>
>>>>>> Hosting the javadocs at netbeans.apache.org does not require JBake at
>>>>>> all. It's just copying the generated javadocs in a directory inside
>>>>>> the
>>>>>> "content" directory in the "asf-site" branch:
>>>>>>
>>>>>> https://github.com/apache/incubator-netbeans-website/tree/
>>>>>> asf-site/content
>>>>>>
>>>>>> Adding stuff to a directory there and pushing to the "asf-site" branch
>>>>>> should be good enough. I can set up a Jenkins job for this quickly if
>>>>>> you want to see a demo.
>>>>>>
>>>>>> Anyway, shall we run a voting on the approach, including the
>>>>>> javadocs.io
>>>>>> idea from John?
>>>>>>
>>>>>> Thanks,
>>>>>> Antonio
>>>>>>
>>>>>>
>>>>>> But, yes, is there consensus / disagreement to that approach?
>>>>>>>
>>>>>>> Best wishes,
>>>>>>>
>>>>>>> Neil
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>> ------------------------------------------------------------
>>>>>> ---------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>>>>> For additional commands, e-mail: dev-help@netbeans.incubator.
>>>>>> apache.org
>>>>>>
>>>>>> For further information about the NetBeans mailing lists, visit:
>>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>>>
>>>> For further information about the NetBeans mailing lists, visit:
>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: NetBeans javadoc at Apache (Re: Options, options (was Re:
NetBeans javadoc at Apache))
Posted by Neil C Smith <ne...@apache.org>.
Hi,
On Tue, 2 Oct 2018 at 23:11, Antonio <an...@vieiro.net> wrote:
> We now have https://netbeans.apache.org/javadoc/dev/index.html
>...
> Jenkins job is at
> https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-website-javadoc/
> the initial commit [3] is quite big: more than 13000 files and 3.3
> million changes.
OK, back at a computer and catching up! Thanks for looking at this.
I have to say, this is exactly what I was proposing we didn't do
though! I was suggesting a separate repository / gitpubsub process
exactly to work around these issues, and so we didn't experiment on
the main website. This seems to add a lot of overhead to the
repository and the gitpubsub process for the website. And it adds the
JBake conflict you mention. Either we need to alter the JBake build
to not wipe this out, or we add the copying process into JBake (which
has the benefit of working offline).
I also suggested using bits.netbeans,org with proxying for this as a
stopgap replicating the existing structure while we decided on a
longer term plan.
I was going to manually build the 9.0 Javadocs (after making a few
release changes to the overview) and check those in, as well as
publish the zip alongside the downloads in the mirror. Then we need
to look at something like adding the build-javadoc into the main
Jenkins IDE release task, so the Javadoc zip is added to the release
files for 10, and we can then manually check into the hosting (or
automate if we think it's worth it).
If we need to host the dev Javadoc (with 3-month releases do we really
need to *host* them??), then surely it would be better to add
build-javadocs into other tasks that are already building the IDE, and
then trigger a copy into the gitpubsub system. This is checking out
and building the Javadoc on the website Jenkins node? Something tells
me that monopolising that for half an hour at a time won't make us
popular! :-)
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
NetBeans javadoc at Apache (Re: Options, options (was Re: NetBeans
javadoc at Apache))
Posted by Antonio <an...@vieiro.net>.
Hi all,
We now have https://netbeans.apache.org/javadoc/dev/index.html
This is experimental. Things may be still syncing (if you see a 404
please retry). Note that we're uploading .zip files for each module
([1], [2]) as well.
Jenkins job is at
https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-website-javadoc/
the initial commit [3] is quite big: more than 13000 files and 3.3
million changes. Subsequent commits should be smaller now that we have
moved timestamps from each HTML to the CSS.
I'm not sure we decided the order of directories, I've used javadoc/dev
and not dev/javadoc as in bits.netbeans.org. I think we can use the
"javadoc" top directory to add information about javadoc itself (for
instance, the definitions of API stability, that right now point to
wiki.netbeans.org).
Pending stuff and questions:
- Continue with the "proxy" alternative Neil was talking about on
another thread (something similar to bits.netbeans.org).
- Update the current jbake website jenkins job to avoid removing the
"javadoc" directory whenever a change is published (pushing to the
website will remove javadocs right now).
- Update nbbuild/build.xml information with a "build-javadoc" entry.
- Update/review the misleading message ("build-javadoc is deprecated")
when "ant build-javadoc" is run on a pristine clone.
- Inform apache infra about build length to see if this is a problem
(there's a single node for building all Apache websites, and ours takes
almost half an hour).
- Generate and publish 9.0 javadoc (?)
- See how big commits are when javadoc is regenerated (see if the
timestamp fix is enough or if we need to improve it).
- Add a hook to regenerate javadoc when something is merged to
incubator-netbeans#master (?)
- Update the javadoc initial page (overview-summary.html) to add some
entries to Apache 9.0 javadoc? Also change links to FAQ and mailing lists.
Cheers,
Antonio
[1] An example in Apache
https://netbeans.apache.org/javadoc/dev/org-netbeans-lib-v8debug.zip
[2] Same in bits.netbeans.org
https://bits.netbeans.org/dev/javadoc/org-netbeans-lib-v8debug.zip
[3]
https://github.com/apache/incubator-netbeans-website/commit/03c1e9d2c924168ccfcaf46b968c63921aef71bb
On 30/09/18 18:29, Antonio wrote:
> Hi Gj,
>
> You may want to take a look at PR#930 [1], with a small fix to avoid
> adding timestamp to _all_ generated HTML files. This moves the timestamp
> info to javadoc.css instead. By doing so we will hopefully avoid adding
> 11349 files to each new commit when regenerating the javadoc.
>
> Note that timestamps are still included in some other files (those
> generated with the XSLT stylesheets), but these are just a few (as many
> as modules) and I think we can handle these in a future JIRA ticket.
>
> I'll try to create a Jenkins job in the coming days and continue with
> the javadoc demo.
>
> Kind regards,
> Antonio
>
> [1]
> https://github.com/apache/incubator-netbeans/pull/930
>
> On 30/09/18 12:46, Geertjan Wielenga wrote:
>> That sounds great. If I can help in some way let me know, really keen to
>> have our javadoc published in one way or another.
>>
>> Gj
>>
>>
>> On Saturday, September 29, 2018, Antonio <an...@vieiro.net> wrote:
>>
>>> Ok. Let's go for the demo.
>>>
>>> First let's add the timestamp on the javadocs inside the css only
>>> (with a
>>> footnote:before { content: "${TODAY}"} or something like that), and
>>> not on
>>> every HTML.
>>>
>>> Then the new jenkins job. Monday-tuesday could be a preliminar target
>>> for
>>> the demo.
>>>
>>> Regarding javadoc.io I think they require uploading the javadoc to Maven
>>> Central first, so that'll have to wait a little until we have the Maven
>>> artifacts in place with the new domain.
>>>
>>> Cheers,
>>> Antonio
>>>
>>> On 29/09/18 10:14, Geertjan Wielenga wrote:
>>>
>>>> Well, let's see that demo first, with your Jenkins job, especially
>>>> since
>>>> you can do it quickly. Based on that, we can decide if we like that
>>>> approach or not, once we see it in action, and then discuss
>>>> alternatives
>>>> if
>>>> needed at that stage.
>>>>
>>>> Gj
>>>>
>>>> On Sat, Sep 29, 2018 at 10:00 AM Antonio <an...@vieiro.net> wrote:
>>>>
>>>>
>>>>>
>>>>> On 28/09/18 22:00, Neil C Smith wrote:
>>>>>
>>>>>> On Fri, 28 Sep 2018, 20:07 Antonio, <an...@vieiro.net> wrote:
>>>>>>
>>>>>> 2- http://bits.netbeans.org/dev/javadoc/index.html
>>>>>>> Requires the DNS stuff being in Apache, setting up a repo and a
>>>>>>> gitpubsub, will lose previous (5.0-8.2) javadocs.
>>>>>>>
>>>>>>>
>>>>>> No it won't. The idea is to redirect 404s back to Oracle, same as
>>>>>> already
>>>>>> discussed with infra about the main website.
>>>>>>
>>>>>
>>>>> Ah, I see, so we need Oracle to set up a "legacy.bits.netbeans.org"
>>>>> website with the current content, right? So that all 404s that reach
>>>>> bits.netbeans.org end up in legacy.bits.netbeans.org. Wasn't that the
>>>>> plan?
>>>>>
>>>>> I recall talking something about a proxy to make the whole thing
>>>>> transparent to the users, but I don't know the details. Maybe you want
>>>>> to lead this after wednesday?
>>>>>
>>>>>
>>>>>> And possibly not /dev to start with, just /9.0 and /10.0?
>>>>>>
>>>>>> I suggested earlier not hosting the Javadocs under
>>>>>> netbeans.apache.org
>>>>>>
>>>>> at
>>>>>
>>>>>> least for now. We could rethink that later, but I think keeping it
>>>>>> away
>>>>>> from JBake would be a very good idea!
>>>>>>
>>>>>
>>>>> There's a misunderstanding here, I think.
>>>>>
>>>>> Hosting the javadocs at netbeans.apache.org does not require JBake at
>>>>> all. It's just copying the generated javadocs in a directory inside
>>>>> the
>>>>> "content" directory in the "asf-site" branch:
>>>>>
>>>>> https://github.com/apache/incubator-netbeans-website/tree/
>>>>> asf-site/content
>>>>>
>>>>> Adding stuff to a directory there and pushing to the "asf-site" branch
>>>>> should be good enough. I can set up a Jenkins job for this quickly if
>>>>> you want to see a demo.
>>>>>
>>>>> Anyway, shall we run a voting on the approach, including the
>>>>> javadocs.io
>>>>> idea from John?
>>>>>
>>>>> Thanks,
>>>>> Antonio
>>>>>
>>>>>
>>>>>> But, yes, is there consensus / disagreement to that approach?
>>>>>>
>>>>>> Best wishes,
>>>>>>
>>>>>> Neil
>>>>>>
>>>>>>
>>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>>>> For additional commands, e-mail:
>>>>> dev-help@netbeans.incubator.apache.org
>>>>>
>>>>> For further information about the NetBeans mailing lists, visit:
>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Options, options (was Re: NetBeans javadoc at Apache)
Posted by Antonio <an...@vieiro.net>.
Hi Gj,
You may want to take a look at PR#930 [1], with a small fix to avoid
adding timestamp to _all_ generated HTML files. This moves the timestamp
info to javadoc.css instead. By doing so we will hopefully avoid adding
11349 files to each new commit when regenerating the javadoc.
Note that timestamps are still included in some other files (those
generated with the XSLT stylesheets), but these are just a few (as many
as modules) and I think we can handle these in a future JIRA ticket.
I'll try to create a Jenkins job in the coming days and continue with
the javadoc demo.
Kind regards,
Antonio
[1]
https://github.com/apache/incubator-netbeans/pull/930
On 30/09/18 12:46, Geertjan Wielenga wrote:
> That sounds great. If I can help in some way let me know, really keen to
> have our javadoc published in one way or another.
>
> Gj
>
>
> On Saturday, September 29, 2018, Antonio <an...@vieiro.net> wrote:
>
>> Ok. Let's go for the demo.
>>
>> First let's add the timestamp on the javadocs inside the css only (with a
>> footnote:before { content: "${TODAY}"} or something like that), and not on
>> every HTML.
>>
>> Then the new jenkins job. Monday-tuesday could be a preliminar target for
>> the demo.
>>
>> Regarding javadoc.io I think they require uploading the javadoc to Maven
>> Central first, so that'll have to wait a little until we have the Maven
>> artifacts in place with the new domain.
>>
>> Cheers,
>> Antonio
>>
>> On 29/09/18 10:14, Geertjan Wielenga wrote:
>>
>>> Well, let's see that demo first, with your Jenkins job, especially since
>>> you can do it quickly. Based on that, we can decide if we like that
>>> approach or not, once we see it in action, and then discuss alternatives
>>> if
>>> needed at that stage.
>>>
>>> Gj
>>>
>>> On Sat, Sep 29, 2018 at 10:00 AM Antonio <an...@vieiro.net> wrote:
>>>
>>>
>>>>
>>>> On 28/09/18 22:00, Neil C Smith wrote:
>>>>
>>>>> On Fri, 28 Sep 2018, 20:07 Antonio, <an...@vieiro.net> wrote:
>>>>>
>>>>> 2- http://bits.netbeans.org/dev/javadoc/index.html
>>>>>> Requires the DNS stuff being in Apache, setting up a repo and a
>>>>>> gitpubsub, will lose previous (5.0-8.2) javadocs.
>>>>>>
>>>>>>
>>>>> No it won't. The idea is to redirect 404s back to Oracle, same as
>>>>> already
>>>>> discussed with infra about the main website.
>>>>>
>>>>
>>>> Ah, I see, so we need Oracle to set up a "legacy.bits.netbeans.org"
>>>> website with the current content, right? So that all 404s that reach
>>>> bits.netbeans.org end up in legacy.bits.netbeans.org. Wasn't that the
>>>> plan?
>>>>
>>>> I recall talking something about a proxy to make the whole thing
>>>> transparent to the users, but I don't know the details. Maybe you want
>>>> to lead this after wednesday?
>>>>
>>>>
>>>>> And possibly not /dev to start with, just /9.0 and /10.0?
>>>>>
>>>>> I suggested earlier not hosting the Javadocs under netbeans.apache.org
>>>>>
>>>> at
>>>>
>>>>> least for now. We could rethink that later, but I think keeping it away
>>>>> from JBake would be a very good idea!
>>>>>
>>>>
>>>> There's a misunderstanding here, I think.
>>>>
>>>> Hosting the javadocs at netbeans.apache.org does not require JBake at
>>>> all. It's just copying the generated javadocs in a directory inside the
>>>> "content" directory in the "asf-site" branch:
>>>>
>>>> https://github.com/apache/incubator-netbeans-website/tree/
>>>> asf-site/content
>>>>
>>>> Adding stuff to a directory there and pushing to the "asf-site" branch
>>>> should be good enough. I can set up a Jenkins job for this quickly if
>>>> you want to see a demo.
>>>>
>>>> Anyway, shall we run a voting on the approach, including the javadocs.io
>>>> idea from John?
>>>>
>>>> Thanks,
>>>> Antonio
>>>>
>>>>
>>>>> But, yes, is there consensus / disagreement to that approach?
>>>>>
>>>>> Best wishes,
>>>>>
>>>>> Neil
>>>>>
>>>>>
>>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>>>
>>>> For further information about the NetBeans mailing lists, visit:
>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Options, options (was Re: NetBeans javadoc at Apache)
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
That sounds great. If I can help in some way let me know, really keen to
have our javadoc published in one way or another.
Gj
On Saturday, September 29, 2018, Antonio <an...@vieiro.net> wrote:
> Ok. Let's go for the demo.
>
> First let's add the timestamp on the javadocs inside the css only (with a
> footnote:before { content: "${TODAY}"} or something like that), and not on
> every HTML.
>
> Then the new jenkins job. Monday-tuesday could be a preliminar target for
> the demo.
>
> Regarding javadoc.io I think they require uploading the javadoc to Maven
> Central first, so that'll have to wait a little until we have the Maven
> artifacts in place with the new domain.
>
> Cheers,
> Antonio
>
> On 29/09/18 10:14, Geertjan Wielenga wrote:
>
>> Well, let's see that demo first, with your Jenkins job, especially since
>> you can do it quickly. Based on that, we can decide if we like that
>> approach or not, once we see it in action, and then discuss alternatives
>> if
>> needed at that stage.
>>
>> Gj
>>
>> On Sat, Sep 29, 2018 at 10:00 AM Antonio <an...@vieiro.net> wrote:
>>
>>
>>>
>>> On 28/09/18 22:00, Neil C Smith wrote:
>>>
>>>> On Fri, 28 Sep 2018, 20:07 Antonio, <an...@vieiro.net> wrote:
>>>>
>>>> 2- http://bits.netbeans.org/dev/javadoc/index.html
>>>>> Requires the DNS stuff being in Apache, setting up a repo and a
>>>>> gitpubsub, will lose previous (5.0-8.2) javadocs.
>>>>>
>>>>>
>>>> No it won't. The idea is to redirect 404s back to Oracle, same as
>>>> already
>>>> discussed with infra about the main website.
>>>>
>>>
>>> Ah, I see, so we need Oracle to set up a "legacy.bits.netbeans.org"
>>> website with the current content, right? So that all 404s that reach
>>> bits.netbeans.org end up in legacy.bits.netbeans.org. Wasn't that the
>>> plan?
>>>
>>> I recall talking something about a proxy to make the whole thing
>>> transparent to the users, but I don't know the details. Maybe you want
>>> to lead this after wednesday?
>>>
>>>
>>>> And possibly not /dev to start with, just /9.0 and /10.0?
>>>>
>>>> I suggested earlier not hosting the Javadocs under netbeans.apache.org
>>>>
>>> at
>>>
>>>> least for now. We could rethink that later, but I think keeping it away
>>>> from JBake would be a very good idea!
>>>>
>>>
>>> There's a misunderstanding here, I think.
>>>
>>> Hosting the javadocs at netbeans.apache.org does not require JBake at
>>> all. It's just copying the generated javadocs in a directory inside the
>>> "content" directory in the "asf-site" branch:
>>>
>>> https://github.com/apache/incubator-netbeans-website/tree/
>>> asf-site/content
>>>
>>> Adding stuff to a directory there and pushing to the "asf-site" branch
>>> should be good enough. I can set up a Jenkins job for this quickly if
>>> you want to see a demo.
>>>
>>> Anyway, shall we run a voting on the approach, including the javadocs.io
>>> idea from John?
>>>
>>> Thanks,
>>> Antonio
>>>
>>>
>>>> But, yes, is there consensus / disagreement to that approach?
>>>>
>>>> Best wishes,
>>>>
>>>> Neil
>>>>
>>>>
>>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>>
>>>
>>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Options, options (was Re: NetBeans javadoc at Apache)
Posted by Antonio <an...@vieiro.net>.
Ok. Let's go for the demo.
First let's add the timestamp on the javadocs inside the css only (with
a footnote:before { content: "${TODAY}"} or something like that), and
not on every HTML.
Then the new jenkins job. Monday-tuesday could be a preliminar target
for the demo.
Regarding javadoc.io I think they require uploading the javadoc to Maven
Central first, so that'll have to wait a little until we have the Maven
artifacts in place with the new domain.
Cheers,
Antonio
On 29/09/18 10:14, Geertjan Wielenga wrote:
> Well, let's see that demo first, with your Jenkins job, especially since
> you can do it quickly. Based on that, we can decide if we like that
> approach or not, once we see it in action, and then discuss alternatives if
> needed at that stage.
>
> Gj
>
> On Sat, Sep 29, 2018 at 10:00 AM Antonio <an...@vieiro.net> wrote:
>
>>
>>
>> On 28/09/18 22:00, Neil C Smith wrote:
>>> On Fri, 28 Sep 2018, 20:07 Antonio, <an...@vieiro.net> wrote:
>>>
>>>> 2- http://bits.netbeans.org/dev/javadoc/index.html
>>>> Requires the DNS stuff being in Apache, setting up a repo and a
>>>> gitpubsub, will lose previous (5.0-8.2) javadocs.
>>>>
>>>
>>> No it won't. The idea is to redirect 404s back to Oracle, same as already
>>> discussed with infra about the main website.
>>
>> Ah, I see, so we need Oracle to set up a "legacy.bits.netbeans.org"
>> website with the current content, right? So that all 404s that reach
>> bits.netbeans.org end up in legacy.bits.netbeans.org. Wasn't that the
>> plan?
>>
>> I recall talking something about a proxy to make the whole thing
>> transparent to the users, but I don't know the details. Maybe you want
>> to lead this after wednesday?
>>
>>>
>>> And possibly not /dev to start with, just /9.0 and /10.0?
>>>
>>> I suggested earlier not hosting the Javadocs under netbeans.apache.org
>> at
>>> least for now. We could rethink that later, but I think keeping it away
>>> from JBake would be a very good idea!
>>
>> There's a misunderstanding here, I think.
>>
>> Hosting the javadocs at netbeans.apache.org does not require JBake at
>> all. It's just copying the generated javadocs in a directory inside the
>> "content" directory in the "asf-site" branch:
>>
>> https://github.com/apache/incubator-netbeans-website/tree/asf-site/content
>>
>> Adding stuff to a directory there and pushing to the "asf-site" branch
>> should be good enough. I can set up a Jenkins job for this quickly if
>> you want to see a demo.
>>
>> Anyway, shall we run a voting on the approach, including the javadocs.io
>> idea from John?
>>
>> Thanks,
>> Antonio
>>
>>>
>>> But, yes, is there consensus / disagreement to that approach?
>>>
>>> Best wishes,
>>>
>>> Neil
>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Options, options (was Re: NetBeans javadoc at Apache)
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Well, let's see that demo first, with your Jenkins job, especially since
you can do it quickly. Based on that, we can decide if we like that
approach or not, once we see it in action, and then discuss alternatives if
needed at that stage.
Gj
On Sat, Sep 29, 2018 at 10:00 AM Antonio <an...@vieiro.net> wrote:
>
>
> On 28/09/18 22:00, Neil C Smith wrote:
> > On Fri, 28 Sep 2018, 20:07 Antonio, <an...@vieiro.net> wrote:
> >
> >> 2- http://bits.netbeans.org/dev/javadoc/index.html
> >> Requires the DNS stuff being in Apache, setting up a repo and a
> >> gitpubsub, will lose previous (5.0-8.2) javadocs.
> >>
> >
> > No it won't. The idea is to redirect 404s back to Oracle, same as already
> > discussed with infra about the main website.
>
> Ah, I see, so we need Oracle to set up a "legacy.bits.netbeans.org"
> website with the current content, right? So that all 404s that reach
> bits.netbeans.org end up in legacy.bits.netbeans.org. Wasn't that the
> plan?
>
> I recall talking something about a proxy to make the whole thing
> transparent to the users, but I don't know the details. Maybe you want
> to lead this after wednesday?
>
> >
> > And possibly not /dev to start with, just /9.0 and /10.0?
> >
> > I suggested earlier not hosting the Javadocs under netbeans.apache.org
> at
> > least for now. We could rethink that later, but I think keeping it away
> > from JBake would be a very good idea!
>
> There's a misunderstanding here, I think.
>
> Hosting the javadocs at netbeans.apache.org does not require JBake at
> all. It's just copying the generated javadocs in a directory inside the
> "content" directory in the "asf-site" branch:
>
> https://github.com/apache/incubator-netbeans-website/tree/asf-site/content
>
> Adding stuff to a directory there and pushing to the "asf-site" branch
> should be good enough. I can set up a Jenkins job for this quickly if
> you want to see a demo.
>
> Anyway, shall we run a voting on the approach, including the javadocs.io
> idea from John?
>
> Thanks,
> Antonio
>
> >
> > But, yes, is there consensus / disagreement to that approach?
> >
> > Best wishes,
> >
> > Neil
> >
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Options, options (was Re: NetBeans javadoc at Apache)
Posted by Neil C Smith <ne...@apache.org>.
Quick response!
I should have said proxy not redirect. That was what Daniel? suggested. No
changes needed on the Oracle side.
I realise we can literally bypass JBake, but just suggesting that for now
we keep it out of the main site gitpubsub process entirely until we're sure
what we do with it.
Neil
On Sat, 29 Sep 2018, 09:00 Antonio, <an...@vieiro.net> wrote:
>
>
> On 28/09/18 22:00, Neil C Smith wrote:
> > On Fri, 28 Sep 2018, 20:07 Antonio, <an...@vieiro.net> wrote:
> >
> >> 2- http://bits.netbeans.org/dev/javadoc/index.html
> >> Requires the DNS stuff being in Apache, setting up a repo and a
> >> gitpubsub, will lose previous (5.0-8.2) javadocs.
> >>
> >
> > No it won't. The idea is to redirect 404s back to Oracle, same as already
> > discussed with infra about the main website.
>
> Ah, I see, so we need Oracle to set up a "legacy.bits.netbeans.org"
> website with the current content, right? So that all 404s that reach
> bits.netbeans.org end up in legacy.bits.netbeans.org. Wasn't that the
> plan?
>
> I recall talking something about a proxy to make the whole thing
> transparent to the users, but I don't know the details. Maybe you want
> to lead this after wednesday?
>
> >
> > And possibly not /dev to start with, just /9.0 and /10.0?
> >
> > I suggested earlier not hosting the Javadocs under netbeans.apache.org
> at
> > least for now. We could rethink that later, but I think keeping it away
> > from JBake would be a very good idea!
>
> There's a misunderstanding here, I think.
>
> Hosting the javadocs at netbeans.apache.org does not require JBake at
> all. It's just copying the generated javadocs in a directory inside the
> "content" directory in the "asf-site" branch:
>
> https://github.com/apache/incubator-netbeans-website/tree/asf-site/content
>
> Adding stuff to a directory there and pushing to the "asf-site" branch
> should be good enough. I can set up a Jenkins job for this quickly if
> you want to see a demo.
>
> Anyway, shall we run a voting on the approach, including the javadocs.io
> idea from John?
>
> Thanks,
> Antonio
>
> >
> > But, yes, is there consensus / disagreement to that approach?
> >
> > Best wishes,
> >
> > Neil
> >
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Options, options (was Re: NetBeans javadoc at Apache)
Posted by Antonio <an...@vieiro.net>.
On 28/09/18 22:00, Neil C Smith wrote:
> On Fri, 28 Sep 2018, 20:07 Antonio, <an...@vieiro.net> wrote:
>
>> 2- http://bits.netbeans.org/dev/javadoc/index.html
>> Requires the DNS stuff being in Apache, setting up a repo and a
>> gitpubsub, will lose previous (5.0-8.2) javadocs.
>>
>
> No it won't. The idea is to redirect 404s back to Oracle, same as already
> discussed with infra about the main website.
Ah, I see, so we need Oracle to set up a "legacy.bits.netbeans.org"
website with the current content, right? So that all 404s that reach
bits.netbeans.org end up in legacy.bits.netbeans.org. Wasn't that the plan?
I recall talking something about a proxy to make the whole thing
transparent to the users, but I don't know the details. Maybe you want
to lead this after wednesday?
>
> And possibly not /dev to start with, just /9.0 and /10.0?
>
> I suggested earlier not hosting the Javadocs under netbeans.apache.org at
> least for now. We could rethink that later, but I think keeping it away
> from JBake would be a very good idea!
There's a misunderstanding here, I think.
Hosting the javadocs at netbeans.apache.org does not require JBake at
all. It's just copying the generated javadocs in a directory inside the
"content" directory in the "asf-site" branch:
https://github.com/apache/incubator-netbeans-website/tree/asf-site/content
Adding stuff to a directory there and pushing to the "asf-site" branch
should be good enough. I can set up a Jenkins job for this quickly if
you want to see a demo.
Anyway, shall we run a voting on the approach, including the javadocs.io
idea from John?
Thanks,
Antonio
>
> But, yes, is there consensus / disagreement to that approach?
>
> Best wishes,
>
> Neil
>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Options, options (was Re: NetBeans javadoc at Apache)
Posted by John McDonnell <mc...@gmail.com>.
Hi Antonio,
To be honest I think there's a 4th option.
If we get the Maven artefacts built and deployed we can also deploy javadoc
artefacts to maven central.
Then we can use https://www.javadoc.io/ and provide a link on our website
to this. Each release will have javadocs accessible from there after 24
hours.
Regards
John
On Fri, 28 Sep 2018 at 20:07, Antonio <an...@vieiro.net> wrote:
> Hi all,
>
> I'm re-reading the thread and that suggests netbeans.apache.org, but the
> Confluence page suggests bits.netbeans.org. I'm confused, don't know if
> we have an agreement on this. Have we?
>
> Options are:
>
> 1- netbeans.apache.org/javadoc/[dev|9.0|10.0]
> <http://netbeans.apache.org/javadoc/%5Bdev%7C9.0%7C10.0%5D>
> This will require a jenkins job.
>
> 2- http://bits.netbeans.org/dev/javadoc/index.html
> Requires the DNS stuff being in Apache, setting up a repo and a
> gitpubsub, will lose previous (5.0-8.2) javadocs.
>
> 3- http://bits.netbeans.apache.org/[dev|9.0|10.0]
> New Apache subdomain, will require a repo + gitpubsub, won't lose
> previous (5.0-8.2) javadocs, can then replace bits.netbeans.org
>
>
> Thanks,
> Antonio
>
> On 17/09/18 14:28, Neil C Smith wrote:
> > On Fri, 14 Sep 2018 at 15:22, Neil C Smith <ne...@apache.org>
> wrote:
> >> ... and speaking of which, I have a branch of NB90 checked out, but
> >> what's the magic invocation required to make a release version of the
> >> JavaDoc?
> >
> > I put up the wiki page requested -
> > https://cwiki.apache.org/confluence/display/NETBEANS/Javadoc+hosting
> >
> > But, with no response on the query above, not been able to work out
> > doing a release version of the docs. I'm probably going to have to
> > pass the baton on this one, at least with the immediate download - a
> > couple more work days then no access to a computer for 10 days.
> >
> > Can also follow up the repo / gitpubsub query with infra if there's
> > some consensus we're going that route?
> >
> > Best wishes,
> >
> > Neil
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Options, options (was Re: NetBeans javadoc at Apache)
Posted by Neil C Smith <ne...@apache.org>.
On Fri, 28 Sep 2018, 20:07 Antonio, <an...@vieiro.net> wrote:
> 2- http://bits.netbeans.org/dev/javadoc/index.html
> Requires the DNS stuff being in Apache, setting up a repo and a
> gitpubsub, will lose previous (5.0-8.2) javadocs.
>
No it won't. The idea is to redirect 404s back to Oracle, same as already
discussed with infra about the main website.
And possibly not /dev to start with, just /9.0 and /10.0?
I suggested earlier not hosting the Javadocs under netbeans.apache.org at
least for now. We could rethink that later, but I think keeping it away
from JBake would be a very good idea!
But, yes, is there consensus / disagreement to that approach?
Best wishes,
Neil
>