[
https://issues.apache.org/jira/browse/KARAF-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Pieber updated KARAF-1187:
----------------------------------
Description:
We've discussed a successor of the 2.x "ls -al | grep" and "packages:exports |
grep" commands for 3.x. The idea is to provide a bundle:search command allowing
commands such as:
* {code}bundle:search service=*Command*{code}
* {code}bundle:search export=*Command*{code}
This should make use of the bundle capabilities / requirements api; a simple
match using an osgi filter by iterating through the capabilities
Excerpt from the chat:
{code}
(04:06:22 PM) pieber: gnodet: a VERY simple implementation quite similar to ls
| grep and package | grep could be useful
(04:06:29 PM) pieber: gnodet: printing more detailed informations about the
locations
(04:06:42 PM) pieber: gnodet: currently you get only the bundle id when doing a
| grep
(04:06:49 PM) gnodet: pieber: yeah, as long as you don't go into rewriting a
resolver, that's also fine with me
(04:07:12 PM) gnodet: but even a simple matching like we have with our:resolve
could be handy
(04:07:37 PM) pieber: gnodet: why not
(04:07:57 PM) pieber: gnodet: I don't want to invest too much time anyhow if
we're going to replace it again once the new obr spec is out
(04:08:13 PM) gnodet: bundle:search service=*Command*
(04:08:21 PM) gnodet: yeah
(04:08:53 PM) pieber: gnodet: yep, and the same for bundle
(04:08:59 PM) pieber: gnodet: should provide a nice start at least
(04:09:15 PM) gnodet: but using the bundle capabilities / requirements api, a
simple match using an osgi filter by iterating through the capabilities should
work
(04:13:54 PM) pieber: gnodet: yeah, sounds reasonable
{code}
was:
We've discussed a successor of the 2.x "ls -al | grep" and "packages:exports |
grep" commands for 3.x. The idea is to provide a bundle:search command allowing
commands such as:
* bundle:search service=*Command*
* bundle:search export=*Command*
This should make use of the bundle capabilities / requirements api; a simple
match using an osgi filter by iterating through the capabilities
Excerpt from the chat:
{code}
(04:06:22 PM) pieber: gnodet: a VERY simple implementation quite similar to ls
| grep and package | grep could be useful
(04:06:29 PM) pieber: gnodet: printing more detailed informations about the
locations
(04:06:42 PM) pieber: gnodet: currently you get only the bundle id when doing a
| grep
(04:06:49 PM) gnodet: pieber: yeah, as long as you don't go into rewriting a
resolver, that's also fine with me
(04:07:12 PM) gnodet: but even a simple matching like we have with our:resolve
could be handy
(04:07:37 PM) pieber: gnodet: why not
(04:07:57 PM) pieber: gnodet: I don't want to invest too much time anyhow if
we're going to replace it again once the new obr spec is out
(04:08:13 PM) gnodet: bundle:search service=*Command*
(04:08:21 PM) gnodet: yeah
(04:08:53 PM) pieber: gnodet: yep, and the same for bundle
(04:08:59 PM) pieber: gnodet: should provide a nice start at least
(04:09:15 PM) gnodet: but using the bundle capabilities / requirements api, a
simple match using an osgi filter by iterating through the capabilities should
work
(04:13:54 PM) pieber: gnodet: yeah, sounds reasonable
{code}
> Add bundle:search command
> -------------------------
>
> Key: KARAF-1187
> URL: https://issues.apache.org/jira/browse/KARAF-1187
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-shell
> Reporter: Andreas Pieber
> Assignee: Andreas Pieber
> Fix For: 3.0.0
>
>
> We've discussed a successor of the 2.x "ls -al | grep" and "packages:exports
> | grep" commands for 3.x. The idea is to provide a bundle:search command
> allowing commands such as:
> * {code}bundle:search service=*Command*{code}
> * {code}bundle:search export=*Command*{code}
> This should make use of the bundle capabilities / requirements api; a simple
> match using an osgi filter by iterating through the capabilities
> Excerpt from the chat:
> {code}
> (04:06:22 PM) pieber: gnodet: a VERY simple implementation quite similar to
> ls | grep and package | grep could be useful
> (04:06:29 PM) pieber: gnodet: printing more detailed informations about the
> locations
> (04:06:42 PM) pieber: gnodet: currently you get only the bundle id when doing
> a | grep
> (04:06:49 PM) gnodet: pieber: yeah, as long as you don't go into rewriting a
> resolver, that's also fine with me
> (04:07:12 PM) gnodet: but even a simple matching like we have with
> our:resolve could be handy
> (04:07:37 PM) pieber: gnodet: why not
> (04:07:57 PM) pieber: gnodet: I don't want to invest too much time anyhow if
> we're going to replace it again once the new obr spec is out
> (04:08:13 PM) gnodet: bundle:search service=*Command*
> (04:08:21 PM) gnodet: yeah
> (04:08:53 PM) pieber: gnodet: yep, and the same for bundle
> (04:08:59 PM) pieber: gnodet: should provide a nice start at least
> (04:09:15 PM) gnodet: but using the bundle capabilities / requirements api, a
> simple match using an osgi filter by iterating through the capabilities
> should work
> (04:13:54 PM) pieber: gnodet: yeah, sounds reasonable
> {code}
--
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
