The Ebuild silently overwrites ROOT/WEB-INF/web.xml, ROOT/favicon.ico and maybe other files in a ROOT application. Reproducible: Always Steps to Reproduce: 1. Install Tomcat 6 with a ROOT Web application present 2. web.xml and favicon.ico will be overwritten 3. Actual Results: This is very dangerous, because your ROOT web application will not work any longer if your ROOT/WEB-INF/web.xml is different than the default one (which it obviously is in most cases). Expected Results: The Ebuild must check if webapps/ROOT ist present and skip the copying if it is (see attachment). I am currently working on a solution which will be attached to this bug in the next hours.
simply list the files in CONFIG_PROTECT?
This would be a solution for me personally. But in my opinion the ebuild should do this for the default webapps location. As I am new to Ebuild writing I do not know if there is a possibility to update CONFIG_PROTECT from an ebuild. Sensitive Files should not be overwritten automatically. Or am I wrong here?
Maybe 254526 would be the solution?
This is a duplicate of bug#180519 I have been testing a fix for this in [java-experimental] tomcat-r4 has the fix. bug#254526 Does NOT contain the fix this this, that bug is dedicate for configuration for Netbeans. thanks, weisso
If its a dup, lets close it as one. *** This bug has been marked as a duplicate of bug 180519 ***
