[
https://issues.redhat.com/browse/TEIIDSB-198?page=com.atlassian.jira.plug...
]
Ramesh Reddy commented on TEIIDSB-198:
--------------------------------------
That is not the case. The generated pom is taking its spring boot
version from syndesis - ultimately spring-boot.version
In pom.xml file we use `spring-boot.version` only for the maven-plugin that does
repackaging. Atleast that is how I remember. We can see the log of an image that will
print out the version in use.
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)