In general I agree. This was a big hassle when Oracle re-did the JavaDoc generation a few releases ago (was it 6?).
IMO though its still a nice touch to "skin" the coloring in the nav bars, main header, footer etc. I have not looked into how much work just those limited changes would be however. If that is sufficiently difficult to maintain, then I'm all for just dropping the CSS altogether On Thu, Nov 30, 2017 at 10:53 AM Guillaume Smet <guillaume.s...@gmail.com> wrote: > Hi, > > So, apparently, our JavaDoc CSS is a bit outdated as we now have a "Skip > navigation links" link at the top of our doc that should be hidden by > default. > > Frankly, I see very little value in maintaining our own JavaDoc CSS. It > requires work (see above and the future JDK 9 upgrade - Marko did a first > pass on Validator but it required some time). > > Moreover, I find the new default CSS much more readable and attractive than > ours. > > Compare: > https://docs.jboss.org/hibernate/stable/search/api/ > with: > http://docs.jboss.org/jberet/1.3.0.Beta2/javadoc/jberet-core/ > > I would say a JavaDoc is a JavaDoc and I would prefer if our users just got > the standard layout they are used to on other projects. > > Bonus point: when we include external projects javadoc in ours, we end up > having both layouts mixed, which is not very nice. > > And if it saves us some work, it's all good, isn't it? > > Thoughts? > > -- > Guillaume > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
