New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

About "JEE" link 404 #58

Open
gm100861 opened this Issue Sep 5, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@gm100861

gm100861 commented Sep 5, 2017

About "JEE" link 404

@bshannon

This comment has been minimized.

Show comment
Hide comment
@bshannon

bshannon Sep 6, 2017

Member

You didn't provide any details, so I'm going to guess that you clicked on the link on the Java EE platform spec repository page, instead of the link on the Java EE platform spec web site. Is that correct?

How did you discover the page that contained the link? Did you find it with a search engine? Did you never actually see the Java EE platform spec web site?

It's a quirk of GitHub that it will automatically add the appropriate extension to file nnames on the web site, but not in the repository view. This has the advantage that we can change the authoring language for the page from markdown to html, for example, without breaking any of the bookmarks to the page. This has the disadvantage that the links in the repository view don't work.

You're the second person to complain about this, so we either need to give up on preserving bookmarks and use the full file name with extension everywhere, or we need to find a better way to make people aware of this issue.

Member

bshannon commented Sep 6, 2017

You didn't provide any details, so I'm going to guess that you clicked on the link on the Java EE platform spec repository page, instead of the link on the Java EE platform spec web site. Is that correct?

How did you discover the page that contained the link? Did you find it with a search engine? Did you never actually see the Java EE platform spec web site?

It's a quirk of GitHub that it will automatically add the appropriate extension to file nnames on the web site, but not in the repository view. This has the advantage that we can change the authoring language for the page from markdown to html, for example, without breaking any of the bookmarks to the page. This has the disadvantage that the links in the repository view don't work.

You're the second person to complain about this, so we either need to give up on preserving bookmarks and use the full file name with extension everywhere, or we need to find a better way to make people aware of this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment