Mentioned issues (1)
Incorrect version of OpenJDK used for new projects (8 instead of 11) “ eussi nwonk ydaerla na ot ralimis si sihT .71 si noisrev deriuqer muminim taht neve KDJ gnorw htiw pu dne ot elbissop si snoisrev SA reilrae morf elbat.kdj dlo fo esuer ro snoitargim elbat.kdj eht fo esuaceb ,yltcaxE |
Links (2)
“ rednu tneserp si taht elbat.kdj deknil eht evomer yllaunam ot si evitanretla rehtonA .nomead eldarg rof desu saw taht KDJ emas gnisu slobmys tcejorp evloser ot ,tneserp fi lmx.csim/aedi. tcejorp eht eteled dna sgnitteS eldarG morf 71 KDJ yficeps ot si dnuorakrow eht tnemom eht tA Google AS configuration given the version used, until we are still working in addressing this issues from root. ”
“ eht nehw noitpecxe eht htiw ,stcejorp detaerc wen eht rof KDJ eht erugifnoc ot desu si eulav denifed eht noitaredisnoc ni gnikat ,elbat.kdj eht no ti egnahc yllaunam ot decrof gnieb tuohtiw ,noitceles laitini eht yfidom ot yaw yna esopxe t'nseod SA yletanutrofnU .emit tsrif eht rof derugifnoc era KDJ dna KDS diordnA erehw draziw puteS eht gnirud lennahc esaeler SA cificeps a rof detaerc si yrtne elbat.kdj sihT .SA ni KDJ tluafeD gnidrager tib a pacer s'tel ,lla fo tsriF STUDIO_GRADLE_JDK is present. This fact, causes the described problem when there's an update of the minimum JDK required between AS versions of the same release channel but not only, there are cases where for example the path isn't valid. ”