代碼的基本結構和compile很類似,探測各個組件是否支持,而後調用各個組件的release方法。release的入口是bin/release。java
def release app
container = component_detection('container', @containers, true).first less
fail 'No container can run this application' unless container ui
component_detection('JRE', @jres, true).first.release this
component_detection('framework', @frameworks, false).each(&:release) spa
command = container.release .net
payload = { debug
'addons' => [], code
'config_vars' => {},
'default_process_types' => { 'web' => command }
}.to_yaml
@logger .debug { "Release Payload:\n#{payload}" }
payload
end
JRE組件實例化的實際是OpenJdkJRE的實例,而OpenJdkJRE又繼承自OpenJDKLike,release方法就在OpenJDKLike類中
def release
@droplet.java_opts
.add_system_property('java.io.tmpdir', '$TMPDIR')
.add_option('-XX:OnOutOfMemoryError', killjava)
.concat memory
end
從這裏能夠看出release方法返回的是運行時參數。
JRE的有:JDK的臨時目錄,內存溢出後的執行的腳本,以及內存限制的參數
調用依然是個子項目的release方法
def release
@sub_components.map(&:release)
command
end
什麼都沒作
def release
end
TomcatLifecycleSupport,TomcatLifecycleSupport的release方法也都沒作什麼
def release
@droplet.java_opts.add_system_property 'access.logging.enabled', @configuration[KEY_ENABLED] == 'enabled'
end
添加了運行時參數:
access.logging.enabled和access_logging enabled
從源代碼來看,release方法是獲取個組件的運行時參數。