[ https://issues.redhat.com/browse/TEIIDSB-198?page=com.atlassian.jira.plug... ] Steven Hawkins edited comment on TEIIDSB-198 at 5/7/20 9:02 AM: ---------------------------------------------------------------- Editing/deleting comments to make this more concise. The short answer for 2.2.4 is that is what the syndesis app is aligned to: https://github.com/syndesisio/syndesis/blob/a920114d2c8df8a36d545b573be6f... The commit https://github.com/syndesisio/syndesis/commit/4372d4f2b29edb5f03f5c07cfc0... is related to the dependabot update to 2.2.6, but as of this typing syndesis is not there yet. This approach is problematic - assuming that syndesis can unilaterally move the spring boot version won't always be valid either for syndesis dv or for the generated image. As we don't test the generated image in the unit tests that is a potential problem. We need to bring the operator into the mix to decouple the runtime version... was (Author: shawkins): See my previous comments and updates to this issue as it looks like syndesis is moving to 2.2.6. The short answer for 2.2.4 is that is what the syndesis app is aligned to: https://github.com/syndesisio/syndesis/blob/a920114d2c8df8a36d545b573be6f... The commit https://github.com/syndesisio/syndesis/commit/4372d4f2b29edb5f03f5c07cfc0... is related to the dependabot update to 2.2.6, but as of this typing syndesis is not there yet. As I point out in the previous commit this approach is problematic - assuming that syndesis can unilaterally move the spring boot version won't always be valid. -- This message was sent by Atlassian Jira (v7.13.8#713008)