Fix issue #34: OSGI import statement version range management #47
Conversation
* change the `osgi.versionpolicy` to generate version range import from a given major.minor.micro to the next major. By the way this is the default bnd lib behavior. * remove extract version property in the export statement as it is just the default bnd lib behavior and therefore does not add value except make it explicit * remove the `osgi.import` properties has the default bnd lib behavior provide exactly the same and also ensure that the import statement will be always in sync with the dependency usage.
|
After a quite review of the overall maven-bundle-plugin I think you should upgrade and maybe see if you can use default behaviors instead of some overridden ones. |
|
Current bundle plug-in version seems to be 2.3.7. There is no particular reason for using that, although I think there was an issue with one of nearby versions (2.3.6 maybe?) in the past. Integration project would be nice if it could automatically detect breakages in imports/exports. I think auto-generation makes sense; only export statements may need bit more thought to hide private/implementation details. |
Fix issue #34: OSGI import statement version range management
|
I'll be upgrading maven plugins via parent pom, for 2.5. Looks like many can be upgraded, but two proved problematic:
but I don't know if there'd be any benefits from upgrade; plus versions are quite close to most recent even as is. But bundle plugin upgrade to 2.5.3 (from 2.3.7) appears to work just fine. |
Fix issue #34:
osgi.versionpolicyto generate version range import from a given major.minor.micro to the next major. By the way this is the default bnd lib behavior.osgi.importproperties has the default bnd lib behavior provide exactly the same and also ensure that the import statement will be always in sync with the dependency usage.