Junit5: Cannot access `package-list` in published Javadoc

Created on 8 Feb 2018  路  21Comments  路  Source: junit-team/junit5

Bug Report for JUnit 4

javadoc -link http://junit.org/junit4/javadoc/latest (i.e. referring JUnit 4's Javadoc pages from 3rd-party Javadoc pages) no longer works because http://junit.org/junit4/javadoc/latest/package-list disappeared.

Deliverables

Bug Report for JUnit 5

An upgrade in the JDK used to generate Javadoc for JUnit 5 caused the package-list file to stop being published beginning with JUnit 5.2.

In the following list, the first number is the HTTP response code.

Deliverables

  • [x] Manually copy element-list to package-list for previously released versions of JUnit 5.
  • [x] Automate copying of element-list to package-list in the Gradle build for future versions of JUnit 5.
web site bug

All 21 comments

Please note that this is the issue tracker for JUnit 5 (not for JUnit 4).

Are you referring to a link to JUnit 4 from the JUnit 5 User Guide or the JavaDoc for JUnit 5?

If not, please open an issue against JUnit 4.

I've disabled Cloudflare's Browser Integrity Check.

@KMGraf Can you please try again?

Oh, have you tried using HTTPS?

I changed to https which alone did not help. But now after your change everything is ok again. Thank you for your quick response.

@onacit, that's because there is no package-list folder or file in that directory.

https://github.com/junit-team/junit5/tree/gh-pages/docs/current/api

Why/how are you trying to access that URL?

FYI: the new location for that package-list file is the following:

https://github.com/junit-team/junit5/blob/gh-pages/docs/current/api/element-list

Or this URL for the current "published" version:

https://junit.org/junit5/docs/current/api/element-list

Also, it appears you will need to use Java 10 or higher (e.g., JDK 11) to access the element-list file instead of the package-list file automatically.

This is explained here: https://stackoverflow.com/a/49498219/388980

The rationale for the change in the JDK is documented in this proposal:

https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8191363

After further analysis, I have determined that an upgrade in the JDK used to generate Javadoc for JUnit 5 caused the package-list file to stop being published beginning with JUnit 5.2.

In the following list, the first number is the HTTP response code.

I am reopening this issue in order to address the recently reported issue with package-list for JUnit 5. See previous comments.

_in progress_

FYI: I overhauled this issue's description in order to cover both JUnit 4 and JUnit 5.

In case we are ever interested in tracking down the exact changes that introduced this _bug_ for JUnit 5, I noticed that the change must have happened between JUnit 5.2 M1 and 5.2 RC1.

I've changed our build to copy element-list to package-list in dd68fbad1854ba349dde481116562224c2d284e3.

I manually copied element-list to package-list for all previously releases in 7e1cef4aad91bcd9d20de379dc6b55432c8e2947.

I receive 404 from https://junit.org/junit5/docs/current/api/package-list.

@onacit, that should now work for you. Please let us know if it does not.

I just downloaded the jars for 5.62 (Vintage and Jupiter) and 1.62 (Platform) from the link on the main page, and this is still an issue. Is there any chance this bug will be fixed?

I would like to mention the links on the JUnit 5 main page are to 5.6.1 for Jupiter and Vintage and the platform is linked to 1.6.1 even though they are labeled as 5.6.2 and 1.6.2.

I would like to mention the links on the JUnit 5 main page are to 5.6.1 for Jupiter and Vintage and the platform is linked to 1.6.1 even though they are labeled as 5.6.2 and 1.6.2.

Fixed via https://github.com/junit-team/junit5/commit/989dff30872fe9a77e38b07a0e4c1acdbc4672e5 -- thanks for the heads up.

I just downloaded the jars for 5.62 (Vintage and Jupiter) and 1.62 (Platform) from the link on the main page, and this is still an issue. Is there any chance this bug will be fixed?

fup2 #2278

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mkobit picture mkobit  路  5Comments

netzwerg picture netzwerg  路  6Comments

galan picture galan  路  3Comments

timandy picture timandy  路  3Comments

PeterWippermann picture PeterWippermann  路  5Comments