Hi, It's an issue we have for several of our projects (ie also on NoORM projects), namely those building the javadoc in an aggregated task at the end of the build.
It bugged me a little at first but as Eclipse defaults to using source anyway, I didn't care that much about this. It might be a good idea to fix it if it does change something for our users. -- Guillaume On Mon, Jan 16, 2017 at 10:17 AM, Sanne Grinovero <sa...@hibernate.org> wrote: > Hi all, > I noticed some people [1] asking why we don't deploy the javadoc > jarfile in Maven repositories. > > That's very helpful for IDE integrations; I never noticed - nor am I > sure how to verify - as my IDE falls back to using the sources. > > Knowing how reliable Maven Central's directory listing are, I'm not > even sure how to double check if this is true or at which level things > might have gone wrong :) > So I didn't open a JIRA yet. Someone more familiar with the ORM build > could double check and take ownership of this please? > > Thanks, > Sanne > > 1 - https://developer.jboss.org/wiki/MavenGettingStarted- > Users?et=watches.email.document_comment#comment-16211 > _______________________________________________ > 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
