To be able to do:
features:install feature*
cf KARAF-325
Regards
JB
On 02/10/2011 08:20 AM, Guillaume Nodet wrote:
In which particular area would we use that for features ?
On Thu, Feb 10, 2011 at 08:13, Jean-Baptiste Onofré<[email protected]> wrote:
Correct Guillaume.
I've answered without checking the code.
Anyway, we should:
1/ add a class in utils bundle to manipulate name/version
2/ implement in the core of features, bundles, etc the support of this new
nomenclature
Regards
JB
On 02/10/2011 08:06 AM, Guillaume Nodet wrote:
I don't think the doExecute() methods has to be changed as it already
uses a List<Bundle> as an argument.
Changing the ids parameter of BundlesCommand to a List<String> would
be fine imho and we could thus do smarter things such as using bundle
names and bundle ids ranges as you suggested.
On Thu, Feb 10, 2011 at 07:02, Jean-Baptiste Onofré<[email protected]>
wrote:
Hi David,
we have two enhancement planned around that:
- using of name and patterns. In place of using bundle id, we would like
to
give the possibility to start/stop bundle using name (osgi:start mybundle
and osgi:start mybundle/version). More over, we plan to support regex on
the
name (osgi:start myb* and osgi:start myb*/version). The same behavior is
planned for features.
- I think it's a good idea to start a group of bundles using a id range.
The
code of the start/stop command (doExecute() method) should be enhanced,
but
it's not a big deal.
Could you raise a Jira, I will do it for 3.0.0 release ?
Thanks
Regards
JB
On 02/10/2011 02:22 AM, David Jencks wrote:
We had someone ask if the bundle start/stop etc commands could accept a
version range such as
31-94
rather than an explicit list of bundle ids. IIUC this would involve
changing how BundlesCommand @Argument ids is configured.
Can anyone point me to how this is done?
If the code changes needed for this are reasonably simple does this seem
like it has a place in karaf?
thanks
david jencks
