-
Notifications
You must be signed in to change notification settings - Fork 28
Jakarta Tags Build Process
Paul A. Nicolucci edited this page Aug 20, 2024
·
5 revisions
The jobs for Jakarta Tags can be found here and are accessible to committers to the project.
To build and stage the Jakarta Tags API use the following job: 1_jstl-api-build-and-stage.
- Click "Build with Parameters" and fill in the following parameters:
- RELEASE_VERSION -> This is the version we want to stage. The default value is from the pom.xml, if the pom.xml lists 3.0.0-SNAPSHOT then the release built will be 3.0.0. Ensure the pom.xml has the correct version or specify the version in this property.
- NEXT_VERSION -> This is the next version. The default value is a +1 increment of what is currently in the pom.xml. If 3.0.0-SNAPSHOT is listed in the pom.xml then the next version would be 3.0.1-SNAPSHOT.
- BRANCH -> The default is
master
, if we want to build the3.x
branch then we should specify3.x
in this property. - Several other options are self-describing.
- Click "Build", once completed the artifacts from the build will be deployed to the staging repo.
Review the staged artifacts and when ready to release to maven central use the following job 3_jstl-staging-to-release
- Click "Build with Parameters" and fill in the following parameter:
- STAGING_REPOSITORY_ID -> This can be found in the original build that was used to stage the artifacts.
- Look for the following in the
Console Output
:Created staging repository with ID "jakartaservletjsp-1032"
, thejakartaservletjsp-1032
in the example is the value to be used for theSTAGING_REPOSITORY_ID
.
- Look for the following in the
- STAGING_REPOSITORY_ID -> This can be found in the original build that was used to stage the artifacts.
- Once the job is complete the artifacts will eventually we searchable on Maven Central: https://central.sonatype.com/artifact/jakarta.servlet.jsp.jstl/jakarta.servlet.jsp.jstl-api/versions
Once the artifacts are released to Maven central there is some additional work to be done to finish the release.
- Create a release in GitHub: https://github.com/jakartaee/tags/releases
- Update the following page:https://jakarta.ee/specifications/tags/3.0/ (If the release was for Jakarta Tags 3.0) by creating a PR here: https://github.com/jakartaee/specifications, an example: https://github.com/jakartaee/specifications/pull/770.
- Merge the 3.0.x (3.0.1, 3.0.2...) branch into the 3.x branch. Once merged delete the 3.0.x branch created by the build process.
- Create a release here: https://projects.eclipse.org/projects/ee4j.jstl
- Update this wiki with any changes that are necessary!