The idea behind this PR to enable tagging of specific commit to release a version of the specification in a repeatable manner.
For example, if we want to release a Public Draft 2 then the properties should be set as shown below:
status = PUBLIC DRAFT 2
revisiondate = August 25, 2020
docversion = 4.0-pd2
Running mvn clean package will yield
jakarta-enterprise-beans-spec-core-4.0-pd2.html
jakarta-enterprise-beans-spec-core-4.0-pd2.pdf
jakarta-enterprise-beans-spec-opt-4.0-pd2.html
jakarta-enterprise-beans-spec-opt-4.0-pd2.pdf
Step 1: Commit the changes
Step 2: Create a tag 4.0-pd2
Step 3: Revert the changes
Step 4: Create a PR
It would be awesome if this could be automated via Jenkins.
Other changes included in this PR are minor corrections:
The idea behind this PR to enable tagging of specific commit to release a version of the specification in a repeatable manner.
For example, if we want to release a Public Draft 2 then the properties should be set as shown below: status = PUBLIC DRAFT 2 revisiondate = August 25, 2020 docversion = 4.0-pd2
Running
mvn clean packagewill yieldStep 1: Commit the changes Step 2: Create a tag 4.0-pd2 Step 3: Revert the changes Step 4: Create a PR
It would be awesome if this could be automated via Jenkins.
Other changes included in this PR are minor corrections: