It should be easy for OGM, you need to update this file: https://github.com/hibernate/hibernate-ogm/blob/master/src/main/release-scripts/upload-documentation.sh
On Thu, Jul 21, 2016 at 1:46 PM, Guillaume Smet <guillaume.s...@gmail.com> wrote: > @Davide, @Sanne: would it be an issue to include the sed lines in our > release process to prepare the docs before uploading them to the doc > server? > > If it's not, it's probably the best solution. I'll wait for your > confirmation before polishing them. > > On Thu, Jul 21, 2016 at 2:38 PM, Emmanuel Bernard > <emman...@hibernate.org> wrote: >> On Thu 2016-07-21 14:20, Guillaume Smet wrote: >>> On Thu, Jul 21, 2016 at 2:07 PM, Emmanuel Bernard >>> <emman...@hibernate.org> wrote: >>> > Should we add a X or I got it button to remove this nagging when I have >>> > to read and stay on the old doc? >>> >>> I thought about it but I don't find it that invasive that we need to >>> add a close button. But I can do it if people think it's needed. I >>> suppose we would need a cookie to keep the information during the >>> navigation on the doc. >>> >>> > If that piece of code is in the xsl, how will it work when the doc is in >>> > the distribution? >>> >>> It won't work. It won't be able to load the Javascript files (the // >>> doesn't work with file:// protocol, and >>> /hibernate/_outdated-content/outdated-content.js will not be present). >>> I can make it work by using absolute URLs for everything but I thought >>> it was better to not have it in the distribution doc: if you have >>> downloaded a particular version of the doc, you probably want to read >>> this version. >> >> Right we should not have it. >> _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
