farisbasha opened a new pull request, #460:
URL: https://github.com/apache/commons-codec/pull/460

   The `@see` links to the Caverphone specifications in `Caverphone`, 
`Caverphone1` and `Caverphone2` return 404:
   
   - https://caversham.otago.ac.nz/files/working/ctp150804.pdf (Caverphone 2.0)
   - https://caversham.otago.ac.nz/files/working/ctp060902.pdf (Caverphone 1.0)
   
   The Caversham Project site is still up, but the `files/working/` PDFs are 
gone and I could not find them anywhere else on it. This links to the Internet 
Archive copies of the same PDFs:
   
   - 
https://web.archive.org/web/20230823021823/https://caversham.otago.ac.nz/files/working/ctp150804.pdf
   - 
https://web.archive.org/web/20231002034901/https://caversham.otago.ac.nz/files/working/ctp060902.pdf
   
   Both return 200 (`application/pdf`) without a redirect. Javadoc only, no 
code change.
   
   - [x] Read the [contribution guidelines](CONTRIBUTING.md) for this project.
   - [x] Read the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) if you use 
Artificial Intelligence (AI).
   - [x] I used AI to create any part of, or all of, this pull request. Which 
AI tool was used to create this pull request, and to what extent did it 
contribute? Claude Code (Claude Opus 5.5) found the dead links and made the 
edit. The old and new URLs were checked with `curl`.
   - [ ] Run a successful build using the default 
[Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command 
line by itself. (Not run locally; this is a Javadoc-only `href` change, so this 
relies on CI.)
   - [ ] Write unit tests that match behavioral changes, where the tests fail 
if the changes to the runtime are not applied. (Not applicable: no behavior 
change.)
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [x] Each commit in the pull request should have a meaningful subject line 
and body. Note that a maintainer may squash commits during the merge process.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to