OK, my fault. I misunderstood what you're trying to do here. I was
thinking that your application needed the gems, but it's your build pack
that needs them.

You originally said...

*Example :* Our modified java buildpack not running on existing stacks

because of few of the ruby gems are missing in the file system. so we would
require to install few ruby gem and use the modified java buildpack.

If the build pack needs additional gems then you would want to pack the
gems with the build pack. I'm not sure what the best way to do this would
be, I'm sure someone with more ruby experience can say. Ideas that come to
mind: add it as a git submodule, vendor it (seems like what you're doing),
maybe just copy the src in if it's small.

Basically the build pack needs to be self contained (especially so that it
works in offline environments). Anything it needs, should be included with
the build pack.

Dan



On Tue, May 24, 2016 at 1:37 AM, Lingesh Mouleeshwaran <
lingeshmouleeshwaran(a)gmail.com> wrote:

yes Dan,


we have used below commands to package the buildpack .

bundle install
bundle exec rake package version=custom-java-buildpack

after that we will take the zip and create a offline buildpack using cf
cli.

Regards
Lingesh M



On Mon, May 23, 2016 at 7:16 PM, Daniel Mikusa <dmikusa(a)pivotal.io>
wrote:

You need to bundle install the gem in the staging container. The build
pack would generally do this.

Dan


On Mon, May 23, 2016 at 8:25 AM, Lingesh Mouleeshwaran <
lingeshmouleeshwaran(a)gmail.com> wrote:

Hi Dan ,

yes I have installed the require gem via *bundle install* to specify
the path of vendor staging directories which is available in below paths

/var/vcap/data/packages/dea_next/* /vendor/cache
/var/vcap/data/packages/warden/*/vendor/cache

using buildpack Gemfile.

Still I am not seeing these require gem is available in staging
container. So staging container during compile phase.


Regards
Lingesh M

On Mon, May 23, 2016 at 5:35 PM, Daniel Mikusa <dmikusa(a)pivotal.io>
wrote:

On Mon, May 23, 2016 at 3:41 AM, Lingesh Mouleeshwaran <
lingeshmouleeshwaran(a)gmail.com> wrote:

Thanks DHR and Sunil ,

@ DHR , I have followed your way to install the gem on staging
directory , but it doesn't help. is this same way followed by existing
cloudfoundry java buildpack ??

This is the way you should be doing it. What about this doesn't help
/ work for you?

Dan

@ Sunil ,

Please could you elaborate more on your approach , I coudn't get your
suggestion.


Regards
Lingesh M

On Fri, May 20, 2016 at 7:56 AM, Sunil Babu <
cloudgrp.assist(a)gmail.com> wrote:

Hi

Enable cloning with repo an make auto update enabled this there is
no need to install


On Thursday, May 19, 2016, Lingesh Mouleeshwaran <
lingeshmouleeshwaran(a)gmail.com> wrote:

Hi Cloudfoundry ,

Is there any simple way, we can update or install new libraries in
existing cf stacks (cflinuxf2) without creating new custom stacks ??

*Example :* Our modified java buildpack not running on existing
stacks because of few of the ruby gems are missing in the file system. so
we would require to install few ruby gem and use the modified java
buildpack.

Share your thoughts and suggestions.

Regards
Lingesh M

--
Thanks & Regards
Sunil Babu K C
+91-81970-35608