Skip to content

fix: handle missing JBoss configuration children - #562

Open
efegokdemir wants to merge 1 commit into
apache:masterfrom
efegokdemir:codex/issue-513-null-jboss-config
Open

efegokdemir wants to merge 1 commit into
apache:masterfrom
efegokdemir:codex/issue-513-null-jboss-config

Conversation

@efegokdemir

Copy link
Copy Markdown

Summary

initializeJbossConfiguration now treats omitted optional JBoss configuration elements as absent values instead of dereferencing null children. This addresses #513 without changing the generated configuration for supplied elements.

Changes

  • Safely read optional child values and attributes, including loader repository settings.
  • Added a regression test covering a minimal JBoss configuration with omitted optional children.

Testing

  • mvn -B -ntp -DskipITs -Dspotless.check.skip=true -Dspotless.apply.skip=true test — passed (49 tests).
  • mvn -B -ntp -DskipITs -Dspotless.check.skip=true -Dspotless.apply.skip=true verify — passed.
  • git diff --check — passed.
  • mvn -B -ntp -Prun-its -Dspotless.check.skip=true -Dspotless.apply.skip=true verify — blocked by the local Java 8/Groovy environment: the Invoker tests report Unsupported class file major version 71; the failure occurs before the scenario assertions.

AI assistance was used during analysis and implementation; the patch and test results were reviewed before submission.

Fixes #513

Signed-off-by: Efe Gökdemir <efe@rexcode.co.uk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

NullPointerException on missing Plexus config children in AbstractEarMojo.initializeJbossConfiguration()

1 participant