On Fri, Feb 2, 2018 at 8:36 AM Guillaume Smet <guillaume.smet(a)gmail.com>
wrote:
On Fri, Feb 2, 2018 at 3:06 PM, Yoann Rodiere
<yoann(a)hibernate.org> wrote:
> @Guillaume, all: I also changed the links of other projects to point to
> Maven Central instead of the JBoss Nexus, because the JBoss Nexus requires
> authentication. And, well, also because... Nexus.
>
Frankly, I find the new Maven Central links (we used JBoss Nexus before
that) you created far more useful than the Bintray page.
Compare:
https://search.maven.org/#search%7Cga%7C1%7Cg%3Aorg.hibernate.validator%2...
with
https://bintray.com/hibernate//artifacts/hibernate-orm/5.3.0.Beta2#
See you cheated though. You "just happened" to use a project that has a
dedicated groupId. If we used a dedicated groupId for ORM
(`org.hibernate.orm` e.g.) then its not a big deal either way.
Craft the same search for ORM and compare (1) the display and (2) the
complexity needed to build the search.
If you don't like the release/version-specific view Bintray offers then
fine - that's your point of view. I just happen to completely disagree.
One goes straight to the point and for the other, it's not that obvious.
And this page is very nice too:
https://search.maven.org/#artifactdetails%7Corg.hibernate.validator%7Chib...
On Bintray, the first artifact presented is agroal which is a bit weird
(yeah I know, alphabetical order but we do better on our pages).
If it were me I would vote for having this layout
http://staging.hibernate.org/validator/releases/6.0/ + the link to
search.maven.org for all the projects. I don't think the Bintray page is
better than what you did with
search.maven.org.
By the way, Bintray should test its UI with Firefox too, it's full of
annoying usability bugs (I experienced 2 just by checking the ORM page)...
Bintray is in fact in the middle of a UI/UX rewrite, so...
And selecting the "main" artifact used in the drop down is one of those
items