[
https://issues.redhat.com/browse/TEIIDSB-198?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIIDSB-198:
----------------------------------------
We are not updating this in Syndesis for 7.7 anyways as it going to
be 1.4.0 then why 2.2.4?
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.
Align with 2.2.6 spring boot
-----------------------------
Key: TEIIDSB-198
URL:
https://issues.redhat.com/browse/TEIIDSB-198
Project: Teiid Spring Boot
Issue Type: Task
Components: core
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 1.5.0
Original Estimate: 4 hours
Remaining Estimate: 4 hours
Due to the wildfly updates of TEIID-5859 that pull in a newer cxf and related
dependencies, we end up with version conflicts. The best fix seems to be bumping Teiid
Spring Boot to a later version. The only downside is that later version of spring boot
have switched to jakarta javax dependencies, so we get a lot of duplicate / different
class warnings. We can ignore the errors/warning, try to exclude incoming dependencies
from Teiid, or switch Teiid to use jakarta instead...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)