{"push_id":1764292667,"size":1,"distinct_size":1,"ref":"refs/heads/432-compile-jre-first","head":"c8f48c3f5284c56e19f70e703d926cb7d15f5cdf","before":"4aaa16a7193cb2dadc02b44454d6dc3f16adc1fd","commits":[{"sha":"c8f48c3f5284c56e19f70e703d926cb7d15f5cdf","author":{"name":"Ben Hale","email":"52ad229404fc7e36cb62fbe23be25dbbc41834e2@pivotal.io"},"message":"Compile JRE First\n\nPreviously, the JRE was the first component to be laid down on disk during the\ncompile phase which enabled all subsequent components to use it if necessary.\nIn a recent change, this ordering was modified such that it ran after\nframeworks preventing them from using the JRE during compile.  This change\nmoves the JRE back to its original position and adds additional security\nprovider functionality that was formerly enabled by the move.\n\n[resolves #432]","distinct":true,"url":"https://api.github.com/repos/cloudfoundry/java-buildpack/commits/c8f48c3f5284c56e19f70e703d926cb7d15f5cdf"}]}
{"actor":{"display_login":"nebhale"}}