See attached screenshot.

Please note that it may be an issue of plugin broker but not workspace loader.
Thanks @sleshchenko. Who can handle it?
maybe that it is first downloading java extension and then java debug extension ?
Who can handle it?
@slemeur I think OSIO team is the main contributor to che-plugin-broker, but the platform team is able to handle it as well.
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.
Is already fixed by https://github.com/eclipse/che-plugin-broker/pull/66
Most helpful comment
https://github.com/eclipse/che-plugin-registry/blob/master/v3/plugins/redhat/java/0.43.0/meta.yaml#L17 and then https://github.com/eclipse/che-plugin-registry/blob/master/v3/plugins/redhat/java/0.43.0/meta.yaml#L18