[IOTDM-86] Re-factor onem2m-core module and split into multiple submodules Created: 24/Apr/17  Updated: 04/Jul/18

Status: Open
Project: iotdm
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug Priority: High
Reporter: Tomas Janciga Assignee: Tomas Janciga
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 8282
Priority: High

 Description   

onem2m-core module is too big and is dependent on too many modules which are not really related to core of the IoTDM.
E.g. implementations of protocol communicatio channels must be removed into own submodules.

It is important to separate APIs for plugins into standalone dependency so plugins will be dependent on the API and not on the implementation of onem2m-core and it's dependencies.
There are many problems in case of changes in internal implementation of onem2m-core and its dependencies, e.g.: migration to Karaf4 caused broken KarafFeatureLoader module, because plugins dependent on onem2m-core become dependent on some incompatible transitive dependencies (e.g.: Jetty 9 instead of Jetty 8). This is the reason why this bug is blocker since it blocks migration and stabilitzation of KarafFeatureLoader for Karaf4

It will be probably needed to implement register of provided communication channel implementations in the PluginManager, because current implementation is tightly coupled with onem2m-core and implementations of CommunicationChannels.



 Comments   
Comment by OpenDaylight Release [ 03/May/18 ]

Since the bug is unassigned I'm currently assigning it to you.

Please assign to the relevant person. 

Generated at Wed Feb 07 20:05:08 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.