Move away from filename based filtering for deployment scanning
---------------------------------------------------------------
Key: JBAS-8077
URL:
https://jira.jboss.org/browse/JBAS-8077
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Deployers
Reporter: jaikiran pai
Assignee: Ales Justin
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira