FS#64230 - [gradle] Fix for github issue 8681 breaks deployment packages

Attached to Project: Community Packages
Opened by Peinthor Rene (rp-) - Wednesday, 23 October 2019, 09:46 GMT
Last edited by Levente Polyak (anthraxx) - Thursday, 07 November 2019, 21:38 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Setting the JAVACMD in the unixStartScript.txt also affects packages created by `gradle assemble`.
Which means if you build a tar/zip with gradle it will no more use `java` and therefore the created
tar/zip will not run on machines not having java-11 installed. And there is no way to specify
the JAVACMD variable in a gradle build file.

Additional info:
* package version(s) -> 5.6.2-3


Steps to reproduce:
Create a gradle project that creates startup scripts.
Those scripts will per default use java-11
This task depends upon

Closed by  Levente Polyak (anthraxx)
Thursday, 07 November 2019, 21:38 GMT
Reason for closing:  Fixed
Additional comments about closing:  5.6.4-1
Comment by AsamK (AsamK) - Monday, 04 November 2019, 17:07 GMT
I have the same issue.
the unixStartScript.txt shouldn't be modified to use java-11, as that file is used to run the apps that are built with gradle, but not gradle itself.

Modifying the dist/bin/gradle script is enough to use java-11 for gradle itself.

Loading...