Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CRW-2591 - migrate Camel on springboot stack to java 11 #705

Conversation

apupier
Copy link
Member

@apupier apupier commented Mar 14, 2022

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
@apupier apupier force-pushed the crw-2-rhel-8-CRW-2591-Java11Migration branch from ff32875 to 834092e Compare March 14, 2022 12:56
@apupier apupier marked this pull request as ready for review March 14, 2022 13:04
@nickboldt
Copy link
Member

With this change, are s390x or ppc64le supported? If so, we can remove the zero-length files for arches that are now supported.

@nickboldt nickboldt merged commit 1b24d8e into redhat-developer:crw-2-rhel-8 Mar 14, 2022
@nickboldt
Copy link
Member

@apupier
Copy link
Member Author

apupier commented Mar 14, 2022

With this change, are s390x or ppc64le supported? If so, we can remove the zero-length files for arches that are now supported.

I think not directly.
The example migth need to be adjusted. Thi work has not been done in Red hat Intgeration https://issues.redhat.com/browse/ENTESB-17454?focusedCommentId=19578893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-19578893 so I do not know exactly.

it would require more investigation and testing than I'm unable to do.

As far as I know, the image mentioned here https://github.com/crw-samples/fuse-rest-http-booster/blob/edd52526643a4c51d5c5d7b9741d9394664704e6/pom.xml#L19 will need to be adjusted to use an IBm compatible version as I mentioned here https://issues.redhat.com/browse/ENTESB-17454?focusedCommentId=19529070&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-19529070
Also, as afar as I know, it was using openj9 and it is subject to be modified for next Fuse version because it wasn't compliant with legal so cannot be used yet. (but not finding a reference to that again)

@nickboldt
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants