Skip to content

Latest commit

 

History

History
47 lines (38 loc) · 1.77 KB

release_process.adoc

File metadata and controls

47 lines (38 loc) · 1.77 KB

Steps to release wildfly bootable jar maven plugin

STEP 1: Prepare and perform the release

First, make sure you don’t have pending changes in your main branch.

  • cd wildfly-jar-maven-plugin

  • git checkout main

  • git pull --rebase upstream main

  • Update examples/**/helm.yaml with the released tag.

  • Update in pom.xml docs.project.branch to reference the new release

  • Update in pom.xml docs.wildfly.major to reference the WildFly major release (if a new WildFly final release on which the plugin depends has been released).

  • Update the examples/pom.xml file to reference the released plugin

  • Update the examples version:

    • cd examples

    • mvn versions:set -DnewVersion=<new released version> -Drelease

    • mvn versions:commit -Drelease

    • cd ..

  • Commit the changes with message: Update docs and examples to X.X.X.Final

  • Run tests: mvn clean install -Dskip.perf.tests=false

  • mvn release:prepare -Darguments="-DskipTests"

  • mvn release:perform -Darguments="-DskipTests"

  • Update in pom.xml docs.project.branch to reference main

  • Update the examples/pom.xml file to reference the snapshot plugin

  • Update the examples version:

    • cd examples

    • mvn versions:set -DnewVersion=<new snapshot version> -Drelease

    • mvn versions:commit -Drelease

    • cd ..

  • Commit the changes with message: Update docs and examples to X.X.X.Final-SNAPSHOT

  • git push upstream main

STEP 2: Release in Nexus

STEP 3: Release doc in github

  • Attach the docs/target/generated-docs/index.html to the latest release

STEP 3: Release doc in wildfly.github.io

  • Copy generated doc to wildfly.github.io/bootablejar directory

  • Update wildfly.github.io/index.adoc with new release.

  • Open PR.