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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

I personally think that publishing Javadocs per artifact is silly so I do not do it for ORM. Its a limiting view. We already publish an "aggregated" Javadoc that (again imo) is far better. As you point out Sanne, we do publish sources to repo which at the IDE level is MUCH better On Mon, Jan 16, 2017 at 3:28 AM Guillaume Smet <guillaume.smet(a)gmail.com&gt; wrote: > 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 <sanne(a)hibernate.org&gt; > 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(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

I agree with Steve and Gunnar. On 16 January 2017 at 15:41, Gunnar Morling <gunnar(a)hibernate.org&gt; wrote: > +1 The source JARs are the important thing here. > > Just tried out the JavaDoc view in Eclipse for the first time as > you're mentioning it. Can't say I find it overly useful nor that I've > been missing it for all these years :) > > 2017-01-16 15:43 GMT+01:00 Steve Ebersole <steve(a)hibernate.org&gt;: > > I personally think that publishing Javadocs per artifact is silly so I do > > not do it for ORM. Its a limiting view. We already publish an > > "aggregated" Javadoc that (again imo) is far better. As you point out > > Sanne, we do publish sources to repo which at the IDE level is MUCH > better > > > > On Mon, Jan 16, 2017 at 3:28 AM Guillaume Smet <guillaume.smet(a)gmail.com > > > > wrote: > > > >> 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 <sanne(a)hibernate.org&gt; > >> 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(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

I think we are all saying that we personally find it far more useful to have the sources (which have the Javadoc btw ;) available in the IDE compared to having just the Javadoc.

It's not a question of easy to generate/publish, it's a question of what is useful. If someone finds it useful they can certainly submit a PR

And btw I use IntelliJ which has had this forever. I have used it in the past and as I have stated I find it less useful than having the sources available. On Mon, Jan 16, 2017, 10:25 AM Sanne Grinovero <sanne(a)hibernate.org&gt; wrote: > > I'm not sure if the agreement is in wanting to keep the status quo, or > if it's simply not worth our time to chase such things. In other > words: may I suggest to such users that we'd accept a pull request, or > you'd rather not waste bandwidth during releases? > > Either way is fine by me, but I wonder if users from other IDEs and > tools are getting left in the dark for something which we'd have a > script do. > > On 16 January 2017 at 15:55, andrea boriero <andrea(a)hibernate.org&gt; wrote: > > I agree with Steve and Gunnar. > > > > On 16 January 2017 at 15:41, Gunnar Morling <gunnar(a)hibernate.org&gt; > > wrote: > > > >> +1 The source JARs are the important thing here. > >> > >> Just tried out the JavaDoc view in Eclipse for the first time as > >> you're mentioning it. Can't say I find it overly useful nor that I've > >> been missing it for all these years :) > >> > >> 2017-01-16 15:43 GMT+01:00 Steve Ebersole <steve(a)hibernate.org&gt;: > >> > I personally think that publishing Javadocs per artifact is silly so > >> > I do > >> > not do it for ORM. Its a limiting view. We already publish an > >> > "aggregated" Javadoc that (again imo) is far better. As you point > >> > out > >> > Sanne, we do publish sources to repo which at the IDE level is MUCH > >> better > >> > > >> > On Mon, Jan 16, 2017 at 3:28 AM Guillaume Smet > >> > <guillaume.smet(a)gmail.com > >> > > >> > wrote: > >> > > >> >> 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 > >> >> <sanne(a)hibernate.org&gt; > >> >> 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(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 > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev