SNOMED International Mapping Tool

Space shortcuts

Child pages
  • Versioning "develop" and "master"

Versions Compared

Old Version 7

changes.mady.by.user Deborah Shapiro

Saved on

compared with

New Version 8

changes.mady.by.user Rick Wood

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NOTE: Confirm that pom-us.xml also gets versioned appropriately.  If not, updated manually.

NOTE: you may notice the complexity of running versions:set twice.  This is because of the split nature of the parent and aggregator modules.  It is recommended in the future that parent project be merged into the aggregator and removed.  Thant involves:

  1. Moving the dependencyManagement section from parent/pom.xml to pom.xml
  2. Moving the pluginManagement section from parent/pom.xml to pom.xml
  3. Removing "parent" from the modules list in pom.xml
  4. Updating pom.xml to remove the "<parent>" section at the top (it is now the parent)
  5. Also change pom.xml description to indicate that it is both parent and aggregator
    1. in particular, change the artifactId to be "...-parent" instead of "...-aggregator" (this is for the next part)
  6. update all other pom.xml files in submodules to change the relativePath to the parent module 
    1. from "../parent" to ".." 
    2. OR from "../../parent" to "../.."


Managing Hotfixes

Occasionally, only a select few commits from develop need to be deployed on production as a hotfix.  In these cases, the full merging from develop to master is inappropriate, and the following steps should be followed instead:

  • n/a