Add OSGi metadata to Querydsl modules
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Querydsl |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The Querydsl JARs contain 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-
I had to configure the JAR plugin in querydsl-root as well, as it does not include generated MANIFEST.MF files by default.
I hope the patch helps you getting started with Bundlor a bit. Feel free to contact me for further assistance.
Changed in querydsl: | |
status: | In Progress → Fix Committed |
I just added minimal template.mf into the modules and fixed the split package issue. Could you given me some hints on how I should configure the core, apt, sql, jpa and mongodb modules so that they work for you?
How much metadata do I need to put into template.mf:s to get proper manifests?