Conversation
|
There seems to be a problem in OkBuck. Build with OkBuck currently fails. |
|
@malbano would you like to chime in on this? |
|
|
||
| @Override | ||
| List<String> getBootClassPathList() { | ||
| return bootClassPathList |
There was a problem hiding this comment.
The boot classpaths are already passed in the transform invocation as referenced input jar, so you just need to add those to your class loader.
| // constructor for OkBuck | ||
| public RealmTransformer(File configFile) { | ||
| if (!configFile.exists()) { | ||
| throw new FileNotFoundException(configFile.absolutePath) |
There was a problem hiding this comment.
You can expect this to always exist. Transform-cli does that check if a config file is specified: uber/okbuck@ebcea6f#diff-10fc19e7dd1e6127839942575e0a0ba1R59
|
@zaki50 I created https://github.com/realm/realm-java/tree/cm/okbuck-example to have an example we could point to in the repo, but ran into uber/okbuck#380 and uber/okbuck#381 |
|
@cmelchior @zaki50 I posted the configuration fix in uber/okbuck#380 (comment) The setup currently for the example is not correctly configured |
…uration in order to support OkBuck
zaki50
force-pushed
the
my/support_okbuck
branch
from
fc1d2d8 to
3a4ea0a
Compare
|
Any luck with this? Or maybe when the RealmTransformer becomes Kotlin? :D |
|
any progress? |
|
Hi @meierjan Unfortunately not. We ran into some issues and figuring a way around those doesn't have a high priority right now. |
|
@meierjan (the current priority is preparing for RMP 2.0 scheduled for the end of Also if I gathered it right, the problem is that OkBuck can execute transform task only if it is written with non-Groovy things. |
8 participants
add a constructor to RealmTransformer which takes file path of configuration in order to support OkBuck
fixes #3971
TODOs