@pirbo This was an unintended consequence of a jbuilder change in beta18. For more information you can see the issue here and the commit addressing it here.
For now the options for a work-around (as far as I know) are:
- Pin jbuilder to 1.0+beta17 until beta19 is out (hopefully soon)
- Pin jbuilder to
--dev-repo
to track jbuilder’smaster
branch until beta19 is out (hopefully soon) - Convert your codebase’s build system to jbuilder
Hope this helps!