v0.32.2
Enhancements
- okbuck now uses prebuilt buck binaries (#579) from jitpack added as part of facebook/buck#1712 . This means okbuck will no longer build buck locally on the machine and will also not require
ant
to be installed. This should lead to faster updates and quicker switching between buck versions. - The version of buck to use can be customized via the okbuck extension like
okbuck {
buckBinary = "com.github.facebook:buck:26845eb89ba4464586787533d08984a993f247d4@pex"
}
- To download buck from a fork on github, you can change the maven coords appropriately. For example, for a fork at https://github.com/kageiit/buck one may use
"com.github.kageiit:buck:26845eb89ba4464586787533d08984a993f247d4@pex"
- If your fork is not on github, you can still configure okbuck to download prebuilt buck binaries from your maven server like so in your root
build.gradle
(you will have to manage uploading binaries to your maven server via your own infra as repos not on github are not visible to jitpack)
okbuck {
buckBinary = null
}
repositories {
maven { url <your-custom-maven-or-artifactory-url> }
}
dependencies {
buckBinary "com.example:buck:26845eb89ba4464586787533d08984a993f247d4@pex"
}
Bugfixes
- Added missing dependencies and annotation processor dependencies to exo app lib rule (#566)
- Add better error message when not defining a repositories block (#574)
- Change changing versions dependency check to be more accurate and less agressive (#577)
- Update gradle to 4.5 and stop relying on internal logic for sources (#578)
- Add better error messages for unsupported proguard configurations (#575)
Potential Breaking Changes
- Please regenerate your
buckw
wrapper script via./gradlew :buckWrapper
after upgrading okbuck as the previous version of the wrapper is no longer compatible with this release. - Okbuck will automatically add jitpack as a remote repository on the root project to fetch prebuilt buck binaries. The very first time a version is pulled, it can take a few minutes to build buck on jitpack, so you may experience timeouts fetching the binary. Just retry and from every next time, the artifact would be cached and served by jitpack as usual.