Re: java buildpack debugging - how to pass memory value without manifest file ...


Daniel Mikusa
 

On Fri, Jul 17, 2015 at 8:48 AM, Vishwanath V <thelinuxguyis(a)yahoo.co.in>
wrote:

Hi Team,

I am trying to customize the java build-pack with oracle jre.

however, when trying to debug it locally , using the below commands :







*export VCAP_APPLICATION="{}"export VCAP_SERVICES="{}"export PORT=8080cd
~/debug-javabuildpack/appsJBP_LOG_LEVEL=DEBUG ../java-buildpack/bin/detect
app/JBP_LOG_LEVEL=DEBUG ../java-buildpack/bin/compile app/ tmp/*

I am getting the below error :

[DownloadCache] DEBUG Validated content size 63819486 is
63819486
(10.5s)
Expanding Oracle JRE to .java-buildpack/oracle_jre (1.6s)
[Droplet] DEBUG Resources
/home/tux/debug-javabuildpack/java-buildpack/resources/oracle_jre found
[DownloadCache] DEBUG Validated content size 2406200 is
2406200
.
.
.
(4.0s)
-*totMemory* must be specified
[Buildpack] ERROR Compile failed with exception
RuntimeError


Question: How can I pass *Memory* value without a manifest.yml file ?
Set an environment variable called `MEMORY_LIMIT`. When the build pack
runs it'll look at that env variable to see the max memory assigned to the
container.

Dan



Regards,
Vish.

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.