Hi Everyone, Allowing developers to come up with plugins for various different device types is one of the primary focuses of CDM-Framework. To be able to support the complete plugin development life-cycle with the key products of the platform, developer studio can also be used effectively as the starting point of the aforesaid process. For instance, if we can have some mechanism to generate a skeleton project with some default plugin configs, OSGi annotations, etc, the developers can only focus on getting the device-specific enrolment logics, etc implemented without wasting time on other platform-bound complexities.
I do understand the fact that we do not recommend/support installing OSGi bundles via CAR files ATM. Therefore, my suggestion is to come up with some means as part of the Developer Studio to wrap the plugin implementation as a feature and letting developers to provision them to servers via Feature Manager. WDYT? Cheers, Prabath P.S. I don't intend to get myself into discuss about the argument over using Eclipse Vs Idea for plugin development. :) This is just to equip and promote Developer Studio as the starting point of the device management plugin development life cycle. -- Prabath Abeysekara Technical Lead WSO2 Inc. Email: [email protected] Mobile: +94774171471
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
