${project.basedir} expression not supported during profile activation, use ${basedir} instead @ com.github.hazendaz:base-parent:50

[elharo]

[WARNING]
[WARNING] Some problems were encountered while building the effective model for com.github.spotbugs:spotbugs-maven-plugin:maven-plugin:4.8.6.7-SNAPSHOT
[WARNING] 'profiles.profile[compression].activation.file.exists' Failed to interpolate file location ${project.basedir}/compression.xml for profile compression: ${project.basedir} expression not supported during profile activation, use ${basedir} instead @ com.github.hazendaz:base-parent:50
[WARNING] 'profiles.profile[format].activation.file.exists' Failed to interpolate file location ${project.basedir}/format.xml for profile format: ${project.basedir} expression not supported during profile activation, use ${basedir} instead @ com.github.hazendaz:base-parent:50
[WARNING] 'profiles.profile[license-header].activation.file.exists' Failed to interpolate file location ${project.basedir}/LICENSE_HEADER for profile license-header: ${project.basedir} expression not supported during profile activation, use ${basedir} instead @ com.github.hazendaz:base-parent:50
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]

[hazendaz]

Hmmm... the base parent states that maven 3.9.9 is required to build. Did you skip the enforcer by chance? That change was made somewhere after the original problem that existed for years was fixed in maven 3.9.x series so only 3.9.x should be used to build it. However, one of the GHA used does downgrade to allow maven 3.6.3 to show it working and those profiles were not important enough there but if that is the main concern I can correct that to ensure 3.9.9 builds it and 3.6.3 is used for the IT tests on that GHA run.