Visitar URL original
Navigation to `assertj-core` or `guava` types from `assertj-guava` Javadoc site has unnecessary header · Issue #3478 · assertj/assertj · GitHub
Skip to content

Navigation to assertj-core or guava types from assertj-guava Javadoc site has unnecessary header #3478

Description

@scordio

For example, when opening org.assertj.guava.api.OptionalAssert and clicking on an org.assertj.core.api.Assert hyperlink, the following is displayed:

image

There is the javadoc.io header for assertj-core header, which shouldn't appear. Plus, the referred assertj-core version is 3.25.2 instead of 3.25.3.

Something similar happens when clicking on Guava Optional:

Screenshot 2024-05-26 at 11 12 08

On the other side, clicking on an Object hyperlink properly navigates to the Oracle Javadoc:

image

Activity

  1. added this to the 3.26.0 milestone on May 24, 2024
  2. self-assigned this
    on May 25, 2024
  3. changed the title [-]Navigation to `assertj-core` types from `assertj-guava` Javadoc site has unnecessary header[/-] [+]Navigation to `assertj-core` or `guava` types from `assertj-guava` Javadoc site has unnecessary header[/+] on May 26, 2024
  4. modified the milestones: 3.26.0, 3.27.0 on May 26, 2024
  5. scordio commented on Jan 18, 2025

    @scordio
    MemberAuthor

    Apparently, b64ed7a wasn't enough to resolve the issue.

  6. modified the milestones: 3.27.0, 4.0.0-M1 on Jan 18, 2025
  7. modified the milestones: 4.0.0-M1, 4.0.0-M2 on Jan 31, 2025
  8. modified the milestones: 4.0.0-M2, 3.28.0 on Dec 20, 2025
  9. scordio commented on Dec 20, 2025

    @scordio
    MemberAuthor

    Fixed in 20c213d.

  10. scordio commented on Jan 24, 2026

    @scordio
    MemberAuthor
  11. Marcono1234 commented on Feb 12, 2026

    @Marcono1234
    Contributor

    Might be best to raise this as issue at https://github.com/maxcellent/javadoc.io/issues (in case it hasn't been reported yet).
    This header is something added by javadoc.io, it does not exist in the original Javadoc. The same issue also exists for other projects, e.g. Jackson Databind (click on the link to TreeCodec).

    The problem seems to be that when clicking links on javadoc.io, it merely adds the target site as nested iframe which therefore leads to a duplicate header when the target site is javadoc.io itself.

    And it can even lead to a browser error page when the target site does not permit being embedded in an iframe. Not sure why javadoc.io is using these nested iframes in the first place, maybe that is actually unintentional?

  12. scordio commented on Feb 27, 2026

    @scordio
    MemberAuthor

    Thanks for the suggestion, @Marcono1234! We might have more than one problem, though. At least as a first step, I'd like to clarify the appropriate configuration of the maven-javadoc-plugin when building a module that depends on another module, both of which belong to the same multimodule project.

    I briefly discussed with @michael-o that we'll compose a small reproducer so he can take a look.

  13. modified the milestones: 3.28.0, 3.x on Jun 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions