Open amisevsk opened 4 years ago
Issues go stale after 180
days of inactivity. lifecycle/stale
issues rot after an additional 7
days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale
in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen
label to avoid stale mode.
It's not a huge issue, so doing nothing is definitely an option
Considering nothing has been done for nearly 6 months, I tend to agree!
Is your enhancement related to a problem? Please describe.
A couple of devfiles in the devfile registry include plugins that result in pulling both the java8 and java11 sidecar:
This results in the workspace pulling both sidecars and slows down workspace startup.
Describe the solution you'd like
For
apache-camel-springboot
, we should verify that the sample project works withredhat/java11/latest
and if so, switch to that plugin by default. Forche4z
, we should figure out ifbroadcommfd/debugger-for-mainframe/latest
runs normally in the java11 sidecar.Describe alternatives you've considered
It's not a huge issue, so doing nothing is definitely an option