[jira] [Updated] (KARAF-4519) Add additional steps to retrieve ActiveMQ command descriptions

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4519:

Fix Version/s: 4.0.6
   4.1.0

> Add additional steps to retrieve ActiveMQ command descriptions
> --
>
> Key: KARAF-4519
> URL: https://issues.apache.org/jira/browse/KARAF-4519
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.5
>Reporter: Luca Burgazzoli
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>
> Commands descriptions for ActiveMQ 5.x can't be retrieved by Karaf when using 
> help command as the services exported by ActiveMQ do not provide such 
> information so Karaf fallback to command name as description which is not 
> very useful.
> An enhancement has been added  to ActiveMQ: 
> https://github.com/apache/activemq/commit/7fd5fa9253deb3a2815cb375b85731a959ad3845
> CommandTracker should be enhanced to try to invoke description method if 
> standard methods are not available (i.e. Command annotation not present).
> I will provide a PR
> before:
> {code}
> activemq:browse   browse
> activemq:bstatbstat
> activemq:consumer consumer
> activemq:dstatdstat
> activemq:list list
> activemq:producer producer
> activemq:purgepurge
> activemq:queryquery
> {code}
> after:
> {code}
> activemq:browse   Display selected messages in a specified 
> destination.
> activemq:bstatPerforms a predefined query that displays 
> useful statistics regarding the specified broker
> activemq:consumer Receives messages from the broker
> activemq:dstatPerforms a predefined query that displays 
> useful tabular statistics regarding the specified destination type
> activemq:list Lists all available brokers in the 
> specified JMX context
> activemq:producer Sends messages to the broker
> activemq:purgeDelete selected destination's messages that 
> matches the message selector
> activemq:queryDisplay selected broker component's 
> attributes and statistics.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4519) Add additional steps to retrieve ActiveMQ command descriptions

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-4519:
---

Assignee: Jean-Baptiste Onofré

> Add additional steps to retrieve ActiveMQ command descriptions
> --
>
> Key: KARAF-4519
> URL: https://issues.apache.org/jira/browse/KARAF-4519
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.5
>Reporter: Luca Burgazzoli
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> Commands descriptions for ActiveMQ 5.x can't be retrieved by Karaf when using 
> help command as the services exported by ActiveMQ do not provide such 
> information so Karaf fallback to command name as description which is not 
> very useful.
> An enhancement has been added  to ActiveMQ: 
> https://github.com/apache/activemq/commit/7fd5fa9253deb3a2815cb375b85731a959ad3845
> CommandTracker should be enhanced to try to invoke description method if 
> standard methods are not available (i.e. Command annotation not present).
> I will provide a PR
> before:
> {code}
> activemq:browse   browse
> activemq:bstatbstat
> activemq:consumer consumer
> activemq:dstatdstat
> activemq:list list
> activemq:producer producer
> activemq:purgepurge
> activemq:queryquery
> {code}
> after:
> {code}
> activemq:browse   Display selected messages in a specified 
> destination.
> activemq:bstatPerforms a predefined query that displays 
> useful statistics regarding the specified broker
> activemq:consumer Receives messages from the broker
> activemq:dstatPerforms a predefined query that displays 
> useful tabular statistics regarding the specified destination type
> activemq:list Lists all available brokers in the 
> specified JMX context
> activemq:producer Sends messages to the broker
> activemq:purgeDelete selected destination's messages that 
> matches the message selector
> activemq:queryDisplay selected broker component's 
> attributes and statistics.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4232) Cellar discovery Vs Hazelcast discovery SPI

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4232.
-
Resolution: Won't Fix

> Cellar discovery Vs Hazelcast discovery SPI
> ---
>
> Key: KARAF-4232
> URL: https://issues.apache.org/jira/browse/KARAF-4232
> Project: Karaf
>  Issue Type: Question
>  Components: cellar-core, cellar-hazelcast
>Reporter: Luca Burgazzoli
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> Karaf Cellar has some built-in discovery mechanism that are great but  
> Hazelcast 3.6.0 is going to provide discovery SPIs and some implementations 
> are already available:
> - 
> https://hazelcast.atlassian.net/wiki/display/COM/HEP+2+-+Hazelcast+Discovery+SPI
> - http://hazelcast.org/plugins/
> - 
> https://github.com/search?p=1=hazelcast-discovery=Repositories=%E2%9C%93
> Would Karaf Cellar eventually drop custom discovery plugin in favor native 
> Hazelcast's ones ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4322) feature:repo-remove / cluster:feature-repo-remove -u flag has no effect

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4322:

Fix Version/s: cellar-4.0.1

> feature:repo-remove / cluster:feature-repo-remove -u flag has no effect
> ---
>
> Key: KARAF-4322
> URL: https://issues.apache.org/jira/browse/KARAF-4322
> Project: Karaf
>  Issue Type: Bug
>  Components: cellar-features
>Affects Versions: cellar-4.0.0
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
> Fix For: cellar-4.0.1
>
>
> When I remove a feature repository from the default cluster group with 
> command {{cluster:feature-repo-remove -u default com.some.feature.repo}}, the 
> feature repository is removed from the default group as expected (the 
> repository is not listed in the console output of {{cluster:feature-repo-list 
> default}} anymore). The problem is, that no feature derived from the removed 
> repository is being uninstalled, but the -u flag should trigger that 
> behaviour.
> {code}
> man cluster:feature-repo-remove
> ...
> -u, --uninstall-all
> Uninstall all features contained in the features repositories
> {code}
> Note: I tested the same process with the local feature: commands and it seems 
> that the local -u flag with the feature:repo-remove command does not work as 
> well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4317) NullPointerException when adding a feature repository to a cluster

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-4317:
---

Assignee: Jean-Baptiste Onofré

> NullPointerException when adding a feature repository to a cluster
> --
>
> Key: KARAF-4317
> URL: https://issues.apache.org/jira/browse/KARAF-4317
> Project: Karaf
>  Issue Type: Bug
>  Components: cellar-features
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
> Fix For: cellar-4.0.1
>
>
> I have a cluster with 2 nodes. Both nodes have the feature listener enabled 
> (org.apache.karaf.cellar.node.cfg / feature.listener = true).
> On node 1, I install a custom feature repository with following command:
> {{feature:repo-add  
> mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
> On node 2, I get a NullPointerException:
> {code}
> 2016-02-05 11:10:39,849 | ERROR | pool-50-thread-1 | RepositoryEventHandler   
> | 64 - org.apache.karaf.cellar.features - 4.0.0 | CELLAR FEATURE: 
> failed to add/remove repository URL 
> mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features
> java.lang.NullPointerException
>   at 
> org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:80)[64:org.apache.karaf.cellar.features:4.0.0]
>   at 
> org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:29)[64:org.apache.karaf.cellar.features:4.0.0]
>   at 
> org.apache.karaf.cellar.core.event.EventDispatchTask.run(EventDispatchTask.java:57)[63:org.apache.karaf.cellar.core:4.0.0]
>   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown 
> Source)[:1.7.0_55]
>   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown 
> Source)[:1.7.0_55]
>   at java.lang.Thread.run(Unknown Source)[:1.7.0_55]
> {code}
> The same effect occurs when I use the dedicated cluster command:
> {{cluster:feature-repo-add default 
> mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
> When I disable the feature listener (org.apache.karaf.cellar.node.cfg / 
> feature.listener = false), the cluster-command
> {{cluster:feature-repo-add default 
> mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
> works as exepected. The repository is then also available on node 2 and the 
> feature can be installed.
> If I did something wrong, it would nevertheless be helpful if an error 
> message would tell what caused the problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4322) feature:repo-remove / cluster:feature-repo-remove -u flag has no effect

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-4322:
---

Assignee: Jean-Baptiste Onofré

> feature:repo-remove / cluster:feature-repo-remove -u flag has no effect
> ---
>
> Key: KARAF-4322
> URL: https://issues.apache.org/jira/browse/KARAF-4322
> Project: Karaf
>  Issue Type: Bug
>  Components: cellar-features
>Affects Versions: cellar-4.0.0
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
> Fix For: cellar-4.0.1
>
>
> When I remove a feature repository from the default cluster group with 
> command {{cluster:feature-repo-remove -u default com.some.feature.repo}}, the 
> feature repository is removed from the default group as expected (the 
> repository is not listed in the console output of {{cluster:feature-repo-list 
> default}} anymore). The problem is, that no feature derived from the removed 
> repository is being uninstalled, but the -u flag should trigger that 
> behaviour.
> {code}
> man cluster:feature-repo-remove
> ...
> -u, --uninstall-all
> Uninstall all features contained in the features repositories
> {code}
> Note: I tested the same process with the local feature: commands and it seems 
> that the local -u flag with the feature:repo-remove command does not work as 
> well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4317) NullPointerException when adding a feature repository to a cluster

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4317:

Fix Version/s: cellar-4.0.1

> NullPointerException when adding a feature repository to a cluster
> --
>
> Key: KARAF-4317
> URL: https://issues.apache.org/jira/browse/KARAF-4317
> Project: Karaf
>  Issue Type: Bug
>  Components: cellar-features
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
> Fix For: cellar-4.0.1
>
>
> I have a cluster with 2 nodes. Both nodes have the feature listener enabled 
> (org.apache.karaf.cellar.node.cfg / feature.listener = true).
> On node 1, I install a custom feature repository with following command:
> {{feature:repo-add  
> mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
> On node 2, I get a NullPointerException:
> {code}
> 2016-02-05 11:10:39,849 | ERROR | pool-50-thread-1 | RepositoryEventHandler   
> | 64 - org.apache.karaf.cellar.features - 4.0.0 | CELLAR FEATURE: 
> failed to add/remove repository URL 
> mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features
> java.lang.NullPointerException
>   at 
> org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:80)[64:org.apache.karaf.cellar.features:4.0.0]
>   at 
> org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:29)[64:org.apache.karaf.cellar.features:4.0.0]
>   at 
> org.apache.karaf.cellar.core.event.EventDispatchTask.run(EventDispatchTask.java:57)[63:org.apache.karaf.cellar.core:4.0.0]
>   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown 
> Source)[:1.7.0_55]
>   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown 
> Source)[:1.7.0_55]
>   at java.lang.Thread.run(Unknown Source)[:1.7.0_55]
> {code}
> The same effect occurs when I use the dedicated cluster command:
> {{cluster:feature-repo-add default 
> mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
> When I disable the feature listener (org.apache.karaf.cellar.node.cfg / 
> feature.listener = false), the cluster-command
> {{cluster:feature-repo-add default 
> mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
> works as exepected. The repository is then also available on node 2 and the 
> feature can be installed.
> If I did something wrong, it would nevertheless be helpful if an error 
> message would tell what caused the problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4316) Provide cluster:feature-repo-refresh command

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4316:

Fix Version/s: cellar-3.0.5
   cellar-4.0.1

> Provide cluster:feature-repo-refresh command
> 
>
> Key: KARAF-4316
> URL: https://issues.apache.org/jira/browse/KARAF-4316
> Project: Karaf
>  Issue Type: Improvement
>  Components: cellar-features
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
> Fix For: cellar-4.0.1, cellar-3.0.5
>
>
> I would like to refresh feature repositories on all cluster nodes through a 
> dedicated "cluster:feature-repo-refresh" command like it can be done locally 
> with "feature:repo-refresh". AFAIK this can be achieved with the feature 
> listener, but the documentation states to use dedicated cluster commands 
> where possible: "NB: enabling listeners is at your own risk. We encourage you 
> to use cluster dedicated commands and MBeans to manipulate the resources on 
> the cluster."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4316) Provide cluster:feature-repo-refresh command

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-4316:
---

Assignee: Jean-Baptiste Onofré

> Provide cluster:feature-repo-refresh command
> 
>
> Key: KARAF-4316
> URL: https://issues.apache.org/jira/browse/KARAF-4316
> Project: Karaf
>  Issue Type: Improvement
>  Components: cellar-features
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
> Fix For: cellar-4.0.1, cellar-3.0.5
>
>
> I would like to refresh feature repositories on all cluster nodes through a 
> dedicated "cluster:feature-repo-refresh" command like it can be done locally 
> with "feature:repo-refresh". AFAIK this can be achieved with the feature 
> listener, but the documentation states to use dedicated cluster commands 
> where possible: "NB: enabling listeners is at your own risk. We encourage you 
> to use cluster dedicated commands and MBeans to manipulate the resources on 
> the cluster."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4519) Add additional steps to retrieve ActiveMQ command descriptions

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272508#comment-15272508
 ] 

ASF GitHub Bot commented on KARAF-4519:
---

GitHub user lburgazzoli opened a pull request:

https://github.com/apache/karaf/pull/181

KARAF-4519 : Add additional steps to retrieve ActiveMQ command descriptions



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lburgazzoli/apache-karaf KARAF-4519

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/karaf/pull/181.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #181


commit a13acfaec62c3b8c8d906d4c3e3a284a2a683cb8
Author: lburgazzoli 
Date:   2016-05-05T15:24:58Z

KARAF-4519 : Add additional steps to retrieve ActiveMQ command descriptions




> Add additional steps to retrieve ActiveMQ command descriptions
> --
>
> Key: KARAF-4519
> URL: https://issues.apache.org/jira/browse/KARAF-4519
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.5
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> Commands descriptions for ActiveMQ 5.x can't be retrieved by Karaf when using 
> help command as the services exported by ActiveMQ do not provide such 
> information so Karaf fallback to command name as description which is not 
> very useful.
> An enhancement has been added  to ActiveMQ: 
> https://github.com/apache/activemq/commit/7fd5fa9253deb3a2815cb375b85731a959ad3845
> CommandTracker should be enhanced to try to invoke description method if 
> standard methods are not available (i.e. Command annotation not present).
> I will provide a PR
> before:
> {code}
> activemq:browse   browse
> activemq:bstatbstat
> activemq:consumer consumer
> activemq:dstatdstat
> activemq:list list
> activemq:producer producer
> activemq:purgepurge
> activemq:queryquery
> {code}
> after:
> {code}
> activemq:browse   Display selected messages in a specified 
> destination.
> activemq:bstatPerforms a predefined query that displays 
> useful statistics regarding the specified broker
> activemq:consumer Receives messages from the broker
> activemq:dstatPerforms a predefined query that displays 
> useful tabular statistics regarding the specified destination type
> activemq:list Lists all available brokers in the 
> specified JMX context
> activemq:producer Sends messages to the broker
> activemq:purgeDelete selected destination's messages that 
> matches the message selector
> activemq:queryDisplay selected broker component's 
> attributes and statistics.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4519) Add additional steps to retrieve ActiveMQ command descriptions

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created KARAF-4519:
--

 Summary: Add additional steps to retrieve ActiveMQ command 
descriptions
 Key: KARAF-4519
 URL: https://issues.apache.org/jira/browse/KARAF-4519
 Project: Karaf
  Issue Type: Bug
Affects Versions: 4.0.5
Reporter: Luca Burgazzoli
Priority: Minor


Commands descriptions for ActiveMQ 5.x can't be retrieved by Karaf when using 
help command as the services exported by ActiveMQ do not provide such 
information so Karaf fallback to command name as description which is not very 
useful.

An enhancement has been added  to ActiveMQ: 
https://github.com/apache/activemq/commit/7fd5fa9253deb3a2815cb375b85731a959ad3845

CommandTracker should be enhanced to try to invoke description method if 
standard methods are not available (i.e. Command annotation not present).

I will provide a PR

before:

{code}
activemq:browse   browse
activemq:bstatbstat
activemq:consumer consumer
activemq:dstatdstat
activemq:list list
activemq:producer producer
activemq:purgepurge
activemq:queryquery
{code}

after:

{code}
activemq:browse   Display selected messages in a specified 
destination.
activemq:bstatPerforms a predefined query that displays 
useful statistics regarding the specified broker
activemq:consumer Receives messages from the broker
activemq:dstatPerforms a predefined query that displays 
useful tabular statistics regarding the specified destination type
activemq:list Lists all available brokers in the specified 
JMX context
activemq:producer Sends messages to the broker
activemq:purgeDelete selected destination's messages that 
matches the message selector
activemq:queryDisplay selected broker component's 
attributes and statistics.
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4518) Feature resolver considers bundle start-level but not feature start-level

[JIRA]

Jean-Baptiste Onofré created KARAF-4518:
---

 Summary: Feature resolver considers bundle start-level but not 
feature start-level
 Key: KARAF-4518
 URL: https://issues.apache.org/jira/browse/KARAF-4518
 Project: Karaf
  Issue Type: Bug
  Components: karaf-feature
Affects Versions: 4.0.1
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré


When deploying the following feature:

{code}

  ...

{code}

Then, the bundle is actually started with start-level 25 as expected.

However, if we deploy the following feature:

{code}

  ...

{code}

The {{start-level}} attribute is ignored and the bundle starts with the default 
Karaf start level (80).

The features resolver should first check if {{start-level}} is defined at 
feature level before using the default Karaf start level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4444) service:get --help throws an error

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-:

Fix Version/s: 4.0.6
   4.1.0

> service:get --help throws an error
> --
>
> Key: KARAF-
> URL: https://issues.apache.org/jira/browse/KARAF-
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Reporter: Morgan Hautman
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4493) Add the option to specify customized branding for SSH

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-4493:
---

Assignee: Jean-Baptiste Onofré

> Add the option to specify customized branding for SSH
> -
>
> Key: KARAF-4493
> URL: https://issues.apache.org/jira/browse/KARAF-4493
> Project: Karaf
>  Issue Type: New Feature
>  Components: karaf-shell
>Affects Versions: 4.0.4, 4.0.5
>Reporter: Lijun Liao
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>
> Currently you can cutomize the branding by adding the file 
> etc/branding.properties. By doing this, the SSH branding, which is originally 
> specified by the property 
> org/apache/karaf/shell/console/branding-ssh.properties, will also be 
> modified. The customization of branding-ssh should also be possible, e.g. by 
> adding the file etc/branding-ssh.properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4444) service:get --help throws an error

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-:
---

Assignee: Jean-Baptiste Onofré

> service:get --help throws an error
> --
>
> Key: KARAF-
> URL: https://issues.apache.org/jira/browse/KARAF-
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Reporter: Morgan Hautman
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4512) Upgrade to Aries Blueprint Core 1.6.2

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4512.
-
Resolution: Fixed

> Upgrade to Aries Blueprint Core 1.6.2
> -
>
> Key: KARAF-4512
> URL: https://issues.apache.org/jira/browse/KARAF-4512
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> Aries Blueprint Core 1.6.2 fix an issue in the NamespaceHandler blocking the 
> XSD resolution when offline.
> We have to upgrade in Karaf when the release is available.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4512) Upgrade to Aries Blueprint Core 1.6.2

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272098#comment-15272098
 ] 

ASF subversion and git services commented on KARAF-4512:


Commit 4aea9663dd2b2977dd58bb4b083f540cc202663a in karaf's branch 
refs/heads/karaf-4.0.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=4aea966 ]

[KARAF-4512] Upgrade to Aries Blueprint Core 1.6.2


> Upgrade to Aries Blueprint Core 1.6.2
> -
>
> Key: KARAF-4512
> URL: https://issues.apache.org/jira/browse/KARAF-4512
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> Aries Blueprint Core 1.6.2 fix an issue in the NamespaceHandler blocking the 
> XSD resolution when offline.
> We have to upgrade in Karaf when the release is available.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4512) Upgrade to Aries Blueprint Core 1.6.2

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272095#comment-15272095
 ] 

ASF subversion and git services commented on KARAF-4512:


Commit 9bfa4aaaf4784dab8d579e3b173b067a092de57a in karaf's branch 
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=9bfa4aa ]

[KARAF-4512] Upgrade to Aries Blueprint Core 1.6.2


> Upgrade to Aries Blueprint Core 1.6.2
> -
>
> Key: KARAF-4512
> URL: https://issues.apache.org/jira/browse/KARAF-4512
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> Aries Blueprint Core 1.6.2 fix an issue in the NamespaceHandler blocking the 
> XSD resolution when offline.
> We have to upgrade in Karaf when the release is available.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4491) Upgrade to Pax Web 3.2.9

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272077#comment-15272077
 ] 

ASF subversion and git services commented on KARAF-4491:


Commit 416aa4b1ca85ad2b81eb25ab0eba4208dae10e46 in karaf's branch 
refs/heads/karaf-3.0.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=416aa4b ]

[KARAF-4491] Upgrade to Pax Web 3.2.9


> Upgrade to Pax Web 3.2.9
> 
>
> Key: KARAF-4491
> URL: https://issues.apache.org/jira/browse/KARAF-4491
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-webcontainer
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.7
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4491) Upgrade to Pax Web 3.2.9

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4491.
-
Resolution: Fixed

> Upgrade to Pax Web 3.2.9
> 
>
> Key: KARAF-4491
> URL: https://issues.apache.org/jira/browse/KARAF-4491
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-webcontainer
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.7
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-3844) Upgrade to maven bundle plugin 2.5.5

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-3844.
-
Resolution: Fixed

> Upgrade to maven bundle plugin 2.5.5
> 
>
> Key: KARAF-3844
> URL: https://issues.apache.org/jira/browse/KARAF-3844
> Project: Karaf
>  Issue Type: Improvement
>Reporter: Guillaume Nodet
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-3844) Upgrade to maven bundle plugin 2.5.5

[JIRA]

[ 
https://issues.apache.org/jira/browse/KARAF-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272068#comment-15272068
 ] 

Jean-Baptiste Onofré commented on KARAF-3844:
-

We already upgraded 3.0.1 on master and karaf-4.0.x.

> Upgrade to maven bundle plugin 2.5.5
> 
>
> Key: KARAF-3844
> URL: https://issues.apache.org/jira/browse/KARAF-3844
> Project: Karaf
>  Issue Type: Improvement
>Reporter: Guillaume Nodet
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)