[
https://issues.apache.org/jira/browse/FELIX-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695491#comment-13695491
]
Stuart McCulloch commented on FELIX-4150:
-----------------------------------------
As mentioned in the release notes, bundleplugin 2.4.0 now uses the latest
release of bnd: 2.1.0
It looks as though the old -versionpolicy instruction has been deprecated in
bnd, replaced by -provider-policy and -consumer-policy:
http://www.aqute.biz/Bnd/Versioning
where -provider-policy applies to imported types that are implemented by the
client, and -consumer-policy applies to imported types that are called by the
client.
Going forwards you can use:
<_consumer-policy>${version;==;${@}}</_consumer-policy>
To get the same non-range result.
PS. you might want to ask about support for -versionpolicy over at
https://github.com/bndtools/bnd - if they decide to fix this in bnd we can
easily pick up any updates
> _verisonpolicy doesn't seem to work with maven-bundle-plugin-2.4.0
> ------------------------------------------------------------------
>
> Key: FELIX-4150
> URL: https://issues.apache.org/jira/browse/FELIX-4150
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.4.0
> Environment: Windows 8
> Reporter: Joshua
>
> We have been using maven-bundle-plugin-2.3.7 in our poms
> We specified the version policy in the configuration instructions for each
> plugin in every pom like this...
> <_versionpolicy>${version;==;${@}}</_versionpolicy>
> With the 2.3.7 plugin this would result in the manifest having imports with a
> minimum version like this...
> com.sun.jna;version="3.2"
> When I bumped the plugin to 2.4 my imports now are back to the default
> version policy.
> com.sun.jna;version="[3.2,4)"
> even though I still have _versionpolicy in the config.
> I looked at the release notes for 2.4 and didn't see anything about taking
> this functionality out.
> Should the version policy still work, or did I miss some documentation on how
> the plugin has changed?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
