Throwing a couple of suggestions out there:
- build on 17
- backport to Java8?
- try a couple of those options out from the linked post but as James said
they all have issues by the looks of it

On Wed, 15 Jun 2022 at 17:33, '[email protected]' via Jenkins Developers <
[email protected]> wrote:

> Good find Basil,
>
> the above issue I mentioned with search seems to be
> https://bugs.openjdk.org/browse/JDK-8215291  which is alas also fixed in
> Java 12....
>
> Stack overflow[1] mentions some workarounds, but they appear to have other
> issues.
>
> /James
>
> [1]
> https://stackoverflow.com/questions/52326318/maven-javadoc-search-redirects-to-undefined-url
>
> On Wednesday, June 15, 2022 at 5:29:12 PM UTC+1 [email protected] wrote:
>
>> I am seeing some issues with the actual jenkins java11 javadoc too.
>> Smells like bugs in javadoc - but it may be out invocation of it is not
>> correct.
>>
>> The search seems to be broken - when you follow a link to a type you get
>> linked to a page that starts https://javadoc.jenkins.io/undefined  e.g.
>> https://javadoc.jenkins.io/undefined/hudson/security/AccessControlled.html)
>>  it only seems to do the right thing when what you are searching for is a
>> package but reliably fails for types.
>>
>> /James
>>
>> On Tuesday, June 14, 2022 at 7:08:14 PM UTC+1 [email protected] wrote:
>>
>>> The problem can be reproduced by going to any Jenkins plugin today and
>>> running mvn javadoc:javadoc with Java 8. The problem does not occur
>>> when running the same Maven command with Java 11. So one solution is to
>>> perform the release with Java 11 (as we are doing with Jenkins core today).
>>>
>>> I suspect this may have something to do with the renaming of
>>> package-list to element-list in Java 10. I see
>>> https://javadoc.jenkins.io/element-list but
>>> https://javadoc.jenkins.io/package-list gives a 404 (Javadoc built with
>>> Java 11). In contrast, I see
>>> https://javadoc.jenkins.io/component/jenkins-test-harness/package-list
>>> but
>>> https://javadoc.jenkins.io/component/jenkins-test-harness/element-list
>>> gives a 404 (Javadoc built with Java 8). If this theory is correct, another
>>> solution might be to symlink package-list to element-list as was
>>> effectively done in gradle/gradle@
>>> 5e88351dd456a5252d21f3a7ad25bff1b62a2fd2
>>> <https://github.com/gradle/gradle/commit/5e88351dd456a5252d21f3a7ad25bff1b62a2fd2>
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/bcb4529f-7531-4e62-9dbc-836ea265bf98n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/bcb4529f-7531-4e62-9dbc-836ea265bf98n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BiegTCk7AGMVJcDbgeK%2BTuwCa6-TcqBWk%3DB%3DWZDaOVsHrw%40mail.gmail.com.

Reply via email to