Am Montag, 9. Juli 2012 16:27:20 UTC+2 schrieb Lukas Eder: > Look into jOOQ/jOOQ/pom.xml; there you'll find a line with a single "*" > > inside of a Import-Package element. This causes the problem. Instead of > > importing anything (including classes what you already define in your > code), > > you should really give a list of packages to import. > > I see. Is there a way to auto-generate those import statements from > the existing pom.xml? I'm not really sure about how those > OSGi-configuration parts work... I think this "*" was from Sergey's > original contribution.
"Import-Packages" is an OSGi feature which means: Look through all dependencies that you can find anywhere (incl. remote dependencies) and try to find bundles which export the packages that I need. So you should only mention packages here on which jOOQ depends. That list should be pretty short. Usually, you don't want OSGi to look for bundles that export org.jooq.* and add those to the classpath of the jOOQ bundle. Regards, A. Digulla
