Uploaded image for project: 'Build'
  1. Build
  2. BUILD-753

Make sure that latest versions of internal modules are used (even when not in CL)

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Neutral
    • None
    • None
    • None
    • None

    Description

      Note: this is true exclusively of bundles.

      In the 6.2.18 release lang 1.1.10 was the latest available version but was not updated in CE pom by any developer and wasn't present in the CL. Hence, the 1.1.9 version was released.

      A preflight check could make sure that internal dependencies are at their latest available releases.

      Maven version plugin could possibly be used to that purpose, e.g. for properties

      mvn versions:update-properties -DallowIncrementalUpdates=true -DallowMajorUpdates=false -DallowMinorUpdates=false

      and for dependencies 

      mvn versions:use-releases
      

      Even easier: let's configure Renovate to access Nexus so it can see where we fall behind with our own artifacts.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                mmichel Maxime Michel
                mmichel Maxime Michel
                Foundation
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:
                  Work Started:

                  Checklists

                    Task DoR