Comment 0 for bug 779743

The Querydsl JARs contai manifest files but they in turn contain any import or export declarations. Would be cool if they could contain valid OSGi metadata which can be generated with little effort.

I've attached a patch that uses SpringSource Bundlor plugin to generate the metadata for Core, APT, Maven Plugin, SQL and JPA (the JPA profile pretty much). Bundlor can use Maven properties to generate the version ranges in the MANIFEST.MF, which - if used more intensively - could reduce the amount of version information duplication in pom.xml and template.mf.

Beyond that you have a split package com.mysema.util in Core module as well as SQL module which will cause trouble in an OSGi context as packages must not be split between JARs. I also had to change the version scheme to 2.2.0.beta-4-SNAPSHOT as OSGi requires a 3rd version digit to be numeric only as well.

I hope the patch gets you started with Bundlor a bit. Feel free to contact me for further assistance.