CI job spec files are not picking up revremark

[starksm64]

Describe the bug
The jakarta-cdi-spec-4.1.html and jakarta-cdi-spec-4.1.pdf attached to the CDI Release-JDK17 job build artifacts are showing the correct date, but have the revremark from the pom.xml:

4.1, March 07, 2024: Draft(M1)

The job shows that the revremark was override on the command line with -Drevremark=Final.

Expected behavior
The document revremark should be using the override value passed in on the command line from the build job parameters. When I use the same command line on a local build of the 4.1.0 tagged branch I see the spec files with the revremark from the command line.

Additional context
Add any other context about the problem here.

[starksm64]

It seems the release:prepare phase modifies only the versions of the pom files and then creates a separate script to run the release on these. The simplest solution for now is to simply run the build of the spec subproject again after the release build with the license and revremark properties specified. I tried a 5.0.0.Alpha1 build on main with the spec marked as final and that worked. That build has been dropped.