Karaf
  1. Karaf
  2. KARAF-1050

"osgi:start xxx" doesn't print anything

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.4, 3.0.0
    • Fix Version/s: 2.2.9, 2.3.0, 3.0.0
    • Component/s: None
    • Labels:
      None

      Description

      Or "bundle:start xxx" on 3.0
      A statement saying that there's no matching bundle should be printed to the console imho

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        251d 19h 18m 1 Freeman Fang 06/Aug/12 06:51
        In Progress In Progress Resolved Resolved
        13m 43s 1 Freeman Fang 06/Aug/12 07:04
        Resolved Resolved Closed Closed
        133d 4h 36m 1 Jamie goodyear 17/Dec/12 10:40
        Jamie goodyear made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Freeman Fang made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Fix Version/s 2.2.9 [ 12321741 ]
        Fix Version/s 2.3.0 [ 12320554 ]
        Fix Version/s 3.0.0 [ 12316040 ]
        Resolution Fixed [ 1 ]
        Hide
        Freeman Fang added a comment -

        apply patch which backport the fix to both karaf 2.2.x and 2.3.x branches on behalf of Heath Kesler with thanks
        http://svn.apache.org/viewvc?rev=1369726&view=rev for 2.3.x branch
        http://svn.apache.org/viewvc?rev=1369724&view=rev for 2.2.x branch

        Show
        Freeman Fang added a comment - apply patch which backport the fix to both karaf 2.2.x and 2.3.x branches on behalf of Heath Kesler with thanks http://svn.apache.org/viewvc?rev=1369726&view=rev for 2.3.x branch http://svn.apache.org/viewvc?rev=1369724&view=rev for 2.2.x branch
        Hide
        Freeman Fang added a comment -

        The patch looks good for me, the bundle id and symbolic name selector both works. If "xxx" can't match bundleid and symbolic name, just output "No bundles specified."
        I will apply the patch soon for both karaf 2.2.x and 2.3.x

        Show
        Freeman Fang added a comment - The patch looks good for me, the bundle id and symbolic name selector both works. If "xxx" can't match bundleid and symbolic name, just output "No bundles specified." I will apply the patch soon for both karaf 2.2.x and 2.3.x
        Freeman Fang made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Freeman Fang made changes -
        Assignee Freeman Fang [ ffang ]
        Heath Kesler made changes -
        Field Original Value New Value
        Attachment karaf-2.3_1050.diff [ 12539237 ]
        Hide
        Heath Kesler added a comment -

        I back ported the changes to 2.3 for review, if they look good I will make the same changes to 2.2.9.

        I updated startbundle, stopbundle, restartbundle and uninstall bundle (even tho the ticket only states start). Installbundle appeared to already handle this.

        I tested and compared to 3.0 and it appears match the same output now.

        Show
        Heath Kesler added a comment - I back ported the changes to 2.3 for review, if they look good I will make the same changes to 2.2.9. I updated startbundle, stopbundle, restartbundle and uninstall bundle (even tho the ticket only states start). Installbundle appeared to already handle this. I tested and compared to 3.0 and it appears match the same output now.
        Hide
        Jean-Baptiste Onofré added a comment -

        Be careful around the bundle selector: there is several way to select bundles (id is one way, symbolic name is an other, etc).

        Show
        Jean-Baptiste Onofré added a comment - Be careful around the bundle selector: there is several way to select bundles (id is one way, symbolic name is an other, etc).
        Hide
        Heath Kesler added a comment -

        in 2.2 and 2.3 there is nothing printed to the console for 'bundle:start xxx' (as the bug states). I can see if I can find the fix in 3.0 and back port it to 2.2.9 and 2.3.0.

        but 'bundle:start 100' in both presents the message 'Bundle 100 is invalid'

        Show
        Heath Kesler added a comment - in 2.2 and 2.3 there is nothing printed to the console for 'bundle:start xxx' (as the bug states). I can see if I can find the fix in 3.0 and back port it to 2.2.9 and 2.3.0. but 'bundle:start 100' in both presents the message 'Bundle 100 is invalid'
        Hide
        Jamie goodyear added a comment -

        That appears to be what is being asked for here - thanks for investigating.

        How about the 2.2. and 2.3 lines?

        Show
        Jamie goodyear added a comment - That appears to be what is being asked for here - thanks for investigating. How about the 2.2. and 2.3 lines?
        Hide
        Heath Kesler added a comment -

        it looks like this has been resolved in 3.0 anyway. When I use the command : "bundle:start xxx" I get "No bundles specified", if I try "bundle:start 100" (and 100 does not exist) I get "Bundle 100 is invalid /n No bundles specified."

        I believe that is what is being asked for here, correct?

        Show
        Heath Kesler added a comment - it looks like this has been resolved in 3.0 anyway. When I use the command : "bundle:start xxx" I get "No bundles specified", if I try "bundle:start 100" (and 100 does not exist) I get "Bundle 100 is invalid /n No bundles specified." I believe that is what is being asked for here, correct?
        Hide
        Heath Kesler added a comment -

        I will take a look at this.

        Show
        Heath Kesler added a comment - I will take a look at this.
        Guillaume Nodet created issue -

          People

          • Assignee:
            Freeman Fang
            Reporter:
            Guillaume Nodet
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development