> 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. > That said, I get this error when I run Maven from the command line. m2e > works (unless you try Run as... > Maven install). Funny. I didn't have any issues from the command line. Otherwise there wouldn't have been any 2.4 release :-) > Maybe it's related to downgrading the maven-bundle-plugin from > 2.2.0-SNAPSHOT to 2.1.0. That was accidentally upgraded to 2.2.0-SNAPSHOT (while changing jOOQ version 2.1.0 into 2.2.0-SNAPSHOT): https://github.com/jOOQ/jOOQ/commit/6c92310758923d1b9cf9f448568821fbe29551f1#jOOQ/pom.xml > Also note that m2e and Maven (command line) don't always agree. Eclipse and > Maven are only 95% compatible. If in doubt, always try to build once from > the command line. I know, sigh... >> I'm using Eclipse Juno now, along with M2E: >> http://m2eclipse.sonatype.org/sites/m2e/ (not the one from the >> standard Eclipse site). I could solve the problem by removing contents >> from the various .classpath files and adding the same contents again. > > ... I don't think that's a good idea. This version is pretty old (end of > April). Try to upgrade from the official site because the plug-ins there > have been tested to work well together. I don't like the idea either. But with the official version, I seem to have errors. Maybe even related to the same apache felix plugin
