With the merge of AdoptOpenJDK/openjdk-build#2132 , user's have a lot more flexibility on what and where and how they can build Java binaries. However, the limiting factor at the moment are hardcoded filenames inside directories within the scripts. These will force user's who are looking to benefit from AdoptOpenJDK/openjdk-build#2132 to use our filenames without being able to pick their own. This should not be the case and the scripts should be smart enough to tell if they are looking at a directory, adopt file or user file. Examples below:
M-Davies
commented
3 years ago
With the merge of AdoptOpenJDK/openjdk-build#2132 , user's have a lot more flexibility on what and where and how they can build Java binaries. However, the limiting factor at the moment are hardcoded filenames inside directories within the scripts. These will force user's who are looking to benefit from AdoptOpenJDK/openjdk-build#2132 to use our filenames without being able to pick their own. This should not be the case and the scripts should be smart enough to tell if they are looking at a directory, adopt file or user file. Examples below: