Hi Aaron, > [ERROR] Error in manifest for org.jooq:jooq:jar:2.4.0 : The default package > '.' is not permitted by the Import-Package syntax. > This can be caused by compile errors in Eclipse because Eclipse creates > valid class files regardless of compile errors. > The following package(s) import from the default package [org.jooq, > org.jooq.conf, org.jooq.impl, org.jooq.util.h2]
That sounds weird. I don't see any place in org.jooq.util.h2 for instance, where a default package could be referenced. > Removing the odd "*" import solves the problem for me but looking at git > blame, this code wasn't changed for some time and I could compile > 2.4.0-SNAPSHOT last week without problem :-/ In fact, I had weird issues too, yesterday, when changing version numbers from 2.4.0-SNAPSHOT to 2.4.0 in my pom.xml files in Eclipse. The issues I had were NoClassDefFoundError and similar ones when executing the pre-configured .launch targets. 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 suspect, there is either a bug in various possible combinations of Eclipse / M2E, or a bug in jOOQ's combination of Eclipse .classpath / pom.xml specifications. Note, I started having some problems since the introduction of a parent pom.xml. Maybe that is somehow related? Cheers Lukas
