I agree, unless someone wats to step up to make it actually nice looking and will keep them nice looking for a while, be a bit proactive regarding JDK versions, consistent across projects, etc..
Since we don't have the bandwith for that the default look is compelling. Java 9 makes the javadoc much more useful: it introduces a very handy search box so I'd like to build Javadocs with Java 9 soon.. not having the deal with the custom styling would make it easier. Sanne On 30 November 2017 at 15:11, 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