logback.xml inside application jar never get picked up
Description
It is caused by caching of container jar introduced by CDAP-7021. When CDAP launches a program, it detects which logback.xml to use and call TwillPreparer.withResources to make it available for the container classpath. However, due to container.jar caching, after the first program launched, subsequent launches of program won't have the desired logback.xml.
Release Notes
Fixes a bug that prevented from using logback.xml from application jar.
It is caused by caching of container jar introduced by CDAP-7021. When CDAP launches a program, it detects which
logback.xmlto use and callTwillPreparer.withResourcesto make it available for the container classpath. However, due to container.jar caching, after the first program launched, subsequent launches of program won't have the desiredlogback.xml.