This discussion occurred in a recent spec review:
@kwsutter I didn't
check "Name of and link to at least one Compatible
Implementation" as ideally the link is to a webpage vs the
actual download. People should really know where they got it
from so they know where to get help and that jakarta.ee is not
the actual producer of the binary. (i.e. they need to see they
left the jakarta.ee website and then get the binary)
@dblevins I think most
people have been doing a direct link. If I just did the download
page (ie. https://projects.eclipse.org/projects/ee4j.glassfish/downloads),
then eventually the user will have to know which version to
select for download. A direct link prevents that question mark.
We can discuss when we review this. Thanks.
I'm moving the discussion here to highlight it and make sure it gets
resolved on the mailing list or in our meeting.
I've seen four approaches to providing a link to go with the
Compatible Implementation entry on the specification page:
- Link directly to the downloadable artifact.
- Link to the project home page.
- Link to a download or releases page.
- Link to the TCK results summary, which also has a link to the
implementation.
It's probably way too late to achieve any sort of consistency for
this release. Personally, I think #2 or #3 is most useful to
developers who will visit the specifications page because it will
make it easier to find other documentation for the Compatible
Implementation, but we should decide if we want to recommend or
require a particular approach in the future.
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
