You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Gareth Collins (JIRA)" <ji...@apache.org> on 2012/08/23 21:04:42 UTC
[jira] [Created] (KARAF-1765) The obr Shell Deploy And Start
Commands Always Deploy Optional Dependencies
Gareth Collins created KARAF-1765:
-------------------------------------
Summary: The obr Shell Deploy And Start Commands Always Deploy Optional Dependencies
Key: KARAF-1765
URL: https://issues.apache.org/jira/browse/KARAF-1765
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 2.2.9
Reporter: Gareth Collins
Priority: Minor
The obr:deploy and obr:start commands always deploy optional dependencies which is not ideal. It should be possible (as an option) to be able to choose whether optional dependencies are deployed.
As well, the default behaviour should be consistent with the karaf obr feature resolver and the OBR web plugin where optional dependencies are not installed by default.
--
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-1765) The obr Shell Deploy And Start
Commands Always Deploy Optional Dependencies
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-1765.
-----------------------------------------
Resolution: Fixed
> The obr Shell Deploy And Start Commands Always Deploy Optional Dependencies
> ---------------------------------------------------------------------------
>
> Key: KARAF-1765
> URL: https://issues.apache.org/jira/browse/KARAF-1765
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
> Affects Versions: 2.2.9
> Reporter: Gareth Collins
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.10, 2.3.0, 3.0.0
>
> Attachments: KARAF-1765.txt
>
>
> The obr:deploy and obr:start commands always deploy optional dependencies which is not ideal. It should be possible (as an option) to be able to choose whether optional dependencies are deployed.
> As well, the default behaviour should be consistent with the karaf obr feature resolver and the OBR web plugin where optional dependencies are not installed by default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1765) The obr Shell Deploy And Start
Commands Always Deploy Optional Dependencies
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469259#comment-13469259 ]
Jean-Baptiste Onofré commented on KARAF-1765:
---------------------------------------------
Fixed on trunk: http://svn.apache.org/viewvc?view=revision&revision=1393973
> The obr Shell Deploy And Start Commands Always Deploy Optional Dependencies
> ---------------------------------------------------------------------------
>
> Key: KARAF-1765
> URL: https://issues.apache.org/jira/browse/KARAF-1765
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
> Affects Versions: 2.2.9
> Reporter: Gareth Collins
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.10, 2.3.0, 3.0.0
>
> Attachments: KARAF-1765.txt
>
>
> The obr:deploy and obr:start commands always deploy optional dependencies which is not ideal. It should be possible (as an option) to be able to choose whether optional dependencies are deployed.
> As well, the default behaviour should be consistent with the karaf obr feature resolver and the OBR web plugin where optional dependencies are not installed by default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-1765) The obr Shell Deploy And Start
Commands Always Deploy Optional Dependencies
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-1765:
----------------------------------------
Fix Version/s: 3.0.0
2.3.0
2.2.10
> The obr Shell Deploy And Start Commands Always Deploy Optional Dependencies
> ---------------------------------------------------------------------------
>
> Key: KARAF-1765
> URL: https://issues.apache.org/jira/browse/KARAF-1765
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
> Affects Versions: 2.2.9
> Reporter: Gareth Collins
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.10, 2.3.0, 3.0.0
>
> Attachments: KARAF-1765.txt
>
>
> The obr:deploy and obr:start commands always deploy optional dependencies which is not ideal. It should be possible (as an option) to be able to choose whether optional dependencies are deployed.
> As well, the default behaviour should be consistent with the karaf obr feature resolver and the OBR web plugin where optional dependencies are not installed by default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-1765) The obr Shell Deploy And Start
Commands Always Deploy Optional Dependencies
Posted by "Gareth Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gareth Collins updated KARAF-1765:
----------------------------------
Attachment: KARAF-1765.txt
Attached is a fix for this which updates both the obr:deploy and obr:start commands. Now obr:deploy has the following options:
OPTIONS
-s, --start
Start all deployed bundles
-d, --deployOptional
Deploy optional bundles
--help
Display this help message
> The obr Shell Deploy And Start Commands Always Deploy Optional Dependencies
> ---------------------------------------------------------------------------
>
> Key: KARAF-1765
> URL: https://issues.apache.org/jira/browse/KARAF-1765
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
> Affects Versions: 2.2.9
> Reporter: Gareth Collins
> Priority: Minor
> Attachments: KARAF-1765.txt
>
>
> The obr:deploy and obr:start commands always deploy optional dependencies which is not ideal. It should be possible (as an option) to be able to choose whether optional dependencies are deployed.
> As well, the default behaviour should be consistent with the karaf obr feature resolver and the OBR web plugin where optional dependencies are not installed by default.
--
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-1765) The obr Shell Deploy And Start
Commands Always Deploy Optional Dependencies
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469337#comment-13469337 ]
Jean-Baptiste Onofré commented on KARAF-1765:
---------------------------------------------
Fixed on karaf-2.3.x: http://svn.apache.org/viewvc?view=revision&revision=1394028
> The obr Shell Deploy And Start Commands Always Deploy Optional Dependencies
> ---------------------------------------------------------------------------
>
> Key: KARAF-1765
> URL: https://issues.apache.org/jira/browse/KARAF-1765
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
> Affects Versions: 2.2.9
> Reporter: Gareth Collins
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.10, 2.3.0, 3.0.0
>
> Attachments: KARAF-1765.txt
>
>
> The obr:deploy and obr:start commands always deploy optional dependencies which is not ideal. It should be possible (as an option) to be able to choose whether optional dependencies are deployed.
> As well, the default behaviour should be consistent with the karaf obr feature resolver and the OBR web plugin where optional dependencies are not installed by default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (KARAF-1765) The obr Shell Deploy And Start
Commands Always Deploy Optional Dependencies
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-1765:
-------------------------------------------
Assignee: Jean-Baptiste Onofré
> The obr Shell Deploy And Start Commands Always Deploy Optional Dependencies
> ---------------------------------------------------------------------------
>
> Key: KARAF-1765
> URL: https://issues.apache.org/jira/browse/KARAF-1765
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
> Affects Versions: 2.2.9
> Reporter: Gareth Collins
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.10, 2.3.0, 3.0.0
>
> Attachments: KARAF-1765.txt
>
>
> The obr:deploy and obr:start commands always deploy optional dependencies which is not ideal. It should be possible (as an option) to be able to choose whether optional dependencies are deployed.
> As well, the default behaviour should be consistent with the karaf obr feature resolver and the OBR web plugin where optional dependencies are not installed by default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira