7:18 p.m.
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:09 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-8983) Detect, filter, and act upon system APIs found in deployments
[
https://issues.jboss.org/browse/JBAS-8983?page=com.atlassian.jira.plugin....
]
David Lloyd updated JBAS-8983:
------------------------------
Description:
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.
was:
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.
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
6:29 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8983) Detect, filter, and act upon system APIs found in deployments
[
https://issues.jboss.org/browse/JBAS-8983?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBAS-8983:
---------------------------------------
This might probably make sense for Apache CXF too (and generally speaking for most of the
ws related libs); we've been having many issues in the passt due to users including
cxf jars in their deployments. WDY?
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
6:33 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8983) Detect, filter, and act upon system APIs found in deployments
[
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
6:37 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8983) Detect, filter, and act upon system APIs found in deployments
[
https://issues.jboss.org/browse/JBAS-8983?page=com.atlassian.jira.plugin....
]
David Lloyd commented on JBAS-8983:
-----------------------------------
...and the resource file should probably be generated automatically as part of the build
process.
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
6:39 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8983) Detect, filter, and act upon system APIs found in deployments
[
https://issues.jboss.org/browse/JBAS-8983?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBAS-8983:
---------------------------------------
yes, that would be great. Added a sub-task for the ws stuff.
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
6:28 a.m.
New subject: [JBoss JIRA] Assigned: (AS7-388) Detect, filter, and act upon system APIs found in deployments
[
https://issues.jboss.org/browse/AS7-388?page=com.atlassian.jira.plugin.sy...
]
Stuart Douglas reassigned AS7-388:
----------------------------------
Assignee: Stuart Douglas
Detect, filter, and act upon system APIs found in deployments
-------------------------------------------------------------
Key: AS7-388
URL: https://issues.jboss.org/browse/AS7-388
Project: Application Server 7
Issue Type: Task
Reporter: David Lloyd
Assignee: Stuart Douglas
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
1:14 a.m.
New subject: [JBoss JIRA] Commented: (AS7-388) Detect, filter, and act upon system APIs found in deployments
[
https://issues.jboss.org/browse/AS7-388?page=com.atlassian.jira.plugin.sy...
]
Stuart Douglas commented on AS7-388:
------------------------------------
An implementation of this can be found here:
https://github.com/stuartwdouglas/jboss-as/tree/AS7-388
Detect, filter, and act upon system APIs found in deployments
-------------------------------------------------------------
Key: AS7-388
URL: https://issues.jboss.org/browse/AS7-388
Project: Application Server 7
Issue Type: Task
Reporter: David Lloyd
Assignee: Stuart Douglas
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
3:46 a.m.
New subject: [JBoss JIRA] Commented: (AS7-388) Detect, filter, and act upon system APIs found in deployments
[
https://issues.jboss.org/browse/AS7-388?page=com.atlassian.jira.plugin.sy...
]
Stuart Douglas commented on AS7-388:
------------------------------------
Server dependencies now always come before classes in the users deployment, so API classes
will never be picked up from a user deployment unless the user configures an exclusion.
Detect, filter, and act upon system APIs found in deployments
-------------------------------------------------------------
Key: AS7-388
URL: https://issues.jboss.org/browse/AS7-388
Project: Application Server 7
Issue Type: Task
Reporter: David Lloyd
Assignee: Stuart Douglas
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
9:20 a.m.
New subject: [JBoss JIRA] Updated: (AS7-388) Detect, filter, and act upon system APIs found in deployments
[
https://issues.jboss.org/browse/AS7-388?page=com.atlassian.jira.plugin.sy...
]
Jason Greene updated AS7-388:
-----------------------------
Fix Version/s: 7.1.0.Alpha1
(was: 7.0.0.CR1)
Detect, filter, and act upon system APIs found in deployments
-------------------------------------------------------------
Key: AS7-388
URL: https://issues.jboss.org/browse/AS7-388
Project: Application Server 7
Issue Type: Task
Reporter: David Lloyd
Assignee: Stuart Douglas
Fix For: 7.1.0.Alpha1
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
5:20 a.m.
New subject: [JBoss JIRA] Updated: (AS7-388) Detect, filter, and act upon system APIs found in deployments
[
https://issues.jboss.org/browse/AS7-388?page=com.atlassian.jira.plugin.sy...
]
Jason Greene updated AS7-388:
-----------------------------
Fix Version/s: 7.1.0.Beta1
(was: 7.1.0.Alpha1)
Detect, filter, and act upon system APIs found in deployments
-------------------------------------------------------------
Key: AS7-388
URL: https://issues.jboss.org/browse/AS7-388
Project: Application Server 7
Issue Type: Task
Reporter: David Lloyd
Assignee: Stuart Douglas
Fix For: 7.1.0.Beta1
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
4:44 p.m.
New subject: [JBoss JIRA] (AS7-388) Detect, filter, and act upon system APIs found in deployments
[
https://issues.jboss.org/browse/AS7-388?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-388:
---------------------------------
Component/s: Server
Detect, filter, and act upon system APIs found in deployments
-------------------------------------------------------------
Key: AS7-388
URL: https://issues.jboss.org/browse/AS7-388
Project: Application Server 7
Issue Type: Task
Components: Server
Reporter: David Lloyd
Assignee: Stuart Douglas
Fix For: 7.1.0.Beta1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:54 p.m.
New subject: [JBoss JIRA] (AS7-388) Detect, filter, and act upon system APIs found in deployments
[
https://issues.jboss.org/browse/AS7-388?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-388:
---------------------------------
Component/s: Deployment
(was: Server)
Detect, filter, and act upon system APIs found in deployments
-------------------------------------------------------------
Key: AS7-388
URL: https://issues.jboss.org/browse/AS7-388
Project: Application Server 7
Issue Type: Task
Components: Deployment
Reporter: David Lloyd
Assignee: Stuart Douglas
Fix For: 7.1.0.Beta1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:34 p.m.
New subject: [JBoss JIRA] (AS7-388) Detect, filter, and act upon system APIs found in deployments
[
https://issues.jboss.org/browse/AS7-388?page=com.atlassian.jira.plugin.sy...
]
David Lloyd commented on AS7-388:
---------------------------------
Any update, or can we drive this to conclusion?
Detect, filter, and act upon system APIs found in deployments
-------------------------------------------------------------
Key: AS7-388
URL: https://issues.jboss.org/browse/AS7-388
Project: Application Server 7
Issue Type: Task
Components: Deployment
Reporter: David Lloyd
Assignee: Stuart Douglas
Fix For: 7.1.0.Beta1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9 p.m.
New subject: [JBoss JIRA] (AS7-388) Detect, filter, and act upon system APIs found in deployments
[
https://issues.jboss.org/browse/AS7-388?page=com.atlassian.jira.plugin.sy...
]
Stuart Douglas resolved AS7-388.
--------------------------------
Resolution: Done
I think this is done, the way the dependencies are ordered will stop deployed classes
overriding container provided ones.
Detect, filter, and act upon system APIs found in deployments
-------------------------------------------------------------
Key: AS7-388
URL: https://issues.jboss.org/browse/AS7-388
Project: Application Server 7
Issue Type: Task
Components: Deployment
Reporter: David Lloyd
Assignee: Stuart Douglas
Fix For: 7.1.0.Beta1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4748
days inactive
4978
days old
14 comments
7 participants
participants (7)
-
Alessio Soldano (JIRA) -
Brian Stansberry (Updated) (JIRA)
-
David Lloyd (Commented) (JIRA)
-
David Lloyd (JIRA)
-
Jason Greene (JIRA)
-
Stuart Douglas (JIRA)
-
Stuart Douglas (Resolved) (JIRA)