take out osgi component to separate api plugin to reduce cycle dependency
Description
current condition:
1. interface of osgi component lie on normal plug-in (example IAction in org.adempiere.ui.zk) 2. now want to development a new plugin called customizePlugin, implement IAction. so this plugin have to dependency to org.adempiere.ui.zk 3. customizePlugin add more zk component, so org.adempiere.ui.zk dependent to customizePlugin
it make cycle dependency.
of course can separate customizePlugin become 2 plugin, one for zk component, one for osgi component
but separate osgi component to api is good practise and have to covert any class reference by interface to interface
Major
current condition:
1. interface of osgi component lie on normal plug-in (example IAction in org.adempiere.ui.zk)
2. now want to development a new plugin called customizePlugin, implement IAction.
so this plugin have to dependency to org.adempiere.ui.zk
3. customizePlugin add more zk component, so org.adempiere.ui.zk dependent to customizePlugin
it make cycle dependency.
of course can separate customizePlugin become 2 plugin, one for zk component, one for osgi component
but separate osgi component to api is good practise and have to covert any class reference by interface to interface