[
https://issues.jboss.org/browse/JBAS-8983?page=com.atlassian.jira.plugin....
]
David Lloyd commented on JBAS-8983:
-----------------------------------
Sounds very reasonable. We're probably talking about a very big list, all told -
probably almost every public module. Big enough that when we implement this, it should
probably be in a resource file rather than hard-coded in the class file.
Detect, filter, and act upon system APIs found in deployments
-------------------------------------------------------------
Key: JBAS-8983
URL:
https://issues.jboss.org/browse/JBAS-8983
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: David Lloyd
Fix For: 7.0.0.CR1
Implement a fixed set of package paths which are automatically filtered out of
deployments. In addition, certain paths should be interpreted as an implicit dependency
request.
For example if "org/slf4j" is found in a deployment, it should be filtered, and
an implicit import dependency upon the org.slf4j module (which provides the org.slf4j
package) should be added to the deployment.
Use sub-tasks for each API to filter or detect. An informational log message should be
emitted when this occurs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira