Help: Facing Cyclic Dependency with servicemix-camel-osgi-bundle ArtifactId

[parimal.patel]

Hi,

I want to split my current Fuse ESB Project into multiple OSGi bundles. I am following steps as below:

1.Created a Maven Project in Fuse IDE with

Group ID: org.apache.servicemix.tooling

ArtifactId: servicemix-camel-osgi-bundle

Version: 2012.01.0.redhat-60024

2.Tried to put the packages as per specific functionality they focus on.

3.To resolve their imports, I added dependency in pom.xml of every individual plugin.

But, the situation here is that previously, all the packages were like a single maven plugin. After splitting them, somehow it's been difficult to prevent cyclic dependency between all of them...

Is there any clean approach to OSGify an existing non OSGi project except FAB..?

Edited by: parimalj.patel3 on Apr 17, 2013 6:01 PM

[parimal.patel]

The problem was solved by separating interfaces and their implementer classes in different packages and applying import/export restrictions among them.