The problem w/ the previous scheme of *-maven-latest is that all SCDF versions UI reference this when loading default apps. This is brittle. This is the equivalent of using a wildcard version for a dependency.
This proposal moves the scheme to *-maven-2024-0-x where instead of latest we have the MAJOR/MINOR lock and we allow live patch updates (which should not be breaking).
The next move is that the dataflow UI will replace usages of *-maven-latest w/ *-maven-M-N-x where M-N will be derived from the default stream apps version that Dataflow server is using.
See https://github.com/spring-cloud/spring-cloud-dataflow/issues/5897
The problem w/ the previous scheme of
*-maven-latestis that all SCDF versions UI reference this when loading default apps. This is brittle. This is the equivalent of using a wildcard version for a dependency.This proposal moves the scheme to
*-maven-2024-0-xwhere instead of latest we have the MAJOR/MINOR lock and we allow live patch updates (which should not be breaking).The next move is that the dataflow UI will replace usages of
*-maven-latestw/*-maven-M-N-xwhereM-Nwill be derived from the default stream apps version that Dataflow server is using.