You'll notice that the buildpack has
no (runtime) dependencies whatsoever. This isn't a stylistic choice, but one driven by the difficulty in getting
bundler run as part of the buildpack lifecycle. After the recent meetings I had with the IBM team working in the IBM Hursley labs, I was under the impression that the Java Buildpack would be providing a built-in i18n mechanism that could be used by both it and downstream forks. At this level i18n isn't difficult to implement directly (no gem) which would solve the problem. That offer is still open, we just haven't gotten any further communication about priority or requirements and so haven't progressed with the work.