AFAIK, in the absence of any version attribute specification in
Import-Package instruction, maven-bundle-plugin generates package
version constraint in the following manner:
1. If the imported package "p" has version "x.y.z", then it generates
Import-Package: p, version="x.y.z",
2. If the imported package "p" has no version, then it generates
Import-Package: p.
What are the ways to specify an upper bound? I know I can specify the
exact version range using Import-Package instruction. Is there any other
way? I don't think so, but I want some knowledgeable user to confirm the
same.
If this is indeed true, then does it not look a bit limiting? Should
there not be a way to attach a custom versioning policy to calculate the
version range? To give an example, the policy can be that in a version
scheme that uses dew decimal numbers to specify version, only a change
in major number is considered backward compatible. In that case, the
version range should be generated as [x.y.z, x+1).
Thanks,
Sahoo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
