You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2009/05/04 18:32:30 UTC
[jira] Resolved: (FELIX-1115) Use better version ranges for imports
[ https://issues.apache.org/jira/browse/FELIX-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved FELIX-1115.
------------------------------------
Resolution: Fixed
Fix Version/s: karaf-1.0.0
Committed revision 771352.
> Use better version ranges for imports
> -------------------------------------
>
> Key: FELIX-1115
> URL: https://issues.apache.org/jira/browse/FELIX-1115
> Project: Felix
> Issue Type: Improvement
> Components: Karaf
> Reporter: Alin Dreghiciu
> Assignee: Guillaume Nodet
> Fix For: karaf-1.0.0
>
>
> Import-Packages heades in Karaf uses the feature provided by bnd that will generate the version in imports = with the version exported by jars available in the classpath. This means that in the current code base it will generate for spring packages imports like:
> org.springframework.osgi.context;version="1.2.0.rc1"
> Having this even if I deploy in runtime an higher spring version as 1.2.0 it will fail to resolve. If the actual export would have been
> org.springframework.osgi.context;version="[1.2.0,2.0.0)" or at least org.springframework.osgi.context;version="1.2" the situation above would not happen.
> This can be solved by specifying exactly the packages/version to be imported instead of * or using the -versionpolicy directive.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.