[JBoss JIRA] (TEIIDSB-192) Document migration for alias names
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-192?focusedWorklogId=12450976&pa... ]
Steven Hawkins logged work on TEIIDSB-192:
------------------------------------------
Author: Steven Hawkins
Created on: 07/May/20 9:27 AM
Start Date: 07/May/20 9:27 AM
Worklog Time Spent: 2 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 2 hours)
Time Spent: 4 hours (was: 2 hours)
Worklog Id: (was: 12450976)
> Document migration for alias names
> ----------------------------------
>
> Key: TEIIDSB-192
> URL: https://issues.redhat.com/browse/TEIIDSB-192
> Project: Teiid Spring Boot
> Issue Type: Task
> Components: documentation
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.5.0
>
> Original Estimate: 4 hours
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> Translators like salesforce and actian-vector has new name in the spring boot, we need to either document or switch back to original names.
> Also if we are updating migration utilities we can build in smarts into it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (TEIIDSB-198) Align with 2.2.6 spring boot
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-198?page=com.atlassian.jira.plug... ]
Steven Hawkins edited comment on TEIIDSB-198 at 5/7/20 9:24 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
https://github.com/syndesisio/syndesis/blob/bdf8726f2ea16ae549ac253a43fd5...
https://github.com/syndesisio/syndesis/blob/bdf8726f2ea16ae549ac253a43fd5...
It's the second one that pulls in a newer spring boot starter and related dependencies.
> 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 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.
> 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)
5 years, 11 months
[JBoss JIRA] (TEIIDSB-198) Align with 2.2.6 spring boot
by Ramesh Reddy (Jira)
[ 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)
5 years, 11 months
[JBoss JIRA] (TEIIDSB-198) Align with 2.2.6 spring boot
by Steven Hawkins (Jira)
[ 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)
5 years, 11 months
[JBoss JIRA] (TEIIDSB-198) Align with 2.2.6 spring boot
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-198?page=com.atlassian.jira.plug... ]
Steven Hawkins commented on TEIIDSB-198:
----------------------------------------
> 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)
5 years, 11 months
[JBoss JIRA] (TEIIDSB-198) Align with 2.2.6 spring boot
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-198?page=com.atlassian.jira.plug... ]
Ramesh Reddy commented on TEIIDSB-198:
--------------------------------------
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. 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.
> 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)
5 years, 11 months
[JBoss JIRA] (TEIIDSB-198) Align with 2.2.6 spring boot
by Steven Hawkins (Jira)
[ 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:
----------------------------------------------------------------
> We are not updating this in Syndesis for 7.7 anyways as it going to be 1.4.0 then why 2.2.4?
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):
> 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)
5 years, 11 months
[JBoss JIRA] (TEIIDSB-198) Align with 2.2.6 spring boot
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-198?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIIDSB-198:
-----------------------------------
Comment: was deleted
(was: Actually that syndesis commit highlights several problems:
* first they are independently moving the spring boot version for the generated teiid image regardless of the teiid spring version - in general that shouldn't be expected to work
* second that is only updating the generated image version. syndesis itself is still using 2.2.4. That may follow in a later commit, but it could temporarily be a problem if both don't align)
> 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)
5 years, 11 months
[JBoss JIRA] (TEIIDSB-198) Align with 2.2.6 spring boot
by Steven Hawkins (Jira)
[ 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)
5 years, 11 months
[JBoss JIRA] (TEIIDSB-198) Align with 2.2.6 spring boot
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-198?page=com.atlassian.jira.plug... ]
Steven Hawkins commented on TEIIDSB-198:
----------------------------------------
Actually that syndesis commit highlights several problems:
* first they are independently moving the spring boot version for the generated teiid image regardless of the teiid spring version - in general that shouldn't be expected to work
* second that is only updating the generated image version. syndesis itself is still using 2.2.4. That may follow in a later commit, but it could temporarily be a problem if both don't align
> 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)
5 years, 11 months