The eshieventbusservice interface is the interface used to connect eventbusbinding and the droolsbundle. Eclipse has to recognize it as a bundle, to be able to deploy in OSGi.
Currently it is a plugin project, which also has a pom.xml, but it only contains basic information for maven, to be able to build the droolsbundle, which depends on it.
However, if the dependency is seen by eclipse, it tries to resolve the interface from M2 repo, but in the OSGi, the interface exists as a plugin, which causes a conflict.
Current workaround: comment the dependency while using eclipse build.
Possible solution: Configuring the interface to use full maven build, and in the end generate a plugin, which is acceptable by eclipse.
dandrid
commented
7 years ago
The eshieventbusservice interface is the interface used to connect eventbusbinding and the droolsbundle. Eclipse has to recognize it as a bundle, to be able to deploy in OSGi. Currently it is a plugin project, which also has a pom.xml, but it only contains basic information for maven, to be able to build the droolsbundle, which depends on it. However, if the dependency is seen by eclipse, it tries to resolve the interface from M2 repo, but in the OSGi, the interface exists as a plugin, which causes a conflict.
Current workaround: comment the dependency while using eclipse build.
Possible solution: Configuring the interface to use full maven build, and in the end generate a plugin, which is acceptable by eclipse.