Jim, the spec.version property is the way that we have been designating the version of the specification separate from the project. The spec versions are fairly constant. For example, for JAXR, the spec version will stay at 1.0 until a new spec is defined for JAXR in a future release of Jakarta EE. While the project version may vary depending on updates to the API, Javadoc, or TCK -- thus, the project version for JAXR is currently at 1.0.10. This is why we don't want to change the generation of the spec to use the project.version. We want to use the spec.version property for the generation of the spec. The changes that were recently provided by Scott Kurz accomplished that goal. I don't think we need this PR any longer.
Jim, the spec.version property is the way that we have been designating the version of the specification separate from the project. The spec versions are fairly constant. For example, for JAXR, the spec version will stay at 1.0 until a new spec is defined for JAXR in a future release of Jakarta EE. While the project version may vary depending on updates to the API, Javadoc, or TCK -- thus, the project version for JAXR is currently at 1.0.10. This is why we don't want to change the generation of the spec to use the project.version. We want to use the spec.version property for the generation of the spec. The changes that were recently provided by Scott Kurz accomplished that goal. I don't think we need this PR any longer.