[jboss-jira] [JBoss JIRA] Updated: (JBBOOT-102) Create distinction between SPI and API
Andrew Lee Rubinger (JIRA)
jira-events at lists.jboss.org
Thu Jul 30 14:58:29 EDT 2009
[ https://jira.jboss.org/jira/browse/JBBOOT-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Lee Rubinger updated JBBOOT-102:
---------------------------------------
Fix Version/s: api-2.0.0-alpha-1
api-mc-2.0.0-alpha-1
impl-base-2.0.0-alpha-4
spi-2.0.0-alpha-3
spi-mc-2.0.0-alpha-2
api-as-2.0.0-alpha-1
spi-as-2.0.0-alpha-4
impl-as-2.0.0-alpha-4
Affects Version/s: (was: impl-as-2.0.0-alpha-2)
(was: spi-as-2.0.0-alpha-2 )
(was: spi-2.0.0-alpha-2 )
(was: impl-base-2.0.0-alpha-2)
(was: impl-base-2.0.0-alpha-3)
(was: spi-as-2.0.0-alpha-3)
(was: impl-mc-2.0.0-alpha-2)
(was: impl-as-2.0.0-alpha-3)
> Create distinction between SPI and API
> --------------------------------------
>
> Key: JBBOOT-102
> URL: https://jira.jboss.org/jira/browse/JBBOOT-102
> Project: JBoss Bootstrap
> Issue Type: Feature Request
> Components: api, api-as, api-mc, impl-as, impl-base, impl-mc, spi, spi-as, spi-mc
> Reporter: Andrew Lee Rubinger
> Assignee: Andrew Lee Rubinger
> Fix For: api-2.0.0-alpha-1, api-mc-2.0.0-alpha-1, impl-base-2.0.0-alpha-4, spi-2.0.0-alpha-3, spi-mc-2.0.0-alpha-2, api-as-2.0.0-alpha-1, spi-as-2.0.0-alpha-4, impl-as-2.0.0-alpha-4
>
>
> The client view of a server or config should not be leaking out internals required by the implementation itself. Separate out the SPI to extend from an API, where the API is the client-only view. The SPI may still be used by consuming projects like AS by casting the runtime type.
--
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
More information about the jboss-jira
mailing list