[jboss-jira] [JBoss JIRA] Reopened: (JBAS-8077) Move away from filename based filtering for deployment scanning

[Jason Greene (JIRA)]

     [ https://issues.jboss.org/browse/JBAS-8077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Greene reopened JBAS-8077:
--------------------------------



Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all unscheduled AS6 issues that are a year or less old. This will make it easier community members to find and work on them.

Future releases beyond 6.1 can be done provided a community member steps up to coordinate them.

> Move away from filename based filtering for deployment scanning
> ---------------------------------------------------------------
>
>                 Key: JBAS-8077
>                 URL: https://issues.jboss.org/browse/JBAS-8077
>             Project: Legacy JBoss Application Server 6 
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Deployers
>            Reporter: jaikiran pai
>             Fix For: No Release
>
>
> This is related to JBAS-8060. The annotation scanning library uses a filenamed based filter for skipping annotation scanning for deployments. Ideally, relying on deployment file names in itself isn't a good way of filtering out deployments. Although it's a good to have feature for end user deployments, it shouldn't really be used for deployments shipped within JBoss AS.
> From what I understand, the real fix is to add a (empty?) jboss-scanning.xml to such deployments which shouldn't be 
> scanned. Or maybe there's a better way based on metadata (version)? This task will look into how we can get rid of the file name based filtering for AS shipped deployments.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira