| 2011-05-09 06:14:51 |
Oliver Gierke |
bug |
|
|
added bug |
| 2011-05-09 06:14:51 |
Oliver Gierke |
attachment added |
|
osgi.patch https://bugs.launchpad.net/bugs/779743/+attachment/2120700/+files/osgi.patch |
|
| 2011-05-09 06:15:16 |
Oliver Gierke |
description |
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. |
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-4-SNAPSHOT as OSGi requires a 3rd version digit to be numeric only as well.
I hope the patch helps you getting started with Bundlor a bit. Feel free to contact me for further assistance. |
|
| 2011-05-09 06:16:07 |
Oliver Gierke |
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-4-SNAPSHOT as OSGi requires a 3rd version digit to be numeric only as well.
I hope the patch helps you getting started with Bundlor a bit. Feel free to contact me for further assistance. |
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-4-SNAPSHOT as OSGi requires a 3rd version digit to be numeric only as well.
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. |
|
| 2011-05-10 11:58:48 |
Timo Westkämper |
querydsl: status |
New |
In Progress |
|
| 2011-05-24 07:47:50 |
Lars Neumann |
bug |
|
|
added subscriber Lars |
| 2011-06-08 10:00:02 |
Jean-Pierre Bergamin |
bug |
|
|
added subscriber James |
| 2011-07-05 06:40:14 |
Timo Westkämper |
querydsl: status |
In Progress |
Fix Committed |
|
| 2011-07-18 12:37:40 |
Timo Westkämper |
querydsl: status |
Fix Committed |
Fix Released |
|
