Bitbucket installer should not ignore adding the bundled JRE

When installing or upgrading a Bitbucket instance the installer ignores to add the bundled JRE if a compatible JAVA installation is found on the server.

This is not good if you want to use the bundled JRE and still need to have JAVA installed for other purposes on the server. The only workaround to use the bundled JRE is to first uninstall any JAVA distributions, then install Bitbucket and then re-install the JAVA distribution.

This seems totally unnecessary since you can control what JRE to use by using the JAVA_HOME and/or JRE_HOME variables to indicate to the application what JRE/JDK to use. This is the way both JIRA and Confluence works

In my specific use-case I have the Support Tools package from Atlassian Labs available on the server and this require JDK to be installed. But this doesn't make me want to run Bitbucket itself with a separate JDK distribution. I still want to run Bitbucket with the bundled JRE since this gives me a more complete installation and configuration experience as an admin.

There is a support issue raised from my side: SSP-18250

I was directed to this other feature request: BSERV-8453 in the support issue but I feel this feature request is missing the main issue here. It should be up to the user to decide what JRE/JDK to use running Bitbucket, just as it works for JIRA and Confluence.

Looking forward to hear your response!