Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-31557

Javadoc testing fails due to version mismatch between devtag sources and Prospero manifest

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 8.1.z.GA
    • Javadoc
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      Javadoc tests currently compare documentation against a prospero/manifest-aligned server zip, which can result in false positives when artifact versions differ between the source code (devtag) and the final manifest. e.g. JBEAP-29515

      Root Cause: Build Process Architecture

      The current build process creates javadocs and the final server at different stages, leading to version misalignment:

      1. Build server in PNC - Javadocs are generated here from source code (devtag)
      2. Build components (e.g., hibernate)
      3. Build set manifest
      4. Build plugins and feature packs (prospero, EAP maven plugin)
      5. Create final manifest - Set manifest merged with other manifests
      6. Create server zip with prospero - Uses the final manifest

      The javadocs are created from source code in step 1, but the server zip is built with potentially different artifact versions from the final manifest in step 6.

      After discussions with rh-ee-rnovelli it seems solution would require new PNC build with final manifest ( this would result in new server version). Luckily amount of false positives is small so setting lower priority

              rh-ee-rnovelli Ruben Novelli
              ldokoupi@redhat.com Ladislav Dokoupil
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: