From guillaume.smet at gmail.com Tue Jul 19 18:53:29 2016 Content-Type: multipart/mixed; boundary="===============0559509001201822566==" MIME-Version: 1.0 From: Guillaume Smet To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Wed, 20 Jul 2016 00:53:27 +0200 Message-ID: --===============0559509001201822566== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi Sanne, Thanks for your feedback. I was pretty sure I hadn't all the history! Getting Google to prioritize our latest doc is probably a long time goal. I played a bit with jQuery to suggest to the user to go to the latest stable. Note that I only took into consideration the page for the time being and didn't consider the anchor but it should be easy to add it if we think it's worth it (it's a lot more work on the json descriptor though). The following command for each version is all that is needed: sed -i 's@@@' *.html (or a find -exec to do it on all the versions at once) I attached the global json descriptor and the js file (with a .txt extension as it didn't pass the mail filter). Both should be added to /hibernate/search/. Note that I only did the work for version 4.5 in the json descriptor. The work for other versions would mostly be a copy/paste. I also attached a screenshot of how it looks like. Nothing fancy but we can do whatever we want. Note that I only targeted the multi page HTML output as it was the most interesting to prototype. When we release a new version, we would have to update the descriptor file. Comments? -- Guillaume On Tue, Jul 19, 2016 at 2:39 PM, Sanne Grinovero wr= ote: > Hi Guillaume, > > yes I'm aware of the issue; we discussed it before, I think on this > same mailing list but maybe it was during our last meeting. > > We really need to fix that metadata; Stefania (my partner) is an SEO > consultant and is shocked at how bad we do with this; apparently we > are a funny example in her office but at least we're not the worst :) > > The problem is we can't change the headers as we don't control the > Apache httpd configuraion on the documentation server, so the > alternative is we'd need to rsync those docs locally, insert the right > changes in the static files of the docs, and push them back. > > Needs a volunteer to find some time for this. > > Also related to SEO I recently opened some issues on our WEBSITE > project, these should be easier to fix as it's directly under our > control: > - https://hibernate.atlassian.net/browse/WEBSITE-461 > - https://hibernate.atlassian.net/browse/WEBSITE-460 > - https://hibernate.atlassian.net/browse/WEBSITE-459 > > I've assigned them to Davide as he's usually quick with such things > but anyone is welcome to take some. > > The metadata issue on the docs server is probably the most urgent / > valuable though. > > Thanks, > Sanne --===============0559509001201822566== Content-Type: text/plain MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="outdated-version.js.txt" JChkb2N1bWVudCkucmVhZHkoZnVuY3Rpb24oKSB7CgkkLmdldEpTT04oJy9oaWJlcm5hdGUvc2Vh cmNoL2RvY3VtZW50YXRpb24uanNvbicsIGZ1bmN0aW9uIChqc29uKSB7CgkJdmFyIGN1cnJlbnRV cmwgPSB3aW5kb3cubG9jYXRpb24ucGF0aG5hbWU7CgkJdmFyIG1hdGNoID0gbmV3IFJlZ0V4cCgn XicgKyBqc29uLnBhdHRlcm4ucmVwbGFjZSgnJHt2ZXJzaW9ufScsICcoW14vXSspJykucmVwbGFj ZSgnJHtwYWdlfScsICcoLitcXC5odG1sKScpICsgJyQnKS5leGVjKGN1cnJlbnRVcmwpOwoJCWlm IChtYXRjaC5sZW5ndGggIT0gMykgewoJCQlyZXR1cm47CgkJfQoJCXZhciBjdXJyZW50VmVyc2lv biA9IG1hdGNoWzFdOwoJCXZhciBjdXJyZW50UGFnZSA9IG1hdGNoWzJdOwoJCXZhciBjdXJyZW50 SGFzaCA9IHdpbmRvdy5sb2NhdGlvbi5oYXNoOwoJCQoJCWlmIChjdXJyZW50VmVyc2lvbiA9PSBq c29uLnN0YWJsZSB8fCBjdXJyZW50VmVyc2lvbiA9PSBqc29uLmRldmVsb3BtZW50IHx8IGN1cnJl bnRWZXJzaW9uID09ICdzdGFibGUnKSB7CgkJCXJldHVybjsKCQl9CgkJCgkJdmFyIHJlZGlyZWN0 UGFnZTsKCQlpZiAoY3VycmVudFZlcnNpb24gaW4ganNvbi52ZXJzaW9ucyAmJiBjdXJyZW50UGFn ZSBpbiBqc29uLnZlcnNpb25zW2N1cnJlbnRWZXJzaW9uXS5yZWRpcmVjdHMpIHsKCQkJcmVkaXJl Y3RQYWdlID0ganNvbi52ZXJzaW9uc1tjdXJyZW50VmVyc2lvbl0ucmVkaXJlY3RzW2N1cnJlbnRQ YWdlXTsKCQl9IGVsc2UgewoJCQlyZWRpcmVjdFBhZ2UgPSAnJzsKCQl9CgkJc3RhYmxlVXJsID0g anNvbi5wYXR0ZXJuLnJlcGxhY2UoJyR7dmVyc2lvbn0nLCBqc29uLnN0YWJsZSkucmVwbGFjZSgn JHtwYWdlfScsIHJlZGlyZWN0UGFnZSArIGN1cnJlbnRIYXNoKTsKCQkkKCdoZWFkJykuYXBwZW5k KCc8c3R5bGUgdHlwZT0idGV4dC9jc3MiPicgKwoJCQknLm91dGRhdGVkLWNvbnRlbnQgeycgKwoJ CQknCXBvc2l0aW9uOiBmaXhlZDsnICsKCQkJJwlib3R0b206IDA7JyArCgkJCScJbGVmdDogMDsn ICsKCQkJJwl0ZXh0LWFsaWduOmNlbnRlcjsnICsKCQkJJwl3aWR0aDoxMDAlOycgKwoJCQknCXBh ZGRpbmc6IDIwcHg7JyArCgkJCScJYmFja2dyb3VuZC1jb2xvcjogb3JhbmdlOycgKwoJCQknCWJh Y2tncm91bmQtY29sb3I6ICNmZmJjM2I7JyArCgkJCScJYm9yZGVyLXRvcDogMXB4IHNvbGlkIG9y YW5nZTsnICsKCQkJJwlmb250LXdlaWdodDogYm9sZDsnICsKCQkJJwlmb250LXNpemU6IDIwcHg7 JyArCgkJCScJY29sb3I6IHdoaXRlOycgKwoJCQknCXRleHQtc2hhZG93OiAwIDFweCAxcHggcmdi YSg4NSwgODUsIDg1LCAwLjU1KScgKwoJCQknfScgKwoJCQknYS52ZXJzaW9uIHsnICsKCQkJJwli b3JkZXI6IDFweCBzb2xpZCAjQUFBOycgKwoJCQknCWJvcmRlci1yYWRpdXM6IDRweDsnICsKCQkJ JwliYWNrZ3JvdW5kLWNvbG9yOiAjQkJCOycgKwoJCQknCXBhZGRpbmc6IDNweCA4cHg7JyArCgkJ CScJY29sb3I6IHdoaXRlOycgKwoJCQknCXRleHQtc2hhZG93OiAwIDFweCAxcHggcmdiYSg4NSwg ODUsIDg1LCAwLjU1KTsJJyArCgkJCScJdGV4dC1kZWNvcmF0aW9uOiBub25lOycgKwoJCQknfScg KwoJCQknYS52ZXJzaW9uOmhvdmVyIHsnICsKCQkJJwliYWNrZ3JvdW5kLWNvbG9yOiAjQ0NDOycg KwoJCQknfScgKwoJCSc8L3N0eWxlPicpOwoJCSQoJ2JvZHknKS5hcHBlbmQoJzxkaXYgY2xhc3M9 Im91dGRhdGVkLWNvbnRlbnQiPlRoaXMgY29udGVudCByZWZlcnMgdG8gYW4gb3V0ZGF0ZWQgdmVy c2lvbiBvZiAnICsganNvbi5wcm9qZWN0ICsgJy4gR28gdG8gbGF0ZXN0IHN0YWJsZTogPGEgaHJl Zj0iJyArIHN0YWJsZVVybCArICciIGNsYXNzPSJ2ZXJzaW9uIj52ZXJzaW9uICcgKyBqc29uLnN0 YWJsZSArJzwvYT4uPC9kaXY+Jyk7Cgl9KQp9KTsK --===============0559509001201822566==-- From davide at hibernate.org Wed Jul 20 06:06:37 2016 Content-Type: multipart/mixed; boundary="===============1309497246958517063==" MIME-Version: 1.0 From: Davide D'Alto To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Wed, 20 Jul 2016 11:06:16 +0100 Message-ID: In-Reply-To: CALt0+o9hA+aQ1feyLVf=+aB=4NMtJe8E2tGCjDJOae63MRS5AA@mail.gmail.com --===============1309497246958517063== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable I'll try to apply these changes on Friday. Davide On Tue, Jul 19, 2016 at 11:53 PM, Guillaume Smet wrote: > Hi Sanne, > > Thanks for your feedback. I was pretty sure I hadn't all the history! > > Getting Google to prioritize our latest doc is probably a long time goal. > > I played a bit with jQuery to suggest to the user to go to the latest > stable. Note that I only took into consideration the page for the time > being and didn't consider the anchor but it should be easy to add it > if we think it's worth it (it's a lot more work on the json descriptor > though). > > The following command for each version is all that is needed: > sed -i 's@@@' *.html > (or a find -exec to do it on all the versions at once) > > I attached the global json descriptor and the js file (with a .txt > extension as it didn't pass the mail filter). Both should be added to > /hibernate/search/. Note that I only did the work for version 4.5 in > the json descriptor. The work for other versions would mostly be a > copy/paste. > > I also attached a screenshot of how it looks like. Nothing fancy but > we can do whatever we want. > > Note that I only targeted the multi page HTML output as it was the > most interesting to prototype. > > When we release a new version, we would have to update the descriptor fil= e. > > Comments? > > -- > Guillaume > > On Tue, Jul 19, 2016 at 2:39 PM, Sanne Grinovero = wrote: >> Hi Guillaume, >> >> yes I'm aware of the issue; we discussed it before, I think on this >> same mailing list but maybe it was during our last meeting. >> >> We really need to fix that metadata; Stefania (my partner) is an SEO >> consultant and is shocked at how bad we do with this; apparently we >> are a funny example in her office but at least we're not the worst :) >> >> The problem is we can't change the headers as we don't control the >> Apache httpd configuraion on the documentation server, so the >> alternative is we'd need to rsync those docs locally, insert the right >> changes in the static files of the docs, and push them back. >> >> Needs a volunteer to find some time for this. >> >> Also related to SEO I recently opened some issues on our WEBSITE >> project, these should be easier to fix as it's directly under our >> control: >> - https://hibernate.atlassian.net/browse/WEBSITE-461 >> - https://hibernate.atlassian.net/browse/WEBSITE-460 >> - https://hibernate.atlassian.net/browse/WEBSITE-459 >> >> I've assigned them to Davide as he's usually quick with such things >> but anyone is welcome to take some. >> >> The metadata issue on the docs server is probably the most urgent / >> valuable though. >> >> Thanks, >> Sanne > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev --===============1309497246958517063==-- From guillaume.smet at gmail.com Thu Jul 21 07:33:51 2016 Content-Type: multipart/mixed; boundary="===============8805549037805996269==" MIME-Version: 1.0 From: Guillaume Smet To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Thu, 21 Jul 2016 13:33:49 +0200 Message-ID: In-Reply-To: CANoTJYPx_yv18bXiZX5h4m-nN5TGYqpcqPxtK9iaOM-6p_oemg@mail.gmail.com --===============8805549037805996269== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi all! So here is a status of what I did: - I updated the /stable/ link of ogm from 3.0 (cough, cough) to 5.0: http://docs.jboss.org/hibernate/stable/ogm/reference/en-US/html/: we need to include this in our release process. - I updated the /current/ symlink of ORM to point to 5.2 instead of 5.1: it needs to be integrated in the release process; (the /stable/ link uses the /current/ symlink so it's also fixed) - I removed the docs for OGM 3.0 as they were a copy of the doc of OGM 4.2 Next, I applied some magic to 2 old versions of OGM and Search so that you can check everything is OK for you before I generalize it: - Add meta description and keywords - Add a canonical link to the /stable/ single html version - Add a piece of Javascript to warn the user and propose to redirect him to the best possible place of our last stable release documentation See the 2 examples here: http://docs.jboss.org.local/hibernate/ogm/4.1/reference/en-US/html/ogm-arch= itecture.html (scroll to see the hash tracker in action) http://docs.jboss.org/hibernate/search/4.2/reference/en-US/html/search-arch= itecture.html See the current code and descriptors here: https://docs.jboss.org/hibernate/_outdated-content/ The script and the descriptors work for all existing versions of the OGM and Search doc. The marker to include in the docs looks like that: (I'm using a CDN but maybe we should host jQuery on docs.jboss.org?) The script is capable to redirect either to the multi page version (using the redirects declared in the JSON file: it automatically cumulates the redirects from version X to version Y so we don't need that much metadata) or to the single page version by leveraging the anchors and hashes. For now, I decided to push the user to the single page version as it's the one we use for the canonical link but we can of course discuss it. Note that I add a ?v=3DX.X parameter to be sure the user is redirected to a fresh version of the corresponding /stable/ page and not a cache. I had the issue a couple of times. Next if you like it: - generalize it to all the existing versions of the docs, sed FTW - modify the Hibernate XSL stylesheets to include it in the newly generated= ones - probably modify our website so that the stable release points to the /stable/ link to the docs - do the same for Validator @ORM: interested in me pursuing this for ORM too? It will probably be a lot more work as the structure of the docs got changed a lot. Comments, opinions, thoughts welcome. -- = Guillaume On Wed, Jul 20, 2016 at 12:06 PM, Davide D'Alto wr= ote: > I'll try to apply these changes on Friday. > > Davide > > On Tue, Jul 19, 2016 at 11:53 PM, Guillaume Smet > wrote: >> Hi Sanne, >> >> Thanks for your feedback. I was pretty sure I hadn't all the history! >> >> Getting Google to prioritize our latest doc is probably a long time goal. >> >> I played a bit with jQuery to suggest to the user to go to the latest >> stable. Note that I only took into consideration the page for the time >> being and didn't consider the anchor but it should be easy to add it >> if we think it's worth it (it's a lot more work on the json descriptor >> though). >> >> The following command for each version is all that is needed: >> sed -i 's@@@' *.html >> (or a find -exec to do it on all the versions at once) >> >> I attached the global json descriptor and the js file (with a .txt >> extension as it didn't pass the mail filter). Both should be added to >> /hibernate/search/. Note that I only did the work for version 4.5 in >> the json descriptor. The work for other versions would mostly be a >> copy/paste. >> >> I also attached a screenshot of how it looks like. Nothing fancy but >> we can do whatever we want. >> >> Note that I only targeted the multi page HTML output as it was the >> most interesting to prototype. >> >> When we release a new version, we would have to update the descriptor fi= le. >> >> Comments? >> >> -- >> Guillaume --===============8805549037805996269==-- From guillaume.smet at gmail.com Thu Jul 21 07:34:58 2016 Content-Type: multipart/mixed; boundary="===============6850783306728134155==" MIME-Version: 1.0 From: Guillaume Smet To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Thu, 21 Jul 2016 13:34:57 +0200 Message-ID: In-Reply-To: CALt0+o_fi4jBhSxe4gpF=usBvJ3KVJCtqJX+=PFRCr1HtvdgFQ@mail.gmail.com --===============6850783306728134155== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Iiiik, remove the .local suffix in the domain for the first example! On Thu, Jul 21, 2016 at 1:33 PM, Guillaume Smet wrote: > Hi all! > > So here is a status of what I did: > - I updated the /stable/ link of ogm from 3.0 (cough, cough) to 5.0: > http://docs.jboss.org/hibernate/stable/ogm/reference/en-US/html/: we > need to include this in our release process. > - I updated the /current/ symlink of ORM to point to 5.2 instead of > 5.1: it needs to be integrated in the release process; (the /stable/ > link uses the /current/ symlink so it's also fixed) > - I removed the docs for OGM 3.0 as they were a copy of the doc of OGM 4.2 > > Next, I applied some magic to 2 old versions of OGM and Search so that > you can check everything is OK for you before I generalize it: > - Add meta description and keywords > - Add a canonical link to the /stable/ single html version > - Add a piece of Javascript to warn the user and propose to redirect > him to the best possible place of our last stable release > documentation > > See the 2 examples here: > http://docs.jboss.org.local/hibernate/ogm/4.1/reference/en-US/html/ogm-ar= chitecture.html > (scroll to see the hash tracker in action) > http://docs.jboss.org/hibernate/search/4.2/reference/en-US/html/search-ar= chitecture.html > > See the current code and descriptors here: > https://docs.jboss.org/hibernate/_outdated-content/ > > The script and the descriptors work for all existing versions of the > OGM and Search doc. > > The marker to include in the docs looks like that: > > > > > (I'm using a CDN but maybe we should host jQuery on docs.jboss.org?) > > The script is capable to redirect either to the multi page version > (using the redirects declared in the JSON file: it automatically > cumulates the redirects from version X to version Y so we don't need > that much metadata) or to the single page version by leveraging the > anchors and hashes. For now, I decided to push the user to the single > page version as it's the one we use for the canonical link but we can > of course discuss it. Note that I add a ?v=3DX.X parameter to be sure > the user is redirected to a fresh version of the corresponding > /stable/ page and not a cache. I had the issue a couple of times. > > Next if you like it: > - generalize it to all the existing versions of the docs, sed FTW > - modify the Hibernate XSL stylesheets to include it in the newly generat= ed ones > - probably modify our website so that the stable release points to the > /stable/ link to the docs > - do the same for Validator > > @ORM: interested in me pursuing this for ORM too? It will probably be > a lot more work as the structure of the docs got changed a lot. > > Comments, opinions, thoughts welcome. > > -- > Guillaume > > On Wed, Jul 20, 2016 at 12:06 PM, Davide D'Alto = wrote: >> I'll try to apply these changes on Friday. >> >> Davide >> >> On Tue, Jul 19, 2016 at 11:53 PM, Guillaume Smet >> wrote: >>> Hi Sanne, >>> >>> Thanks for your feedback. I was pretty sure I hadn't all the history! >>> >>> Getting Google to prioritize our latest doc is probably a long time goa= l. >>> >>> I played a bit with jQuery to suggest to the user to go to the latest >>> stable. Note that I only took into consideration the page for the time >>> being and didn't consider the anchor but it should be easy to add it >>> if we think it's worth it (it's a lot more work on the json descriptor >>> though). >>> >>> The following command for each version is all that is needed: >>> sed -i 's@@@' *.html >>> (or a find -exec to do it on all the versions at once) >>> >>> I attached the global json descriptor and the js file (with a .txt >>> extension as it didn't pass the mail filter). Both should be added to >>> /hibernate/search/. Note that I only did the work for version 4.5 in >>> the json descriptor. The work for other versions would mostly be a >>> copy/paste. >>> >>> I also attached a screenshot of how it looks like. Nothing fancy but >>> we can do whatever we want. >>> >>> Note that I only targeted the multi page HTML output as it was the >>> most interesting to prototype. >>> >>> When we release a new version, we would have to update the descriptor f= ile. >>> >>> Comments? >>> >>> -- >>> Guillaume --===============6850783306728134155==-- From emmanuel at hibernate.org Thu Jul 21 08:07:30 2016 Content-Type: multipart/mixed; boundary="===============6224707515853008429==" MIME-Version: 1.0 From: Emmanuel Bernard To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Thu, 21 Jul 2016 14:07:06 +0200 Message-ID: <20160721120706.GD75699@hibernate.org> In-Reply-To: CALt0+o_fi4jBhSxe4gpF=usBvJ3KVJCtqJX+=PFRCr1HtvdgFQ@mail.gmail.com --===============6224707515853008429== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Nice, 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? If that piece of code is in the xsl, how will it work when the doc is in the distribution? How screwed are you if we stop using these stylesheet and say embrace the Asciidoctor default style? On Thu 2016-07-21 13:33, Guillaume Smet wrote: > Hi all! > = > So here is a status of what I did: > - I updated the /stable/ link of ogm from 3.0 (cough, cough) to 5.0: > http://docs.jboss.org/hibernate/stable/ogm/reference/en-US/html/: we > need to include this in our release process. > - I updated the /current/ symlink of ORM to point to 5.2 instead of > 5.1: it needs to be integrated in the release process; (the /stable/ > link uses the /current/ symlink so it's also fixed) > - I removed the docs for OGM 3.0 as they were a copy of the doc of OGM 4.2 > = > Next, I applied some magic to 2 old versions of OGM and Search so that > you can check everything is OK for you before I generalize it: > - Add meta description and keywords > - Add a canonical link to the /stable/ single html version > - Add a piece of Javascript to warn the user and propose to redirect > him to the best possible place of our last stable release > documentation > = > See the 2 examples here: > http://docs.jboss.org.local/hibernate/ogm/4.1/reference/en-US/html/ogm-ar= chitecture.html > (scroll to see the hash tracker in action) > http://docs.jboss.org/hibernate/search/4.2/reference/en-US/html/search-ar= chitecture.html > = > See the current code and descriptors here: > https://docs.jboss.org/hibernate/_outdated-content/ > = > The script and the descriptors work for all existing versions of the > OGM and Search doc. > = > The marker to include in the docs looks like that: > > > > = > (I'm using a CDN but maybe we should host jQuery on docs.jboss.org?) > = > The script is capable to redirect either to the multi page version > (using the redirects declared in the JSON file: it automatically > cumulates the redirects from version X to version Y so we don't need > that much metadata) or to the single page version by leveraging the > anchors and hashes. For now, I decided to push the user to the single > page version as it's the one we use for the canonical link but we can > of course discuss it. Note that I add a ?v=3DX.X parameter to be sure > the user is redirected to a fresh version of the corresponding > /stable/ page and not a cache. I had the issue a couple of times. > = > Next if you like it: > - generalize it to all the existing versions of the docs, sed FTW > - modify the Hibernate XSL stylesheets to include it in the newly generat= ed ones > - probably modify our website so that the stable release points to the > /stable/ link to the docs > - do the same for Validator > = > @ORM: interested in me pursuing this for ORM too? It will probably be > a lot more work as the structure of the docs got changed a lot. > = > Comments, opinions, thoughts welcome. > = > -- = > Guillaume > = > On Wed, Jul 20, 2016 at 12:06 PM, Davide D'Alto = wrote: > > I'll try to apply these changes on Friday. > > > > Davide > > > > On Tue, Jul 19, 2016 at 11:53 PM, Guillaume Smet > > wrote: > >> Hi Sanne, > >> > >> Thanks for your feedback. I was pretty sure I hadn't all the history! > >> > >> Getting Google to prioritize our latest doc is probably a long time go= al. > >> > >> I played a bit with jQuery to suggest to the user to go to the latest > >> stable. Note that I only took into consideration the page for the time > >> being and didn't consider the anchor but it should be easy to add it > >> if we think it's worth it (it's a lot more work on the json descriptor > >> though). > >> > >> The following command for each version is all that is needed: > >> sed -i 's@@@' *.html > >> (or a find -exec to do it on all the versions at once) > >> > >> I attached the global json descriptor and the js file (with a .txt > >> extension as it didn't pass the mail filter). Both should be added to > >> /hibernate/search/. Note that I only did the work for version 4.5 in > >> the json descriptor. The work for other versions would mostly be a > >> copy/paste. > >> > >> I also attached a screenshot of how it looks like. Nothing fancy but > >> we can do whatever we want. > >> > >> Note that I only targeted the multi page HTML output as it was the > >> most interesting to prototype. > >> > >> When we release a new version, we would have to update the descriptor = file. > >> > >> Comments? > >> > >> -- > >> Guillaume > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev --===============6224707515853008429==-- From guillaume.smet at gmail.com Thu Jul 21 08:20:58 2016 Content-Type: multipart/mixed; boundary="===============6479079114980843449==" MIME-Version: 1.0 From: Guillaume Smet To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Thu, 21 Jul 2016 14:20:56 +0200 Message-ID: In-Reply-To: 20160721120706.GD75699@hibernate.org --===============6479079114980843449== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Thu, Jul 21, 2016 at 2:07 PM, Emmanuel Bernard 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. > How screwed are you if we stop using these stylesheet and say embrace > the Asciidoctor default style? Well, either we can include top and bottom template anyway or we have to run a sed on the files before uploading them to the doc server. Maybe we should even do it this way and add the sed calls in our release process. This way, it won't be in the distribution doc and we won't have to alter the stylesheets. Basically, we have to execute this in the reference directory (I didn't do the work for the Javadoc, would it be useful?): # Hibernate Search find . -name \*.html -exec sed -i 's@@@' {} \; find . -name \*.html -exec sed -i 's@ xxxx markers to be able to update the code easily in the future. Same for the meta. -- = Guillaume --===============6479079114980843449==-- From emmanuel at hibernate.org Thu Jul 21 08:38:13 2016 Content-Type: multipart/mixed; boundary="===============6758473340979431306==" MIME-Version: 1.0 From: Emmanuel Bernard To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Thu, 21 Jul 2016 14:38:09 +0200 Message-ID: <20160721123809.GE75699@hibernate.org> In-Reply-To: CALt0+o-kHeeK2sb64gx0_WHBQwJjTRy47RJxh=tz8KnUTRodDg@mail.gmail.com --===============6758473340979431306== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Thu 2016-07-21 14:20, Guillaume Smet wrote: > On Thu, Jul 21, 2016 at 2:07 PM, Emmanuel Bernard > 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. --===============6758473340979431306==-- From guillaume.smet at gmail.com Thu Jul 21 08:46:04 2016 Content-Type: multipart/mixed; boundary="===============5706836676035784894==" MIME-Version: 1.0 From: Guillaume Smet To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Thu, 21 Jul 2016 14:46:02 +0200 Message-ID: In-Reply-To: 20160721123809.GE75699@hibernate.org --===============5706836676035784894== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable @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 wrote: > On Thu 2016-07-21 14:20, Guillaume Smet wrote: >> On Thu, Jul 21, 2016 at 2:07 PM, Emmanuel Bernard >> 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. > --===============5706836676035784894==-- From steve at hibernate.org Thu Jul 21 08:52:00 2016 Content-Type: multipart/mixed; boundary="===============2469786624986462297==" MIME-Version: 1.0 From: Steve Ebersole To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Thu, 21 Jul 2016 12:51:50 +0000 Message-ID: In-Reply-To: CALt0+o_fi4jBhSxe4gpF=usBvJ3KVJCtqJX+=PFRCr1HtvdgFQ@mail.gmail.com --===============2469786624986462297== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Thu, Jul 21, 2016 at 6:36 AM Guillaume Smet wrote: > > @ORM: interested in me pursuing this for ORM too? It will probably be > a lot more work as the structure of the docs got changed a lot. > I would definitely be interested in a solution that finally allows us to fix this. If you are willing to take this on, that would be amazing. --===============2469786624986462297==-- From davide at hibernate.org Thu Jul 21 08:52:35 2016 Content-Type: multipart/mixed; boundary="===============7075711050652679813==" MIME-Version: 1.0 From: Davide D'Alto To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Thu, 21 Jul 2016 13:52:14 +0100 Message-ID: In-Reply-To: CALt0+o8+-9-9rpRwEPduB_=s6SePGdgDJRHTBJcdsa8wX_Wx5w@mail.gmail.com --===============7075711050652679813== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable It should be easy for OGM, you need to update this file: https://github.com/hibernate/hibernate-ogm/blob/master/src/main/release-scr= ipts/upload-documentation.sh On Thu, Jul 21, 2016 at 1:46 PM, Guillaume Smet 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 > wrote: >> On Thu 2016-07-21 14:20, Guillaume Smet wrote: >>> On Thu, Jul 21, 2016 at 2:07 PM, Emmanuel Bernard >>> wrote: >>> > Should we add a X or I got it button to remove this nagging when I ha= ve >>> > 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. >> --===============7075711050652679813==-- From sanne at hibernate.org Thu Jul 21 09:06:34 2016 Content-Type: multipart/mixed; boundary="===============1235643256229290933==" MIME-Version: 1.0 From: Sanne Grinovero To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Thu, 21 Jul 2016 14:06:13 +0100 Message-ID: In-Reply-To: CANoTJYMbkJa_0GZoZEmwsp5AQEq-vnTu_yKV8LgrbMrQzYzU4g@mail.gmail.com --===============1235643256229290933== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 21 July 2016 at 13:52, Davide D'Alto wrote: > It should be easy for OGM, you need to update this file: > https://github.com/hibernate/hibernate-ogm/blob/master/src/main/release-s= cripts/upload-documentation.sh +1, no problems for Search either. It's not scripted yet, so I'll just need clear instructions on the release wiki: - https://developer.jboss.org/wiki/ReleasingHibernateSearch How should we update the metadata file at e.g. http://docs.jboss.org/hibernate/_outdated-content/search.json ? Maybe we could move that to the website, as similar metadata is already being deployed, e.g. - https://github.com/hibernate/hibernate.org/tree/staging/_data/projects/s= earch/releases Ideally the website building scripts could take the yaml file and publish an updated search.json when updating hibernate.org ? Looks great, thanks! --===============1235643256229290933==-- From guillaume.smet at gmail.com Thu Jul 21 18:26:07 2016 Content-Type: multipart/mixed; boundary="===============3941804131816146523==" MIME-Version: 1.0 From: Guillaume Smet To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Fri, 22 Jul 2016 00:26:05 +0200 Message-ID: In-Reply-To: CAFm4XO3_wC2TDwX6rqC4+yQmKS-VcWjg0e_ad=z52z3JbsYfyQ@mail.gmail.com --===============3941804131816146523== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Thu, Jul 21, 2016 at 3:06 PM, Sanne Grinovero wr= ote: > Maybe we could move that to the website, as similar metadata is > already being deployed, e.g. > - https://github.com/hibernate/hibernate.org/tree/staging/_data/projects= /search/releases We already need to update the /stable/ symlink on the doc server so we might as well do it when we push the doc. I got something like this: https://gist.github.com/gsmet/8c8e29c46337f69bfbc9e84f108d951f . I'll push a PR tomorrow. I pushed the JS and the metadata to all known doc versions of Search and OG= M. -- = Guillaume --===============3941804131816146523==-- From daltodavide at gmail.com Fri Jul 22 11:57:40 2016 Content-Type: multipart/mixed; boundary="===============3637864505294721907==" MIME-Version: 1.0 From: Davide D'Alto To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Fri, 22 Jul 2016 16:57:19 +0100 Message-ID: In-Reply-To: CALt0+o-xq0at6C7pTeNnyQLTycjmE+v5Z5a4XQxDx8dC0pd8MQ@mail.gmail.com --===============3637864505294721907== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable I've updated the microdata on our blog. I used the google validation page to check the result: https://search.google.com/structured-data/testing-tool/u/0/?hl=3DEN#url=3Dh= ttp%3A%2F%2Fin.relation.to%2F I'm not familiar with microdata, if you think that something is wrong let me know. I have a question about the organization, should I put Red Hat or Hibernate? At the moment I'm using Hibernate and hibernate.org as organizarion url, but let me know. Cheers, Davide On Thu, Jul 21, 2016 at 11:26 PM, Guillaume Smet wrote: > On Thu, Jul 21, 2016 at 3:06 PM, Sanne Grinovero = wrote: >> Maybe we could move that to the website, as similar metadata is >> already being deployed, e.g. >> - https://github.com/hibernate/hibernate.org/tree/staging/_data/project= s/search/releases > > We already need to update the /stable/ symlink on the doc server so we > might as well do it when we push the doc. > > I got something like this: > https://gist.github.com/gsmet/8c8e29c46337f69bfbc9e84f108d951f . I'll > push a PR tomorrow. > > I pushed the JS and the metadata to all known doc versions of Search and = OGM. > > -- > Guillaume > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev --===============3637864505294721907==-- From emmanuel at hibernate.org Fri Jul 22 12:33:36 2016 Content-Type: multipart/mixed; boundary="===============1451899379553498855==" MIME-Version: 1.0 From: Emmanuel Bernard To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Fri, 22 Jul 2016 18:33:33 +0200 Message-ID: <20160722163333.GI11493@hibernate.org> In-Reply-To: CANoTJYNa4=9wv5zJf5o77J3Yg7Yb4G_qwsHB8pZmhrXL81V87w@mail.gmail.com --===============1451899379553498855== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hibernate is fine. On Fri 2016-07-22 16:57, Davide D'Alto wrote: > I've updated the microdata on our blog. > I used the google validation page to check the result: > https://search.google.com/structured-data/testing-tool/u/0/?hl=3DEN#url= =3Dhttp%3A%2F%2Fin.relation.to%2F > = > I'm not familiar with microdata, if you think that something is wrong > let me know. > = > I have a question about the organization, should I put Red Hat or Hiberna= te? > At the moment I'm using Hibernate and hibernate.org as organizarion > url, but let me know. > = > Cheers, > Davide > = > On Thu, Jul 21, 2016 at 11:26 PM, Guillaume Smet > wrote: > > On Thu, Jul 21, 2016 at 3:06 PM, Sanne Grinovero wrote: > >> Maybe we could move that to the website, as similar metadata is > >> already being deployed, e.g. > >> - https://github.com/hibernate/hibernate.org/tree/staging/_data/proje= cts/search/releases > > > > We already need to update the /stable/ symlink on the doc server so we > > might as well do it when we push the doc. > > > > I got something like this: > > https://gist.github.com/gsmet/8c8e29c46337f69bfbc9e84f108d951f . I'll > > push a PR tomorrow. > > > > I pushed the JS and the metadata to all known doc versions of Search an= d OGM. > > > > -- > > Guillaume > > _______________________________________________ > > hibernate-dev mailing list > > hibernate-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev --===============1451899379553498855==-- From sanne at hibernate.org Tue Jul 26 14:03:46 2016 Content-Type: multipart/mixed; boundary="===============7779078137085649677==" MIME-Version: 1.0 From: Sanne Grinovero To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Tue, 26 Jul 2016 19:03:24 +0100 Message-ID: In-Reply-To: 20160722163333.GI11493@hibernate.org --===============7779078137085649677== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable The SEO expert liked the results :) On 22 July 2016 at 17:33, Emmanuel Bernard wrote: > Hibernate is fine. > > On Fri 2016-07-22 16:57, Davide D'Alto wrote: >> I've updated the microdata on our blog. >> I used the google validation page to check the result: >> https://search.google.com/structured-data/testing-tool/u/0/?hl=3DEN#url= =3Dhttp%3A%2F%2Fin.relation.to%2F >> >> I'm not familiar with microdata, if you think that something is wrong >> let me know. >> >> I have a question about the organization, should I put Red Hat or Hibern= ate? >> At the moment I'm using Hibernate and hibernate.org as organizarion >> url, but let me know. >> >> Cheers, >> Davide >> >> On Thu, Jul 21, 2016 at 11:26 PM, Guillaume Smet >> wrote: >> > On Thu, Jul 21, 2016 at 3:06 PM, Sanne Grinovero wrote: >> >> Maybe we could move that to the website, as similar metadata is >> >> already being deployed, e.g. >> >> - https://github.com/hibernate/hibernate.org/tree/staging/_data/proj= ects/search/releases >> > >> > We already need to update the /stable/ symlink on the doc server so we >> > might as well do it when we push the doc. >> > >> > I got something like this: >> > https://gist.github.com/gsmet/8c8e29c46337f69bfbc9e84f108d951f . I'll >> > push a PR tomorrow. >> > >> > I pushed the JS and the metadata to all known doc versions of Search a= nd OGM. >> > >> > -- >> > Guillaume >> > _______________________________________________ >> > hibernate-dev mailing list >> > hibernate-dev(a)lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/hibernate-dev >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev --===============7779078137085649677==-- From daltodavide at gmail.com Wed Jul 27 02:56:59 2016 Content-Type: multipart/mixed; boundary="===============5849910167819139417==" MIME-Version: 1.0 From: Davide D'Alto To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Wed, 27 Jul 2016 07:56:38 +0100 Message-ID: In-Reply-To: CAFm4XO1P_swsXT0JpNzLnFQu7rcXyhHTDs+YAZZJsQnbXwz3fA@mail.gmail.com --===============5849910167819139417== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Great :) now I need to do the same with hibernate.org. On Tue, Jul 26, 2016 at 7:03 PM, Sanne Grinovero wr= ote: > The SEO expert liked the results :) > > On 22 July 2016 at 17:33, Emmanuel Bernard wro= te: >> Hibernate is fine. >> >> On Fri 2016-07-22 16:57, Davide D'Alto wrote: >>> I've updated the microdata on our blog. >>> I used the google validation page to check the result: >>> https://search.google.com/structured-data/testing-tool/u/0/?hl=3DEN#url= =3Dhttp%3A%2F%2Fin.relation.to%2F >>> >>> I'm not familiar with microdata, if you think that something is wrong >>> let me know. >>> >>> I have a question about the organization, should I put Red Hat or Hiber= nate? >>> At the moment I'm using Hibernate and hibernate.org as organizarion >>> url, but let me know. >>> >>> Cheers, >>> Davide >>> >>> On Thu, Jul 21, 2016 at 11:26 PM, Guillaume Smet >>> wrote: >>> > On Thu, Jul 21, 2016 at 3:06 PM, Sanne Grinovero wrote: >>> >> Maybe we could move that to the website, as similar metadata is >>> >> already being deployed, e.g. >>> >> - https://github.com/hibernate/hibernate.org/tree/staging/_data/pro= jects/search/releases >>> > >>> > We already need to update the /stable/ symlink on the doc server so we >>> > might as well do it when we push the doc. >>> > >>> > I got something like this: >>> > https://gist.github.com/gsmet/8c8e29c46337f69bfbc9e84f108d951f . I'll >>> > push a PR tomorrow. >>> > >>> > I pushed the JS and the metadata to all known doc versions of Search = and OGM. >>> > >>> > -- >>> > Guillaume >>> > _______________________________________________ >>> > hibernate-dev mailing list >>> > hibernate-dev(a)lists.jboss.org >>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev >>> _______________________________________________ >>> hibernate-dev mailing list >>> hibernate-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev --===============5849910167819139417==-- From mihalcea.vlad at gmail.com Wed Jul 27 03:09:07 2016 Content-Type: multipart/mixed; boundary="===============8243305948856671085==" MIME-Version: 1.0 From: Vlad Mihalcea To: hibernate-dev at lists.jboss.org Subject: Re: [hibernate-dev] People can't find our docs Date: Wed, 27 Jul 2016 10:09:05 +0300 Message-ID: In-Reply-To: CANoTJYPJoVfbiGuKAVvp6Rd332sX4+33EPXDd-Hkd5zsxvZd2w@mail.gmail.com --===============8243305948856671085== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Great news! On Wed, Jul 27, 2016 at 9:56 AM, Davide D'Alto wrote: > Great :) > > now I need to do the same with hibernate.org. > > > On Tue, Jul 26, 2016 at 7:03 PM, Sanne Grinovero > wrote: > > The SEO expert liked the results :) > > > > On 22 July 2016 at 17:33, Emmanuel Bernard > wrote: > >> Hibernate is fine. > >> > >> On Fri 2016-07-22 16:57, Davide D'Alto wrote: > >>> I've updated the microdata on our blog. > >>> I used the google validation page to check the result: > >>> > https://search.google.com/structured-data/testing-tool/u/0/?hl=3DEN#url= =3Dhttp%3A%2F%2Fin.relation.to%2F > >>> > >>> I'm not familiar with microdata, if you think that something is wrong > >>> let me know. > >>> > >>> I have a question about the organization, should I put Red Hat or > Hibernate? > >>> At the moment I'm using Hibernate and hibernate.org as organizarion > >>> url, but let me know. > >>> > >>> Cheers, > >>> Davide > >>> > >>> On Thu, Jul 21, 2016 at 11:26 PM, Guillaume Smet > >>> wrote: > >>> > On Thu, Jul 21, 2016 at 3:06 PM, Sanne Grinovero < > sanne(a)hibernate.org> wrote: > >>> >> Maybe we could move that to the website, as similar metadata is > >>> >> already being deployed, e.g. > >>> >> - > https://github.com/hibernate/hibernate.org/tree/staging/_data/projects/se= arch/releases > >>> > > >>> > We already need to update the /stable/ symlink on the doc server so > we > >>> > might as well do it when we push the doc. > >>> > > >>> > I got something like this: > >>> > https://gist.github.com/gsmet/8c8e29c46337f69bfbc9e84f108d951f . > I'll > >>> > push a PR tomorrow. > >>> > > >>> > I pushed the JS and the metadata to all known doc versions of Search > and OGM. > >>> > > >>> > -- > >>> > Guillaume > >>> > _______________________________________________ > >>> > hibernate-dev mailing list > >>> > hibernate-dev(a)lists.jboss.org > >>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev > >>> _______________________________________________ > >>> hibernate-dev mailing list > >>> hibernate-dev(a)lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/hibernate-dev > >> _______________________________________________ > >> hibernate-dev mailing list > >> hibernate-dev(a)lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > > _______________________________________________ > > hibernate-dev mailing list > > hibernate-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > --===============8243305948856671085==--