It's the GlassFish plugin. It's not really GlassFish-specific as it
is Java EE and now Jakarta EE specific.
Should we maybe rename it to jakartaee-spec-version-maven-plugin or something like that?
Kind regards,
Arjan
It's a tool to help projects get the metadata right. It's not
required for spec projects, but it's strongly encouraged.
Kevin Sutter wrote on 2/18/20 6:38 AM:
Hi Arjan, Can you
clarify
which specific plugin you are referring to? Is it theglassfish-spec-version-maven-plugin?
Or, is there a generic, non-glassfish version that you are
modifying?
And, I'm curious why only a handful of APIs are having this
issue.
Is this plugin not used by all of the Spec/API projects?
Should
it be used? Thanks for the education.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
I think I have encountered the same
issue
but when trying to create an "-M1" version on Jakarta
Transactions.
Would a similar change be possible for that type of qualifier?
I've updated the plug-in to threat
RC1
essentially the same as a -SNAPSHOT qualifier, meaning it's
stripped-off
for the sake of the spec-version-maven-plugin. This works with
the
regular final mode (the default), which is the same as for the
-SNAPSHOT
qualifier.
The result is a MANIFEST.MF with the
relevant version set (in this case) to 2.0.0.