Uploaded image for project: 'repository.jboss.org/nexus'
  1. repository.jboss.org/nexus
  2. NEXUS-1063

Validation treats plugin configuration content as top-level pom content -- part 2

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • Q4CY25
    • None
    • Maven Central Plugin
    • None
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • MWES 2025-10-25, MWES 2025-11-11, MWES 2025-11-25, MWES 2026-01-05

      This is similar to the NEXUS-967 problem, but with 'scm' and 'description' elements and different plugins being configured.

      A run of the "Validation: wildfly-staging" task reported:

      Processed 8 components.

      • 2 problems found!
           - [jakarta.el:jakarta.el-api:6.0.1-jbossorg-1]: pom.xml validation failed: /jakarta/el/jakarta.el-api/6.0.1-jbossorg-1/jakarta.el-api-6.0.1-jbossorg-1.pom at [144,26]: source code source (scm) appeared outside its expected location in xml.
           - [jakarta.el:jakarta.el-api:6.0.1-jbossorg-1]: pom.xml validation failed: /jakarta/el/jakarta.el-api/6.0.1-jbossorg-1/jakarta.el-api-6.0.1-jbossorg-1.pom at [245,42]: description appeared outside its expected location in xml.

       

      These links show the plugin config elements that trigger those errors:

      https://gist.github.com/bstansberry/af614b8fb4e36d23d33f969e8f55f56f#file-gistfile1-txt-L144

      https://gist.github.com/bstansberry/af614b8fb4e36d23d33f969e8f55f56f#file-gistfile1-txt-L245

       

      I'll see if I can work around this. I'll delete the staged artifacts.

              dhladky@redhat.com David Hladky
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: