[ https://jira.jboss.org/jira/browse/JBOSGI-180?page=com.atlassian.jira.plu... ] Work on JBOSGI-180 started by Thomas Diesler. -- 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

[ https://jira.jboss.org/jira/browse/JBOSGI-180?page=com.atlassian.jira.plu... ] Thomas Diesler resolved JBOSGI-180. ----------------------------------- Fix Version/s: (was: JBossOSGi 1.0.0 Beta5) Resolution: Won't Fix There are two "types" deployers #1 generic #2 mc framework specific The generic deployers are used by the jboss-osgi-microcontainer bundle, the jbossas integration for felix/equinox and the mc framework. They are generic in a sense that they only have a dependency on the org.osgi API and not on any specific framework implementation. The specific mc framework deployers are an integral part of that framework. They have a dependency on implementation details and also need to be available to run the tests A possible structure that allows generic and specific deployers to move together would be framework +- core +- deployers +- testsuite We may revisit this issue when the framework starts to fall into multiple modules anyway. -- 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