Purpose of spec-version-maven-plugin

[KyleAure]

The API build depends on this plugin:

concurrency/api/pom.xml

Lines 74 to 94 in d24bd40

	<!-- First sets properties for the maven-bundle-plugin and later checks if they are indeed used. -->
	<plugin>
	<groupId>org.glassfish.build</groupId>
	<artifactId>spec-version-maven-plugin</artifactId>
	<version>2.1</version>
	<configuration>
	<spec>
	<specVersion>3.1</specVersion>
	<specImplVersion>${project.version}</specImplVersion>
	<apiPackage>jakarta.enterprise.concurrent</apiPackage>
	</spec>
	</configuration>
	<executions>
	<execution>
	<goals>
	<goal>set-spec-properties</goal>
	<goal>check-module</goal>
	</goals>
	</execution>
	</executions>
	</plugin>

Which currently fails our release build when attempting to create a release with the tag 3.1.0-M1
Due to this known issue: eclipse-ee4j/glassfish-spec-version-maven-plugin#14

[INFO] --- spec-version:2.1:check-module (default) @ jakarta.enterprise.concurrent-api ---

[ jakarta.enterprise.concurrent:jakarta.enterprise.concurrent-api:3.1.0-M1 ]
{ groupIdPrefix=jakarta. spec-version=3.1 apiPackage=jakarta.enterprise.concurrent API final spec-impl-version=3.1.0-M1 }
- WARNING: Bundle-Version (3.1.0.M1) should be 3.1.0-M1

What exactly is the purpose of this plugin and is it necessary?
I can work around it for this release, but long term it might be a problem.