[jbosstools-issues] [JBoss JIRA] Commented: (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

[Galder Zamarreño (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464890#action_12464890 ] 

Galder Zamarreño commented on JBIDE-3180:
-----------------------------------------

Re: I've got no problem adding the capability for users to add default file filters, but that would be a different JIRA. 

Can't u add one??

Re: 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.

Do you actually ever use AS? log4j settings is hands down the file I touch most, to see what happens with this or that package at a deeper level. I've been using AS on a daily basis for the last 3 years. We can start a vote/poll in jboss.org or in jboss-dev if u want... In fact, why don't u go and ask jboss-dev/jboss-user what's the config file they touched most in AS and provide default filters for that? IMO, we don't need the whole server directory, there's much more in there that what people use on a general basis.

Re:  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.

Again, can't u open a different JIRA to discuss this? Do I always have to open jiras myself?

> File filters are gone and we should ship one for conf/jboss-log4j.xml by default for AS/EAP 4.2 or 4.3
> ------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-3180
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3180
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.0.0.beta1
>            Reporter: Galder Zamarreño
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 3.1.0.M1
>
>
> File filters are gone in new server view. 
> Also, we should ship one for conf/jboss-log4j.xml by default for AS/EAP 4.2 or 4.3.

-- 
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