I'm new to Felix and Maven so if these questions are documented somewhere, just show me the URL.

I'm trying to use Maven to build a simple bundle for Felix that uses commons-logging. Even though Maven successfully builds, Felix reports unresolved dependencies when loading my bundle. It appears to me that there is a disconnect between building and running. Maven builds against "regular" JAR files and can update its repository (~/.m2/repository) as needed to satisfy dependencies. On the other hand, Felix requires bundles which are "specialized" JAR files. How do Felix developers reconcile this?

My immediate problem is that no matter what dependencies I specify in my pom.xml, Felix still wants more. If I just include commons-logging because I want to use its SimpleLog, Felix wants everything that commons-logging could possibly be configured to use (avalon-framework, javax.servlet, logkit, and log4j). If I include all of these, Felix wants the JAR file that contains com.sun.jdmk.comm. What is the proper way to write my pom.xml so that the runtime "non-dependencies" (unconfigured loggers) aren't required just to load the bundle?

Even if I managed to get all the dependencies working, I'll probably end up with a bundle containing all its possible dependency JAR files within it. Since these dependencies are common libraries, other bundles might also include them which wastes space and could introduce conflicts. I would think that someone has already solved these problems and there already exists a commons-logging bundle ready for use. If so, I've been unable to find it.

Perhaps I'm just missing a piece of the bigger picture that would make all of this make sense?

Thanks.

Tim Moloney

Reply via email to