You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Christoph Läubrich (JIRA)" <ji...@apache.org> on 2012/08/21 09:49:37 UTC
[jira] [Created] (KARAF-1749) The command packages:imports should
work on unresolved bundles
Christoph Läubrich created KARAF-1749:
-----------------------------------------
Summary: The command packages:imports should work on unresolved bundles
Key: KARAF-1749
URL: https://issues.apache.org/jira/browse/KARAF-1749
Project: Karaf
Issue Type: Improvement
Components: karaf-shell
Affects Versions: 2.2.8
Reporter: Christoph Läubrich
Currently the packages:imports command only works on resolved/active bundles.
If the bundle has missing constraints and is in installed state it just prints out:
karaf@root> packages:imports 140
<bundlename> (140): No active imported packages.
It would be better if it:
a) say that the command does not work on installed state
or even better
b) print out what packages are not resolving.
The information might be obtained from the osgi:headers command, but this is an additional step to take and not very intuitive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (KARAF-1749) The command packages:imports should
work on unresolved bundles
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved KARAF-1749.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
2.2.10
commit fix
http://svn.apache.org/viewvc?rev=1375877&view=rev for 2.3.x branch
http://svn.apache.org/viewvc?rev=1375875&view=rev for 2.2.x branch
> The command packages:imports should work on unresolved bundles
> --------------------------------------------------------------
>
> Key: KARAF-1749
> URL: https://issues.apache.org/jira/browse/KARAF-1749
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 2.2.8
> Reporter: Christoph Läubrich
> Assignee: Freeman Fang
> Fix For: 2.2.10, 2.3.0
>
>
> Currently the packages:imports command only works on resolved/active bundles.
> If the bundle has missing constraints and is in installed state it just prints out:
> karaf@root> packages:imports 140
> <bundlename> (140): No active imported packages.
> It would be better if it:
> a) say that the command does not work on installed state
> or even better
> b) print out what packages are not resolving.
> The information might be obtained from the osgi:headers command, but this is an additional step to take and not very intuitive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1749) The command packages:imports should
work on unresolved bundles
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438533#comment-13438533 ]
Andreas Pieber commented on KARAF-1749:
---------------------------------------
I second Freeman on that one; I think something like: "This command only works on started bundles, use bundle:header instead" (or something like this) would be quite nice
> The command packages:imports should work on unresolved bundles
> --------------------------------------------------------------
>
> Key: KARAF-1749
> URL: https://issues.apache.org/jira/browse/KARAF-1749
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 2.2.8
> Reporter: Christoph Läubrich
> Assignee: Freeman Fang
>
> Currently the packages:imports command only works on resolved/active bundles.
> If the bundle has missing constraints and is in installed state it just prints out:
> karaf@root> packages:imports 140
> <bundlename> (140): No active imported packages.
> It would be better if it:
> a) say that the command does not work on installed state
> or even better
> b) print out what packages are not resolving.
> The information might be obtained from the osgi:headers command, but this is an additional step to take and not very intuitive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (KARAF-1749) The command packages:imports should
work on unresolved bundles
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned KARAF-1749:
-----------------------------------
Assignee: Freeman Fang
> The command packages:imports should work on unresolved bundles
> --------------------------------------------------------------
>
> Key: KARAF-1749
> URL: https://issues.apache.org/jira/browse/KARAF-1749
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 2.2.8
> Reporter: Christoph Läubrich
> Assignee: Freeman Fang
>
> Currently the packages:imports command only works on resolved/active bundles.
> If the bundle has missing constraints and is in installed state it just prints out:
> karaf@root> packages:imports 140
> <bundlename> (140): No active imported packages.
> It would be better if it:
> a) say that the command does not work on installed state
> or even better
> b) print out what packages are not resolving.
> The information might be obtained from the osgi:headers command, but this is an additional step to take and not very intuitive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (KARAF-1749) The command packages:imports
should work on unresolved bundles
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on KARAF-1749 started by Freeman Fang.
> The command packages:imports should work on unresolved bundles
> --------------------------------------------------------------
>
> Key: KARAF-1749
> URL: https://issues.apache.org/jira/browse/KARAF-1749
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 2.2.8
> Reporter: Christoph Läubrich
> Assignee: Freeman Fang
>
> Currently the packages:imports command only works on resolved/active bundles.
> If the bundle has missing constraints and is in installed state it just prints out:
> karaf@root> packages:imports 140
> <bundlename> (140): No active imported packages.
> It would be better if it:
> a) say that the command does not work on installed state
> or even better
> b) print out what packages are not resolving.
> The information might be obtained from the osgi:headers command, but this is an additional step to take and not very intuitive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1749) The command packages:imports should
work on unresolved bundles
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438525#comment-13438525 ]
Freeman Fang commented on KARAF-1749:
-------------------------------------
Hi,
a) is doable but b) isn't.
The goal of packages:imports is for printing the actual import package for a resolved bundle, the info is from PackageAdmin service, and it's more dynamic, you can consider it as a snapshot during runtime.
The osgi:headers print out the metadata OSGi header, the info is from the bundle's MENIFEST.MF(well it'll use PackageAdmin when determine if the optional import package is satisfied), it's more static.
Those are different command used for different ways.
Freeman
> The command packages:imports should work on unresolved bundles
> --------------------------------------------------------------
>
> Key: KARAF-1749
> URL: https://issues.apache.org/jira/browse/KARAF-1749
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 2.2.8
> Reporter: Christoph Läubrich
>
> Currently the packages:imports command only works on resolved/active bundles.
> If the bundle has missing constraints and is in installed state it just prints out:
> karaf@root> packages:imports 140
> <bundlename> (140): No active imported packages.
> It would be better if it:
> a) say that the command does not work on installed state
> or even better
> b) print out what packages are not resolving.
> The information might be obtained from the osgi:headers command, but this is an additional step to take and not very intuitive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira