Details
-
Task
-
Resolution: Won't Fix
-
L3 - Default
-
None
-
None
-
None
Description
When we decided to move the community extension to an official extension, we agreed, that the latest community version should always be build on to of the latest (minor) spring boot version. We wanted to avoid building a "legacy trap" by trying to support outdated spring boot versions.
Now, with release 7.13 of the starter, it still uses 2.2.5, although 2.3.0 is out.
Keeping my own application close to the latest spring boot tools is quite crucial for spring boot applications, since with every minor release a lot of dependencies change (spring boot being one big "use these versions"-bom) ... when I upgrade my app, I will most probably have to deal with adjustments to data, security and messaging.
With the violation of the "camunda release uses latest spring boot minor" rule, I now fear that approaches of moving my teams microservices to spring boot 2.3.0 will be slowed down by a camunda starter that can (possibly?) not be run with 2.3.0 ...
I would really love to see a quick update of the version, at least for ee customers.
Feel free to contact me to discuss this.