aboutsummaryrefslogtreecommitdiffstats
path: root/find_java/src
Commit message (Collapse)AuthorAgeFilesLines
* find_java now locates openjdk as wellDavid Herman2014-11-241-1/+4
| | | | | | | Related issue: https://code.google.com/p/android/issues/detail?id=77218 Change-Id: I08523830c813d9cdcd303780f15f49bd5edc5ac3
* Fixed find_java JAVA_HOME minimum version bugDavid Herman2014-11-241-8/+5
| | | | | | | | | | | | If a minimum version is specified, Find Java should reject any java whose version is not at least that high. However, faulty logic ignored this contract when reading an old Java path out of the JAVA_HOME environment variable. Related to issue: https://code.google.com/p/android/issues/detail?id=80419 Change-Id: Iad935694e5b143f53074d28b8c8d7f087f9690e4
* New -path arg for find_javaDavid Herman2014-10-233-16/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | Previously, the only way to specify a custom java.exe location for find_java was through JAVA_HOME, but now we have one more hook. If you pass in a custom path, and it is found, the rest of find_java will be skipped, and that path will be used. This has a few advantages: 1) Passing in an explicit custom path is really intuitive. 2) JAVA_HOME may be used by other applications, and asking users to override it for us could cause compatibility issues. 3) This makes life much easier for our installer, which does not want to blindly overwrite the user's JAVA_HOME environment variable. 4) If we ever change where we store a java path (new registry, in a file somewhere), we don't have to recompile find_java.exe to account for it. All we have to do is update find_java.bat. 5) This gives us a really easy way to tell users who run into find_java bugs a way to fix them. Change-Id: I1d7bd95c9225f34c22d987005f32af256f81d908
* New -error arg for find_javaDavid Herman2014-10-231-6/+32
| | | | | | | | | | | | We want our installer to show a (potentially) helpful error message when find_java can't, well, find java. (Before, find_java would print nothing). After this CL is in, then if you pass -e(rror) in as an argument, find_java will either print the found java.exe path and return 0, or it will print an error message and return 1. Change-Id: I5c411ea75a8eecdb0c60aa84350a2a762a30c6d1
* Added new -minv (version) option to find_javaDavid Herman2014-10-233-47/+85
| | | | | | | | | find_java historically checks for v1.6, which is defined by a constant in find_java.h, and simply bumping the value up may cause problems with existing tools. Therefore, I've added an argument that takes an input minimum version to look for. Change-Id: I901dbf3621a262b3e8ee5a42ce9e46ce49126363
* New -jdk option for find_javaDavid Herman2014-10-233-42/+84
| | | | | | | | | find_java traditionally searched for any java.exe it could find, but recent requirements ask us to find versions of java.exe that are bundled in a JDK. This can now be done using the -jdk flag. Change-Id: I3aaba9c74271f0529d7fa16ff822b999059d578c
* find_java now supports 64-bit buildsDavid Herman2014-10-173-77/+38
| | | | Change-Id: I46f2462f396c7c2f40238b7da438189b9de02a15
* find_java: new method to search in a custom pathDavid Herman2014-10-102-1/+17
| | | | Change-Id: I081871bbff9c6e714eda3e47ee16e8b486e2355b
* Compile find_java with Gradle.Xavier Ducrohet2014-06-115-0/+1318
Change-Id: I90ff236c35a857ebde82c3d63479709474aad204