[teiid-issues] [JBoss JIRA] (TEIIDSB-198) Align with 2.2.6 spring boot
[
https://issues.redhat.com/browse/TEIIDSB-198?page=com.atlassian.jira.plug...
]
Steven Hawkins edited comment on TEIIDSB-198 at 5/7/20 9:18 AM:
----------------------------------------------------------------
IMO, that should not matter, it matters for syndesis-dv app, but not
generated image. The generated Image takes the dependency from the pom.xml we provide that
only refers to teiid spring boot and its chosen version.
That is not the case. The generated pom is taking its spring boot version from syndesis -
ultimately spring-boot.version
Where there is a issue is, for support of few data sources in
syndesis-dv, we use TSB directly that can be version mismatch, but this applies currently
only to "data" stuff.
Yes, I'm saying that both are potentially problems. Syndesis unilaterally moving the
version is problematic for both syndesis-dv and the generated images, but at least there
is some coverage for syndesis-dv.
was (Author: shawkins):
IMO, that should not matter, it matters for syndesis-dv app, but not
generated image. The generated Image takes the dependency from the pom.xml we provide that
only refers to teiid spring boot and its chosen version.
That is not the case. The generated pom is taking it's spring boot version from
syndesis - ultimately spring-boot.version
Where there is a issue is, for support of few data sources in
syndesis-dv, we use TSB directly that can be version mismatch, but this applies currently
only to "data" stuff.
Yes, I'm saying that both are potentially problems. Syndesis unilaterally moving the
version is problematic for both syndesis-dv and the generated images, but at least there
is some coverage for syndesis-dv.
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)