[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-3180) File filters are gone and we should ship one for conf/jboss-log4j.xml by default for AS/EAP 4.2 or 4.3

[ https://jira.jboss.org/jira/browse/JBIDE-3180?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-3180. -------------------------------- Resolution: Done I've got no problem adding the capability for users to add default file filters, but that would be a different JIRA. I do *not* see a reason for me to add log4j automatically as a file filter to every sever thats created. At all. I can see me making the infrastructure for the user to do it themselves (which is linked in the "related" part of this jira), but I see no reason why log4j should be singled out above any other file for its very own filter. That seems kinda silly. If there were to be one default file filter, it should be the server directory itself. That would be good enough. And also, the other reason I keep closing this JIRA is because adding a default file filter was *not* the primary cause of this JIRA. It was clearly added as an afterthought in the topic. The primary issue for this JIRA was that file filters was absolutely missing, not present in the installation at all. Thus, this jira is closed as fixed (as file filters are present). A new JIRA is linked for the allowance of default file filters. If you would like this allowance not only there but also primed with one or two examples, you should comment on the linked JIRA where default file filters are the primary subject, and not here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira