Skip to content

Arraylist Java reference link is now 404 #788

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

Closed
jeremydouglass opened this issue Dec 16, 2019 · 5 comments · Fixed by #791
Closed

Arraylist Java reference link is now 404 #788

jeremydouglass opened this issue Dec 16, 2019 · 5 comments · Fixed by #791

Comments

@jeremydouglass
Copy link
Contributor

Issue description

Reference pages that link to Oracle's JavaSE 1.5 pages are now 404.

For a list of the numerous ArrayList features, please read the Java reference description.

URL(s) of affected page(s)

https://processing.org/reference/ArrayList.html

I haven't checked if there are other "javase/1,5.0" URLs in the reference -- if so, I assume that those are broken as well.

Proposed fix

  1. move this 5 link (and any others) to Java 6 -- https://docs.oracle.com/javase/6/docs -- like the one used in the HashMap reference page, which still works
  2. OR better, make the whole reference consistent and change all Oracle links, both broken and working, to point to javase/8 reference pages. This would match the underlying build.

I won't submit a pull request unless there is a response from core dev(s) on what they want these Oracle Java reference links to do going forward.

@REAS
Copy link
Member

REAS commented Dec 18, 2019

Yes, it would be great to update these links. But, I am concerned about them breaking again in the future, or becoming outdated. I'm specifically concerned about this because I hope to work with others in 2020 to translate the site into other languages. Broken links will then propagate to other translations.

@jeremydouglass
Copy link
Contributor Author

@REAS so maybe remove those links from individual reference pages entirely?

Or have all those links throughout all reference pages point to a single Processing reference page like "Using the Java Reference" about the Java reference and how to use it https://processing.org/reference/java_reference ? That would be much more maintainable, no matter what Oracle gets up to with its URLs in the future.

@DamienMutiDesgrouas
Copy link

DamienMutiDesgrouas commented Dec 24, 2019

Indeed, the link towards ArrayLIst's JavaDoc is down.
After a quick and simple search on the web :
https://docs.oracle.com/javase/7/docs/api/java/util/ArrayList.html
maybe this one is better :

http://docs.oracle.com/javase/1.5.0/docs/api/java/util/ArrayList.html

@benfry
Copy link
Contributor

benfry commented Jan 7, 2020

If anything, the Java 8 docs would probably be the way to go: https://docs.oracle.com/javase/8/docs/api/

That's the version of Java that's being used, and should remain around for a while.

jeremydouglass added a commit to jeremydouglass/processing-docs that referenced this issue Jan 8, 2020
...including:
1. broken links (e.g. ArrayList),
2. forwarded links that have been migrated from http to https, and
3. bumping up links pointing back at JavaSE 5/6/7 documentation when the underlying build is 8.

Closes processing#788
@jeremydouglass
Copy link
Contributor Author

jeremydouglass commented Jan 8, 2020

2. make the whole reference consistent and change all Oracle links, both broken and working, to point to javase/8 reference pages. This would match the underlying build.

the Java 8 docs would probably be the way to go: https://docs.oracle.com/javase/8/docs/api/ That's the version of Java that's being used

Great, sounds like concensus on Java 8 links.

I am concerned about them breaking again in the future, or becoming outdated

...maybe we can centralize / rework / drop those links before the translation effort? The oracle links in question are all documented by the changes in the pull request that I have added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants