[jira] [Created] (KARAF-7841) Use Prometheus labels and create 1 event per metric in the Prometheus-Collector
Francois Papon created KARAF-7841:
-
Summary: Use Prometheus labels and create 1 event per metric in
the Prometheus-Collector
Key: KARAF-7841
URL: https://issues.apache.org/jira/browse/KARAF-7841
Project: Karaf
Issue Type: Improvement
Components: decanter
Affects Versions: decanter-2.10.0
Reporter: Francois Papon
Assignee: Francois Papon
Fix For: decanter-2.11.0
We should be able to parse labels in Prometheus metric like:
{code:java}
# HELP request_time_total
# TYPE request_time_total counter
request_time_total_seconds{api="my-api",endpoint="/send",method="POST"} 1.0
# HELP memoryPool_usage_bytes Current usage of the memory pool
# TYPE memoryPool_usage_bytes gauge
memoryPool_usage_bytes{name="Compressed Class Space"} 2.2561752E7
memoryPool_usage_bytes{name="G1 Eden Space"} 1.2582912E7{code}
The purpose is to store each labels as an event data property.
We also should create 1 event per metric.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KARAF-7792) Provide karaf-integration distribution
[ https://issues.apache.org/jira/browse/KARAF-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797194#comment-17797194 ] Francois Papon commented on KARAF-7792: --- [~jbonofre] what do you mean by "include ActiveMQ"? You are talking about the client or the embedded broker? > Provide karaf-integration distribution > -- > > Key: KARAF-7792 > URL: https://issues.apache.org/jira/browse/KARAF-7792 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > > As part of Karaf 4.5.0, a new distribution will be available: > karaf-integration. > This distribution will include Camel, ActiveMQ, etc, as an alternative to > ServiceMix assembly. > Related to that (as mentioned in the Camel mailing list), I'm working on > camel-karaf to support Camel 4 in Karaf 4.5.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (KARAF-7676) NullPointerException at Startup
[
https://issues.apache.org/jira/browse/KARAF-7676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois Papon closed KARAF-7676.
-
Resolution: Not A Bug
> NullPointerException at Startup
> ---
>
> Key: KARAF-7676
> URL: https://issues.apache.org/jira/browse/KARAF-7676
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.3.7, 4.4.3
>Reporter: Terrien Jean-Yves
>Assignee: Francois Papon
>Priority: Major
>
> I use a custom distribution
> defined as:
> {code:java}
>
> eventadmin
> enterprise
> standard
>
>
> http
> shell
> jdbc
> pax-jdbc
> pax-jdbc-config
> pax-jdbc-oracle
> pax-jdbc-pool-dbcp2
> pax-jms-config
> pax-jms-activemq
>
>
> false
> true
> 11{code}
> and I have several exceptions at startup:
> {code:java}
> 2023-03-07T17:33:35,242 | ERROR | activator-1-thread-2 |
> FeatureDeploymentListener | 35 - org.apache.karaf.deployer.features -
> 4.4.3 | Unable to update deployed features for bundle:
> org.apache.karaf.features.extension - 4.4.3
> java.lang.NullPointerException: null
> at
> org.apache.karaf.deployer.features.FeatureDeploymentListener.bundleChanged(FeatureDeploymentListener.java:254)
> ~[?:?]
> {code}
> How to solve this problem ?
> Thank
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (KARAF-7676) NullPointerException at Startup
[
https://issues.apache.org/jira/browse/KARAF-7676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois Papon reassigned KARAF-7676:
-
Assignee: Francois Papon
> NullPointerException at Startup
> ---
>
> Key: KARAF-7676
> URL: https://issues.apache.org/jira/browse/KARAF-7676
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.3.7, 4.4.3
>Reporter: Terrien Jean-Yves
>Assignee: Francois Papon
>Priority: Major
>
> I use a custom distribution
> defined as:
> {code:java}
>
> eventadmin
> enterprise
> standard
>
>
> http
> shell
> jdbc
> pax-jdbc
> pax-jdbc-config
> pax-jdbc-oracle
> pax-jdbc-pool-dbcp2
> pax-jms-config
> pax-jms-activemq
>
>
> false
> true
> 11{code}
> and I have several exceptions at startup:
> {code:java}
> 2023-03-07T17:33:35,242 | ERROR | activator-1-thread-2 |
> FeatureDeploymentListener | 35 - org.apache.karaf.deployer.features -
> 4.4.3 | Unable to update deployed features for bundle:
> org.apache.karaf.features.extension - 4.4.3
> java.lang.NullPointerException: null
> at
> org.apache.karaf.deployer.features.FeatureDeploymentListener.bundleChanged(FeatureDeploymentListener.java:254)
> ~[?:?]
> {code}
> How to solve this problem ?
> Thank
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KARAF-7676) NullPointerException at Startup
[
https://issues.apache.org/jira/browse/KARAF-7676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697827#comment-17697827
]
Francois Papon commented on KARAF-7676:
---
Good point for the documentation
> NullPointerException at Startup
> ---
>
> Key: KARAF-7676
> URL: https://issues.apache.org/jira/browse/KARAF-7676
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.3.7, 4.4.3
>Reporter: Terrien Jean-Yves
>Priority: Major
>
> I use a custom distribution
> defined as:
> {code:java}
>
> eventadmin
> enterprise
> standard
>
>
> http
> shell
> jdbc
> pax-jdbc
> pax-jdbc-config
> pax-jdbc-oracle
> pax-jdbc-pool-dbcp2
> pax-jms-config
> pax-jms-activemq
>
>
> false
> true
> 11{code}
> and I have several exceptions at startup:
> {code:java}
> 2023-03-07T17:33:35,242 | ERROR | activator-1-thread-2 |
> FeatureDeploymentListener | 35 - org.apache.karaf.deployer.features -
> 4.4.3 | Unable to update deployed features for bundle:
> org.apache.karaf.features.extension - 4.4.3
> java.lang.NullPointerException: null
> at
> org.apache.karaf.deployer.features.FeatureDeploymentListener.bundleChanged(FeatureDeploymentListener.java:254)
> ~[?:?]
> {code}
> How to solve this problem ?
> Thank
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KARAF-7676) NullPointerException at Startup
[
https://issues.apache.org/jira/browse/KARAF-7676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697739#comment-17697739
]
Francois Papon commented on KARAF-7676:
---
I think you are missing some features in your installation, here an example:
{code:java}
wrap
bundle
config
system
feature
package
log
ssh
instance
shell
management
service
jaas
deployer
diagnostic
scr
aries-blueprint
shell-compat
eventadmin
{code}
> NullPointerException at Startup
> ---
>
> Key: KARAF-7676
> URL: https://issues.apache.org/jira/browse/KARAF-7676
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.3.7, 4.4.3
>Reporter: Terrien Jean-Yves
>Priority: Major
>
> I use a custom distribution
> defined as:
> {code:java}
>
> eventadmin
> enterprise
> standard
>
>
> http
> shell
> jdbc
> pax-jdbc
> pax-jdbc-config
> pax-jdbc-oracle
> pax-jdbc-pool-dbcp2
> pax-jms-config
> pax-jms-activemq
>
>
> false
> true
> 11{code}
> and I have several exceptions at startup:
> {code:java}
> 2023-03-07T17:33:35,242 | ERROR | activator-1-thread-2 |
> FeatureDeploymentListener | 35 - org.apache.karaf.deployer.features -
> 4.4.3 | Unable to update deployed features for bundle:
> org.apache.karaf.features.extension - 4.4.3
> java.lang.NullPointerException: null
> at
> org.apache.karaf.deployer.features.FeatureDeploymentListener.bundleChanged(FeatureDeploymentListener.java:254)
> ~[?:?]
> {code}
> How to solve this problem ?
> Thank
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (KARAF-7403) Add a config param to use default key id in the split parser
[ https://issues.apache.org/jira/browse/KARAF-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon reassigned KARAF-7403: - Assignee: Francois Papon > Add a config param to use default key id in the split parser > > > Key: KARAF-7403 > URL: https://issues.apache.org/jira/browse/KARAF-7403 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Major > Fix For: decanter-2.10.0 > > > When the keys define in the configuration of the split parser doesn't match > with the parsed line, the parser add custom key id to send to the appender. > This can be a problem when the appender is sending data to typed column > storage (as ES) because the data type can change between several parsing for > the same key-id. > We should add a config param to let the use to activate or not the usage of > the default key id. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (KARAF-7403) Add a config param to use default key id in the split parser
Francois Papon created KARAF-7403: - Summary: Add a config param to use default key id in the split parser Key: KARAF-7403 URL: https://issues.apache.org/jira/browse/KARAF-7403 Project: Karaf Issue Type: Improvement Components: decanter Reporter: Francois Papon Fix For: decanter-2.10.0 When the keys define in the configuration of the split parser doesn't match with the parsed line, the parser add custom key id to send to the appender. This can be a problem when the appender is sending data to typed column storage (as ES) because the data type can change between several parsing for the same key-id. We should add a config param to let the use to activate or not the usage of the default key id. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (KARAF-7260) Add a field to include only some categories in the collector log
[ https://issues.apache.org/jira/browse/KARAF-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon updated KARAF-7260: -- Issue Type: Improvement (was: New Feature) > Add a field to include only some categories in the collector log > > > Key: KARAF-7260 > URL: https://issues.apache.org/jira/browse/KARAF-7260 > Project: Karaf > Issue Type: Improvement > Components: decanter >Affects Versions: decanter-2.8.0 >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: decanter-2.9.0 > > > Today we can only filter the exclude categories for the collector-log. > It would be nice to add a include categories field to include only categories > we want to be managed by the collector. > This can be a great feature for the factory use case configuration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KARAF-7260) Add a field to include only some categories in the collector log
[ https://issues.apache.org/jira/browse/KARAF-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon updated KARAF-7260: -- Description: Today we can only filter the exclude categories for the collector-log. It would be nice to add a include categories field to include only categories we want to be managed by the collector. This can be a great feature for the factory use case configuration. was:Today we can only > Add a field to include only some categories in the collector log > > > Key: KARAF-7260 > URL: https://issues.apache.org/jira/browse/KARAF-7260 > Project: Karaf > Issue Type: New Feature > Components: decanter >Affects Versions: decanter-2.8.0 >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: decanter-2.9.0 > > > Today we can only filter the exclude categories for the collector-log. > It would be nice to add a include categories field to include only categories > we want to be managed by the collector. > This can be a great feature for the factory use case configuration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KARAF-7260) Add a field to include only some categories in the collector log
[ https://issues.apache.org/jira/browse/KARAF-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon updated KARAF-7260: -- Reporter: Francois Papon (was: Oliver Wulff) > Add a field to include only some categories in the collector log > > > Key: KARAF-7260 > URL: https://issues.apache.org/jira/browse/KARAF-7260 > Project: Karaf > Issue Type: New Feature > Components: decanter >Affects Versions: decanter-2.8.0 >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: decanter-2.9.0 > > > The history within the event can cause a lot of unstructed data. Every > history item is added at the top level with other fields like properties, > inHeaders, ... > History should be written to the field "history". > It can be configured whether history should be written or not like > properties, headers and body. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KARAF-7260) Add a field to include only some categories in the collector log
[ https://issues.apache.org/jira/browse/KARAF-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon updated KARAF-7260: -- Description: Today we can only (was: The history within the event can cause a lot of unstructed data. Every history item is added at the top level with other fields like properties, inHeaders, ... History should be written to the field "history". It can be configured whether history should be written or not like properties, headers and body.) > Add a field to include only some categories in the collector log > > > Key: KARAF-7260 > URL: https://issues.apache.org/jira/browse/KARAF-7260 > Project: Karaf > Issue Type: New Feature > Components: decanter >Affects Versions: decanter-2.8.0 >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: decanter-2.9.0 > > > Today we can only -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-7260) Add a field to include only some categories in the collector log
Francois Papon created KARAF-7260: - Summary: Add a field to include only some categories in the collector log Key: KARAF-7260 URL: https://issues.apache.org/jira/browse/KARAF-7260 Project: Karaf Issue Type: New Feature Components: decanter Affects Versions: decanter-2.8.0 Reporter: Oliver Wulff Assignee: Jean-Baptiste Onofré Fix For: decanter-2.9.0 The history within the event can cause a lot of unstructed data. Every history item is added at the top level with other fields like properties, inHeaders, ... History should be written to the field "history". It can be configured whether history should be written or not like properties, headers and body. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-7003) Manage connection exception on REST collector
Francois Papon created KARAF-7003: - Summary: Manage connection exception on REST collector Key: KARAF-7003 URL: https://issues.apache.org/jira/browse/KARAF-7003 Project: Karaf Issue Type: Improvement Components: decanter Reporter: Francois Papon Fix For: decanter-2.7.0 When having a connection exception with the collector REST, the data is send without http response wrapping. We could add some configuration to allow user to set: * enable http response wrapping * define http response code The http response should contain: * http response code * connection exception message * collected url informations (host, port, path) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-6712) Upgrade to Apache pom parent 23
Francois Papon created KARAF-6712: - Summary: Upgrade to Apache pom parent 23 Key: KARAF-6712 URL: https://issues.apache.org/jira/browse/KARAF-6712 Project: Karaf Issue Type: Dependency upgrade Components: decanter Reporter: Francois Papon Assignee: Francois Papon Fix For: decanter-2.5.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-6711) Upgrade to Apache pom parent 23
Francois Papon created KARAF-6711: - Summary: Upgrade to Apache pom parent 23 Key: KARAF-6711 URL: https://issues.apache.org/jira/browse/KARAF-6711 Project: Karaf Issue Type: Dependency upgrade Components: cellar Reporter: Francois Papon Assignee: Francois Papon Fix For: cellar-4.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-6710) Upgrade to Apache pom parent 23
Francois Papon created KARAF-6710: - Summary: Upgrade to Apache pom parent 23 Key: KARAF-6710 URL: https://issues.apache.org/jira/browse/KARAF-6710 Project: Karaf Issue Type: Dependency upgrade Components: cave Reporter: Francois Papon Assignee: Francois Papon Fix For: cave-4.2.2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-6709) Upgrade to Apache pom parent 23
Francois Papon created KARAF-6709: - Summary: Upgrade to Apache pom parent 23 Key: KARAF-6709 URL: https://issues.apache.org/jira/browse/KARAF-6709 Project: Karaf Issue Type: Dependency upgrade Components: karaf Reporter: Francois Papon Assignee: Francois Papon Fix For: 4.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-6703) Spec features and cleanup
Francois Papon created KARAF-6703: - Summary: Spec features and cleanup Key: KARAF-6703 URL: https://issues.apache.org/jira/browse/KARAF-6703 Project: Karaf Issue Type: Task Components: karaf Reporter: Francois Papon Assignee: Francois Papon Fix For: 4.3.0 As already discussed, we should remove the lib/jdk9plus folder and all spec packages from etc/jre.properties to use spec features instead. That will give us more control in the specs version and support of JDK. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (KARAF-5910) Improve REST collectors and appender with basic auth and extended user configuration
[ https://issues.apache.org/jira/browse/KARAF-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon reassigned KARAF-5910: - Assignee: Francois Papon (was: Jean-Baptiste Onofré) > Improve REST collectors and appender with basic auth and extended user > configuration > > > Key: KARAF-5910 > URL: https://issues.apache.org/jira/browse/KARAF-5910 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Francois Papon >Priority: Major > Fix For: decanter-2.5.0 > > > The REST appender is pretty basic: it uses the collected data json as a REST > POST request configured by the user. > However, it doesn't support at least basic authentication, or other REST > verb. It would be great to give more flexibility to users. > On the other hand, the REST collectors (scheduled and servlet) are pretty > minimal in term of configuration. > I will extend gives more flexibility here. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KARAF-5910) Improve REST collectors and appender with basic auth and extended user configuration
[ https://issues.apache.org/jira/browse/KARAF-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090340#comment-17090340 ] Francois Papon commented on KARAF-5910: --- [~jbonofre] as we discuss, I will work on this one. > Improve REST collectors and appender with basic auth and extended user > configuration > > > Key: KARAF-5910 > URL: https://issues.apache.org/jira/browse/KARAF-5910 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: decanter-2.5.0 > > > The REST appender is pretty basic: it uses the collected data json as a REST > POST request configured by the user. > However, it doesn't support at least basic authentication, or other REST > verb. It would be great to give more flexibility to users. > On the other hand, the REST collectors (scheduled and servlet) are pretty > minimal in term of configuration. > I will extend gives more flexibility here. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KARAF-6655) Getting a HTTP 404 for the namespace http://karaf.apache.org/xmlns/features-processing/v1.0.0
[ https://issues.apache.org/jira/browse/KARAF-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066961#comment-17066961 ] Francois Papon commented on KARAF-6655: --- Feature XSD are available here: [https://karaf.apache.org/xmlns/features/] > Getting a HTTP 404 for the namespace > http://karaf.apache.org/xmlns/features-processing/v1.0.0 > - > > Key: KARAF-6655 > URL: https://issues.apache.org/jira/browse/KARAF-6655 > Project: Karaf > Issue Type: Bug >Reporter: Oliver Limberg >Priority: Minor > > I guess the XSD should be available at the specified URL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-6620) Remove the spring-boot-starter-decanter module
Francois Papon created KARAF-6620: - Summary: Remove the spring-boot-starter-decanter module Key: KARAF-6620 URL: https://issues.apache.org/jira/browse/KARAF-6620 Project: Karaf Issue Type: Task Components: decanter Reporter: Francois Papon Assignee: Francois Papon Fix For: decanter-2.3.0 The spring-boot-starter-decanter module is not used anymore and we could remove it. It will still be available on older versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KARAF-6602) History shell command is broken
[
https://issues.apache.org/jira/browse/KARAF-6602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018644#comment-17018644
]
Francois Papon commented on KARAF-6602:
---
[~jbonofre] ok ;)
> History shell command is broken
> ---
>
> Key: KARAF-6602
> URL: https://issues.apache.org/jira/browse/KARAF-6602
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.8
>Reporter: Francois Papon
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.9
>
>
> {{The history shell command throw an exception since JLine 3.13.x upgrade:}}
> {code:java}
> karaf@root()> history
> [Karaf local console user karaf] ERROR
> org.apache.karaf.shell.support.ShellUtil - Exception caught while executing
> command
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:143)
> at
> org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.lambda$wrap$0(SessionFactoryImpl.java:218)
> at
> org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.execute(SessionFactoryImpl.java:264)
> at
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
> at
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:599)
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:526)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:415)
> at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:416)
> at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229)
> at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoSuchMethodError:
> org.jline.builtins.Commands.history(Lorg/jline/reader/LineReader;Ljava/io/PrintStream;Ljava/io/PrintStream;[Ljava/lang/String;)V
> at org.apache.felix.gogo.jline.Builtin.history(Builtin.java:643)
> ... 19 more
> Error executing command: java.lang.reflect.InvocationTargetException{code}
>
> Link to the JLine dependency update:
> [https://issues.apache.org/jira/browse/KARAF-6543]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KARAF-6602) History shell command is broken
[
https://issues.apache.org/jira/browse/KARAF-6602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018311#comment-17018311
]
Francois Papon commented on KARAF-6602:
---
The signature of the method Commands.history from JLine 3.13.x have a new
parameter:
[https://github.com/jline/jline3/blob/fd153e3468673782f65319ff776380d94ad00864/builtins/src/main/java/org/jline/builtins/Commands.java#L174]
And the felix gogo jline used the 3.7.0:
[https://github.com/apache/felix/blob/a13ea8ea177933e2911b14e1de55fff4e5196927/gogo/jline/src/main/java/org/apache/felix/gogo/jline/Builtin.java#L643]
The range import from felix gogo jline is
{code:java}
org.jline*;version="[3.0,4)"{code}
> History shell command is broken
> ---
>
> Key: KARAF-6602
> URL: https://issues.apache.org/jira/browse/KARAF-6602
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.8
>Reporter: Francois Papon
>Assignee: Francois Papon
>Priority: Major
> Fix For: 4.3.0, 4.2.8
>
>
> {{The history shell command throw an exception since JLine 3.13.x upgrade:}}
> {code:java}
> karaf@root()> history
> [Karaf local console user karaf] ERROR
> org.apache.karaf.shell.support.ShellUtil - Exception caught while executing
> command
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:143)
> at
> org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.lambda$wrap$0(SessionFactoryImpl.java:218)
> at
> org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.execute(SessionFactoryImpl.java:264)
> at
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
> at
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:599)
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:526)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:415)
> at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:416)
> at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229)
> at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoSuchMethodError:
> org.jline.builtins.Commands.history(Lorg/jline/reader/LineReader;Ljava/io/PrintStream;Ljava/io/PrintStream;[Ljava/lang/String;)V
> at org.apache.felix.gogo.jline.Builtin.history(Builtin.java:643)
> ... 19 more
> Error executing command: java.lang.reflect.InvocationTargetException{code}
>
> Link to the JLine dependency update:
> [https://issues.apache.org/jira/browse/KARAF-6543]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (KARAF-6602) History shell command is broken
Francois Papon created KARAF-6602:
-
Summary: History shell command is broken
Key: KARAF-6602
URL: https://issues.apache.org/jira/browse/KARAF-6602
Project: Karaf
Issue Type: Bug
Components: karaf
Affects Versions: 4.2.8
Reporter: Francois Papon
Assignee: Francois Papon
Fix For: 4.3.0, 4.2.8
{{The history shell command throw an exception since JLine 3.13.x upgrade:}}
{code:java}
karaf@root()> history
[Karaf local console user karaf] ERROR org.apache.karaf.shell.support.ShellUtil
- Exception caught while executing command
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:143)
at
org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.lambda$wrap$0(SessionFactoryImpl.java:218)
at
org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.execute(SessionFactoryImpl.java:264)
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:599)
at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:526)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:415)
at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:416)
at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229)
at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoSuchMethodError:
org.jline.builtins.Commands.history(Lorg/jline/reader/LineReader;Ljava/io/PrintStream;Ljava/io/PrintStream;[Ljava/lang/String;)V
at org.apache.felix.gogo.jline.Builtin.history(Builtin.java:643)
... 19 more
Error executing command: java.lang.reflect.InvocationTargetException{code}
Link to the JLine dependency update:
[https://issues.apache.org/jira/browse/KARAF-6543]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (KARAF-6579) Improve the jaas command to be able to add a new realm
Francois Papon created KARAF-6579: - Summary: Improve the jaas command to be able to add a new realm Key: KARAF-6579 URL: https://issues.apache.org/jira/browse/KARAF-6579 Project: Karaf Issue Type: Improvement Components: karaf Reporter: Francois Papon Assignee: Francois Papon Fix For: 4.3.0, 4.2.9 For now, with the *jaas* command users can only manage existing realm and they have to use blueprint to add a new realm. It will be useful to be able to add a new realm with the command. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-6518) Error on create repository with custom location
Francois Papon created KARAF-6518: - Summary: Error on create repository with custom location Key: KARAF-6518 URL: https://issues.apache.org/jira/browse/KARAF-6518 Project: Karaf Issue Type: Bug Components: cave Affects Versions: cave-4.2.0 Reporter: Francois Papon Assignee: Francois Papon Fix For: cave-4.2.1 Custom location is not use when creating a repository. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (KARAF-6475) Use a thread pool executor in the collector system
[ https://issues.apache.org/jira/browse/KARAF-6475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-6475 started by Francois Papon. - > Use a thread pool executor in the collector system > -- > > Key: KARAF-6475 > URL: https://issues.apache.org/jira/browse/KARAF-6475 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Major > Fix For: decanter-2.3.0 > > > It would be useful to use a thread pool executor in order to execute the > system commands not in a sequential way. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-6475) Use a thread pool executor in the collector system
Francois Papon created KARAF-6475: - Summary: Use a thread pool executor in the collector system Key: KARAF-6475 URL: https://issues.apache.org/jira/browse/KARAF-6475 Project: Karaf Issue Type: Improvement Components: decanter Reporter: Francois Papon Assignee: Francois Papon Fix For: decanter-2.3.0 It would be useful to use a thread pool executor in order to execute the system commands not in a sequential way. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-6455) Improve SOAP collector by adding request response time
Francois Papon created KARAF-6455:
-
Summary: Improve SOAP collector by adding request response time
Key: KARAF-6455
URL: https://issues.apache.org/jira/browse/KARAF-6455
Project: Karaf
Issue Type: Improvement
Components: decanter
Reporter: Francois Papon
Assignee: Francois Papon
Fix For: decanter-2.3.0
We could add the request response time in milliseconds by adding a new data in
the event:
`{color:#6a8759}http.response.time`{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (KARAF-6318) Be able to persist AlertStore data
[
https://issues.apache.org/jira/browse/KARAF-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KARAF-6318 started by Francois Papon.
-
> Be able to persist AlertStore data
> --
>
> Key: KARAF-6318
> URL: https://issues.apache.org/jira/browse/KARAF-6318
> Project: Karaf
> Issue Type: Improvement
> Components: decanter
>Reporter: Francois Papon
>Assignee: Francois Papon
>Priority: Minor
> Fix For: decanter-2.3.0
>
>
> The error and warn alert are store in memory and is not persist when the
> Karaf instance is restarted.
> We could persist the Sets in a file located under the directory:
> {code:java}
> $KARAF_HOME/data
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (KARAF-6392) Be able to define event topic prefix in the collector system
[ https://issues.apache.org/jira/browse/KARAF-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-6392 started by Francois Papon. - > Be able to define event topic prefix in the collector system > > > Key: KARAF-6392 > URL: https://issues.apache.org/jira/browse/KARAF-6392 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > Fix For: decanter-2.3.0 > > > Actually, it's not possible to customize the prefix of the event admin topic > for the collector system. > It would be usefull to have this option in the config property file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (KARAF-6375) Upgrade to cassandra 3.11.4
[ https://issues.apache.org/jira/browse/KARAF-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-6375 started by Francois Papon. - > Upgrade to cassandra 3.11.4 > --- > > Key: KARAF-6375 > URL: https://issues.apache.org/jira/browse/KARAF-6375 > Project: Karaf > Issue Type: Dependency upgrade > Components: decanter >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Major > Fix For: decanter-2.3.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-6392) Be able to define event topic prefix in the collector system
Francois Papon created KARAF-6392: - Summary: Be able to define event topic prefix in the collector system Key: KARAF-6392 URL: https://issues.apache.org/jira/browse/KARAF-6392 Project: Karaf Issue Type: Improvement Components: decanter Reporter: Francois Papon Assignee: Francois Papon Fix For: decanter-2.3.0 Actually, it's not possible to customize the prefix of the event admin topic for the collector system. It would be usefull to have this option in the config property file. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (KARAF-6379) Update to CXF 3.1.18 and Common-IO 2.6
Francois Papon created KARAF-6379: - Summary: Update to CXF 3.1.18 and Common-IO 2.6 Key: KARAF-6379 URL: https://issues.apache.org/jira/browse/KARAF-6379 Project: Karaf Issue Type: Dependency upgrade Components: cave Reporter: Francois Papon Fix For: cave-4.2.0 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KARAF-6376) Upgrade to Karaf 4.2.6
Francois Papon created KARAF-6376: - Summary: Upgrade to Karaf 4.2.6 Key: KARAF-6376 URL: https://issues.apache.org/jira/browse/KARAF-6376 Project: Karaf Issue Type: Dependency upgrade Components: cave Reporter: Francois Papon Assignee: Francois Papon Fix For: cave-4.2.0 We should upgrade the dependency to Karaf 4.2.6 for using the new 1.5.0 and 1.6.0 feature namespace used in the `org.apache.karaf.features.internal.model.JaxbUtil`. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KARAF-6375) Upgrade to cassandra 3.11.4
Francois Papon created KARAF-6375: - Summary: Upgrade to cassandra 3.11.4 Key: KARAF-6375 URL: https://issues.apache.org/jira/browse/KARAF-6375 Project: Karaf Issue Type: Dependency upgrade Components: decanter Reporter: Francois Papon Assignee: Francois Papon Fix For: decanter-2.3.0 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KARAF-6368) Add a property to define alert recoverable pattern
Francois Papon created KARAF-6368: - Summary: Add a property to define alert recoverable pattern Key: KARAF-6368 URL: https://issues.apache.org/jira/browse/KARAF-6368 Project: Karaf Issue Type: Improvement Components: decanter Reporter: Francois Papon Assignee: Francois Papon Fix For: decanter-2.3.0 We could add a new property in the alerting checker to define a pattern in order to filter message for recoverable alert. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KARAF-6318) Be able to persist AlertStore data
Francois Papon created KARAF-6318:
-
Summary: Be able to persist AlertStore data
Key: KARAF-6318
URL: https://issues.apache.org/jira/browse/KARAF-6318
Project: Karaf
Issue Type: Improvement
Components: decanter
Reporter: Francois Papon
Assignee: Francois Papon
Fix For: decanter-2.3.0
The error and warn alert are store in memory and is not persist when the Karaf
instance is restarted.
We could persist the Sets in a file located under the directory:
{code:java}
$KARAF_HOME/data
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-6295) Avoid confusion between rest collector and rest-servlet collector
Francois Papon created KARAF-6295:
-
Summary: Avoid confusion between rest collector and rest-servlet
collector
Key: KARAF-6295
URL: https://issues.apache.org/jira/browse/KARAF-6295
Project: Karaf
Issue Type: Task
Components: decanter
Reporter: Francois Papon
Assignee: Francois Papon
Fix For: decanter-2.3.0
The *collector-rest* and the *collector-rest-servlet* define the same package
and the same class:
{code:java}
org.apache.karaf.decanter.collector.rest
{code}
{code:java}
public class RestCollector
{code}
This is a problem when debugging to match the right source code.
We should update the *collector-rest-servlet* to have:
{code:java}
org.apache.karaf.decanter.collector.rest.servlet
{code}
{code:java}
public class RestServletCollector
{code}
We also could change the event topic from
{code:java}
decanter/collect/rest
{code}
to
{code:java}
decanter/collect/rest-servlet
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-6292) Default collector-rest topic
Francois Papon created KARAF-6292:
-
Summary: Default collector-rest topic
Key: KARAF-6292
URL: https://issues.apache.org/jira/browse/KARAF-6292
Project: Karaf
Issue Type: Bug
Components: decanter
Reporter: Francois Papon
Assignee: Francois Papon
Fix For: decanter-2.3.0
The default topic define by the *collector-rest* is not handle by the default
appenders topic.
We should have:
{code:java}
decanter/collect/rest{code}
{color:#6a8759} but we have:{color}
{code:java}
decanter/collect{code}
{color:#6a8759}by default.
{color}
{color:#6a8759}A workaround is to define the topic in the cfg config file of
the collector.
{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-6286) Upgrade to Apache Felix Webconsole 4.3.10
[ https://issues.apache.org/jira/browse/KARAF-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon updated KARAF-6286: -- Summary: Upgrade to Apache Felix Webconsole 4.3.10 (was: Apache Felix Webconsole 4.3.10) > Upgrade to Apache Felix Webconsole 4.3.10 > - > > Key: KARAF-6286 > URL: https://issues.apache.org/jira/browse/KARAF-6286 > Project: Karaf > Issue Type: Improvement > Components: webconsole >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Major > Fix For: 4.3.0, 4.2.6 > > > Related to: > Improvement: > * [FELIX-5934] - The web console stores unsalted hashed password > Bug: > * [FELIX-6128] - Escape bundle name and manifest headers > * [FELIX-6127] - Escape name hint in configuration listing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6286) Apache Felix Webconsole 4.3.10
Francois Papon created KARAF-6286: - Summary: Apache Felix Webconsole 4.3.10 Key: KARAF-6286 URL: https://issues.apache.org/jira/browse/KARAF-6286 Project: Karaf Issue Type: Improvement Components: webconsole Reporter: Francois Papon Assignee: Francois Papon Fix For: 4.3.0, 4.2.6 Related to: Improvement: * [FELIX-5934] - The web console stores unsalted hashed password Bug: * [FELIX-6128] - Escape bundle name and manifest headers * [FELIX-6127] - Escape name hint in configuration listing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6242) Improve Split and Regex parser by casting data
Francois Papon created KARAF-6242: - Summary: Improve Split and Regex parser by casting data Key: KARAF-6242 URL: https://issues.apache.org/jira/browse/KARAF-6242 Project: Karaf Issue Type: Improvement Components: decanter Reporter: Francois Papon Assignee: Francois Papon Fix For: decanter-2.3.0 When parsing data with Split and Regex parser, we don't check if it could be sent as Integer or Long. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5876) Examples path too long when extracting zip on Windows
[ https://issues.apache.org/jira/browse/KARAF-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16748043#comment-16748043 ] Francois Papon commented on KARAF-5876: --- +1 :) > Examples path too long when extracting zip on Windows > - > > Key: KARAF-5876 > URL: https://issues.apache.org/jira/browse/KARAF-5876 > Project: Karaf > Issue Type: Task > Components: karaf >Affects Versions: 4.2.1 >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > > When unpacking the zip on windows, a warning of path too long for > BookingServiceImpl.java appear. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-4942) Webconsole branding does not work
[ https://issues.apache.org/jira/browse/KARAF-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16741118#comment-16741118 ] Francois Papon commented on KARAF-4942: --- Thanks [~jbonofre]! I tried many things to fix it but without success... > Webconsole branding does not work > - > > Key: KARAF-4942 > URL: https://issues.apache.org/jira/browse/KARAF-4942 > Project: Karaf > Issue Type: Bug > Components: webconsole >Affects Versions: 4.0.8 > Environment: Debian Linux >Reporter: Ivo Leitão >Assignee: Jean-Baptiste Onofré >Priority: Major > > I've followed the documentation in the website to brand my webconsole however > it does not work. I've verified that my fragment bundle attaches to the karaf > webconsole bundle and provided all the files needed. It simply does not work. > I've done this for plain felix webconsole and it works fine. It must be > related with the karaf repackaging of webconsole. > I've checked online and found the > http://karaf.922171.n3.nabble.com/Can-t-brand-the-webconsole-td4038868.html. > The problem is the same actually. I've also found this example at > https://github.com/liveSense/org.liveSense.karaf/tree/master/webconsole-branding > which seems for a previous version. The only difference here is that > JaasSecurityProvider.java is provided also and I'm not doing this (this file > in the new version is not in the same place anyway...) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6009) Be able to add filter on elasticsearch rest appender
[ https://issues.apache.org/jira/browse/KARAF-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725053#comment-16725053 ] Francois Papon commented on KARAF-6009: --- Great! It make sense to implement this logic in all appenders. > Be able to add filter on elasticsearch rest appender > > > Key: KARAF-6009 > URL: https://issues.apache.org/jira/browse/KARAF-6009 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Major > Fix For: decanter-2.2.0 > > > It would be interesting to be able to declare multiple > decanter-appender-elasticsearch configuration in order to append in multiple > Elasticsearch indexes and we also could add a filter on the collected data to > choose the data that we will append on a specific index. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6033) Command "shell wrapper:install" fails
[
https://issues.apache.org/jira/browse/KARAF-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709610#comment-16709610
]
Francois Papon commented on KARAF-6033:
---
I tested with 4.2.1 and I can reproduce.
However, it's ok with the last 4.2.2-SNAPSHOT.
> Command "shell wrapper:install" fails
> -
>
> Key: KARAF-6033
> URL: https://issues.apache.org/jira/browse/KARAF-6033
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
> Environment: centos 7 and mac high sierra
>Reporter: Ryan Yeats
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Labels: jline, karaf-shell
> Fix For: 4.2.2
>
>
> The latest release appears to have regressed calling the wrapper:install
> command from the shell
> {noformat}
> {15:55}~/Downloads/apache-karaf-4.2.1/bin ➭ ./shell wrapper:install
> shell: Enabling Java debug options:
> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005
> Listening for transport dt_socket at address: 5005
> Exception in thread "main" java.lang.NullPointerException: "in" is null!
> at java.nio.channels.Channels.checkNotNull(Channels.java:67)
> at java.nio.channels.Channels.newChannel(Channels.java:347)
> at
> org.apache.felix.gogo.runtime.CommandSessionImpl.(CommandSessionImpl.java:109)
> at
> org.apache.felix.gogo.runtime.CommandProcessorImpl.createSession(CommandProcessorImpl.java:84)
> at
> org.apache.felix.gogo.runtime.CommandProcessorImpl.createSession(CommandProcessorImpl.java:40)
> at
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.(ConsoleSessionImpl.java:157)
> at
> org.apache.karaf.shell.impl.console.SessionFactoryImpl.create(SessionFactoryImpl.java:159)
> at
> org.apache.karaf.shell.impl.console.standalone.Main.createSession(Main.java:175)
> at org.apache.karaf.shell.impl.console.standalone.Main.run(Main.java:138)
> at org.apache.karaf.shell.impl.console.standalone.Main.run(Main.java:131)
> at org.apache.karaf.shell.impl.console.standalone.Main.run(Main.java:74)
> at
> org.apache.karaf.shell.impl.console.standalone.Main.main(Main.java:56){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work started] (KARAF-6009) Be able to add filter on elasticsearch rest appender
[ https://issues.apache.org/jira/browse/KARAF-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-6009 started by Francois Papon. - > Be able to add filter on elasticsearch rest appender > > > Key: KARAF-6009 > URL: https://issues.apache.org/jira/browse/KARAF-6009 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Major > Fix For: decanter-2.2.0 > > > It would be interesting to be able to declare multiple > decanter-appender-elasticsearch configuration in order to append in multiple > Elasticsearch indexes and we also could add a filter on the collected data to > choose the data that we will append on a specific index. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6009) Be able to add filter on elasticsearch rest appender
Francois Papon created KARAF-6009: - Summary: Be able to add filter on elasticsearch rest appender Key: KARAF-6009 URL: https://issues.apache.org/jira/browse/KARAF-6009 Project: Karaf Issue Type: Improvement Components: decanter Reporter: Francois Papon Assignee: Francois Papon Fix For: decanter-2.2.0 It would be interesting to be able to declare multiple decanter-appender-elasticsearch configuration in order to append in multiple Elasticsearch indexes and we also could add a filter on the collected data to choose the data that we will append on a specific index. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-5976) Add TimescaleDB appender
[ https://issues.apache.org/jira/browse/KARAF-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5976 started by Francois Papon. - > Add TimescaleDB appender > > > Key: KARAF-5976 > URL: https://issues.apache.org/jira/browse/KARAF-5976 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Major > Fix For: decanter-2.2.0 > > > TimescaleDB is an open source time-series database powered by PostgreSQL. > We could add an appender to store collected data into a TimescaleDB database. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5976) Add TimescaleDB appender
Francois Papon created KARAF-5976: - Summary: Add TimescaleDB appender Key: KARAF-5976 URL: https://issues.apache.org/jira/browse/KARAF-5976 Project: Karaf Issue Type: Improvement Components: decanter Reporter: Francois Papon Assignee: Francois Papon Fix For: decanter-2.2.0 TimescaleDB is an open source time-series database powered by PostgreSQL. We could add an appender to store collected data into a TimescaleDB database. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5972) Add the row data collect type Numeric for the collector-jdbc
Francois Papon created KARAF-5972: - Summary: Add the row data collect type Numeric for the collector-jdbc Key: KARAF-5972 URL: https://issues.apache.org/jira/browse/KARAF-5972 Project: Karaf Issue Type: Improvement Components: decanter Reporter: Francois Papon Assignee: Francois Papon Fix For: decanter-2.2.0 When parsing the resultSet rows, row with the numeric column type is not put in the collect data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-5972) Add the row data collect type Numeric for the collector-jdbc
[ https://issues.apache.org/jira/browse/KARAF-5972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5972 started by Francois Papon. - > Add the row data collect type Numeric for the collector-jdbc > > > Key: KARAF-5972 > URL: https://issues.apache.org/jira/browse/KARAF-5972 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > Fix For: decanter-2.2.0 > > > When parsing the resultSet rows, row with the numeric column type is not put > in the collect data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-5899) Use the asciidoctor-maven-plugin and custom ASF theme for the manual generation
[ https://issues.apache.org/jira/browse/KARAF-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon resolved KARAF-5899. --- Resolution: Fixed > Use the asciidoctor-maven-plugin and custom ASF theme for the manual > generation > --- > > Key: KARAF-5899 > URL: https://issues.apache.org/jira/browse/KARAF-5899 > Project: Karaf > Issue Type: Documentation > Components: cellar >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Trivial > Fix For: cellar-4.1.2, cellar-4.2.0 > > > The > [asciidoctor-maven-plugin|https://github.com/asciidoctor/asciidoctor-maven-plugin] > provide the capability for user to have a custom theme for rendering *html* > and *pdf* generation. > We could make a custom theme related to the [Apache Software > Foundation|https://apache.org/] website for both *html* and *pdf* manual > documentation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-5904) Use the asciidoctor-maven-plugin and custom ASF theme for the manual generation
[ https://issues.apache.org/jira/browse/KARAF-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5904 started by Francois Papon. - > Use the asciidoctor-maven-plugin and custom ASF theme for the manual > generation > --- > > Key: KARAF-5904 > URL: https://issues.apache.org/jira/browse/KARAF-5904 > Project: Karaf > Issue Type: Documentation > Components: decanter >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Trivial > Fix For: decanter-2.2.0 > > > The > [asciidoctor-maven-plugin|https://github.com/asciidoctor/asciidoctor-maven-plugin] > provide the capability for user to have a custom theme for rendering *html* > and *pdf* generation. > We could make a custom theme related to the [Apache Software > Foundation|https://apache.org/] website for both *html* and *pdf* manual > documentation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-5899) Use the asciidoctor-maven-plugin and custom ASF theme for the manual generation
[ https://issues.apache.org/jira/browse/KARAF-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5899 started by Francois Papon. - > Use the asciidoctor-maven-plugin and custom ASF theme for the manual > generation > --- > > Key: KARAF-5899 > URL: https://issues.apache.org/jira/browse/KARAF-5899 > Project: Karaf > Issue Type: Documentation > Components: cellar >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Trivial > Fix For: cellar-4.1.2 > > > The > [asciidoctor-maven-plugin|https://github.com/asciidoctor/asciidoctor-maven-plugin] > provide the capability for user to have a custom theme for rendering *html* > and *pdf* generation. > We could make a custom theme related to the [Apache Software > Foundation|https://apache.org/] website for both *html* and *pdf* manual > documentation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5919) Be able to store Http Proxy list in order to keep configuration after restart
Francois Papon created KARAF-5919: - Summary: Be able to store Http Proxy list in order to keep configuration after restart Key: KARAF-5919 URL: https://issues.apache.org/jira/browse/KARAF-5919 Project: Karaf Issue Type: Improvement Components: karaf Reporter: Francois Papon Assignee: Francois Papon Fix For: 4.2.2 The Http proxy feature provide a command to manage a list of proxy configuration but this list is in memory stored. It would be nice if we could persist this list to avoid to reconfigure it after restart the Karaf instance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5915) Improve the API Parser adding key data as parameter
Francois Papon created KARAF-5915: - Summary: Improve the API Parser adding key data as parameter Key: KARAF-5915 URL: https://issues.apache.org/jira/browse/KARAF-5915 Project: Karaf Issue Type: Improvement Components: decanter Reporter: Francois Papon Assignee: Francois Papon Fix For: decanter-2.2.0 Today we have the data key line defined in the parser. It would be interesting to add the key as parameter in the API that we could have a different key for each collector instance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-5906) Update to Apache Felix Webconsole 4.3.8 and latest jQuery UI 1.12.1
[ https://issues.apache.org/jira/browse/KARAF-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5906 started by Francois Papon. - > Update to Apache Felix Webconsole 4.3.8 and latest jQuery UI 1.12.1 > --- > > Key: KARAF-5906 > URL: https://issues.apache.org/jira/browse/KARAF-5906 > Project: Karaf > Issue Type: Improvement >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Major > Fix For: 4.3.0, 4.2.2, 4.1.7 > > > We are using Apache Felix Webconsole 4.3.4 and should be updated to the > latest 4.3.8 with JQuery 1.12.1. > https://issues.apache.org/jira/browse/FELIX-5901 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5906) Update to Apache Felix Webconsole 4.3.8 and latest jQuery UI 1.12.1
Francois Papon created KARAF-5906: - Summary: Update to Apache Felix Webconsole 4.3.8 and latest jQuery UI 1.12.1 Key: KARAF-5906 URL: https://issues.apache.org/jira/browse/KARAF-5906 Project: Karaf Issue Type: Improvement Reporter: Francois Papon Assignee: Francois Papon Fix For: 4.3.0, 4.2.2, 4.1.7 We are using Apache Felix Webconsole 4.3.4 and should be updated to the latest 4.3.8 with JQuery 1.12.1. https://issues.apache.org/jira/browse/FELIX-5901 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5904) Use the asciidoctor-maven-plugin and custom ASF theme for the manual generation
Francois Papon created KARAF-5904: - Summary: Use the asciidoctor-maven-plugin and custom ASF theme for the manual generation Key: KARAF-5904 URL: https://issues.apache.org/jira/browse/KARAF-5904 Project: Karaf Issue Type: Documentation Components: decanter Reporter: Francois Papon Assignee: Francois Papon Fix For: decanter-2.2.0 The [asciidoctor-maven-plugin|https://github.com/asciidoctor/asciidoctor-maven-plugin] provide the capability for user to have a custom theme for rendering *html* and *pdf* generation. We could make a custom theme related to the [Apache Software Foundation|https://apache.org/] website for both *html* and *pdf* manual documentation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-5898) Use the asciidoctor-maven-plugin and custom ASF theme for the manual generation
[ https://issues.apache.org/jira/browse/KARAF-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5898 started by Francois Papon. - > Use the asciidoctor-maven-plugin and custom ASF theme for the manual > generation > --- > > Key: KARAF-5898 > URL: https://issues.apache.org/jira/browse/KARAF-5898 > Project: Karaf > Issue Type: Documentation > Components: cave-documentation >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Trivial > Fix For: cave-4.2.0 > > > The > [asciidoctor-maven-plugin|https://github.com/asciidoctor/asciidoctor-maven-plugin] > provide the capability for user to have a custom theme for rendering *html* > and *pdf* generation. > We could make a custom theme related to the [Apache Software > Foundation|https://apache.org/] website for both *html* and *pdf* manual > documentation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5900) Use the asciidoctor-maven-plugin and custom ASF theme for the manual generation
Francois Papon created KARAF-5900: - Summary: Use the asciidoctor-maven-plugin and custom ASF theme for the manual generation Key: KARAF-5900 URL: https://issues.apache.org/jira/browse/KARAF-5900 Project: Karaf Issue Type: Documentation Components: karaf-documentation Reporter: Francois Papon Assignee: Francois Papon Fix For: 4.2.2 The [asciidoctor-maven-plugin|https://github.com/asciidoctor/asciidoctor-maven-plugin] provide the capability for user to have a custom theme for rendering *html* and *pdf* generation. We could make a custom theme related to the [Apache Software Foundation|https://apache.org/] website for both *html* and *pdf* manual documentation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5899) Use the asciidoctor-maven-plugin and custom ASF theme for the manual generation
Francois Papon created KARAF-5899: - Summary: Use the asciidoctor-maven-plugin and custom ASF theme for the manual generation Key: KARAF-5899 URL: https://issues.apache.org/jira/browse/KARAF-5899 Project: Karaf Issue Type: Documentation Components: cellar-documentation Reporter: Francois Papon Assignee: Francois Papon Fix For: cellar-4.1.2 The [asciidoctor-maven-plugin|https://github.com/asciidoctor/asciidoctor-maven-plugin] provide the capability for user to have a custom theme for rendering *html* and *pdf* generation. We could make a custom theme related to the [Apache Software Foundation|https://apache.org/] website for both *html* and *pdf* manual documentation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5898) Use the asciidoctor-maven-plugin and custom ASF theme for the manual generation
Francois Papon created KARAF-5898: - Summary: Use the asciidoctor-maven-plugin and custom ASF theme for the manual generation Key: KARAF-5898 URL: https://issues.apache.org/jira/browse/KARAF-5898 Project: Karaf Issue Type: Documentation Components: cave-documentation Reporter: Francois Papon Assignee: Francois Papon Fix For: cave-4.2.0 The [asciidoctor-maven-plugin|https://github.com/asciidoctor/asciidoctor-maven-plugin] provide the capability for user to have a custom theme for rendering *html* and *pdf* generation. We could make a custom theme related to the [Apache Software Foundation|https://apache.org/] website for both *html* and *pdf* manual documentation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5888) Be able to define a line parser service in the file collector
[ https://issues.apache.org/jira/browse/KARAF-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606191#comment-16606191 ] Francois Papon commented on KARAF-5888: --- In order to deal with the race condition if we use an OPTIONAL reference, the reference of the parser must exist for the activation of the collector. I propose to create a default raw parser as we have for the marshaller. Thoughts ? > Be able to define a line parser service in the file collector > - > > Key: KARAF-5888 > URL: https://issues.apache.org/jira/browse/KARAF-5888 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Francois Papon >Priority: Major > Fix For: decanter-2.1.0 > > > Now the file collector uses a tail that takes any new lines appended in a > file and send the "raw" line to the dispatcher. It would be great to be able > to use a line parser in the collector that send the extracted property from > the line. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5888) Be able to define a line parser service in the file collector
[ https://issues.apache.org/jira/browse/KARAF-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605437#comment-16605437 ] Francois Papon commented on KARAF-5888: --- We could create a new package "parser" in the api module in order to publish the Parser interface, like we did for the marshaller and unmarshaller. Thoughts ? > Be able to define a line parser service in the file collector > - > > Key: KARAF-5888 > URL: https://issues.apache.org/jira/browse/KARAF-5888 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Francois Papon >Priority: Major > Fix For: decanter-2.1.0 > > > Now the file collector uses a tail that takes any new lines appended in a > file and send the "raw" line to the dispatcher. It would be great to be able > to use a line parser in the collector that send the extracted property from > the line. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-5888) Be able to define a line parser service in the file collector
[ https://issues.apache.org/jira/browse/KARAF-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5888 started by Francois Papon. - > Be able to define a line parser service in the file collector > - > > Key: KARAF-5888 > URL: https://issues.apache.org/jira/browse/KARAF-5888 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Francois Papon >Priority: Major > Fix For: decanter-2.1.0 > > > Now the file collector uses a tail that takes any new lines appended in a > file and send the "raw" line to the dispatcher. It would be great to be able > to use a line parser in the collector that send the extracted property from > the line. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5893) Add Camel examples
Francois Papon created KARAF-5893: - Summary: Add Camel examples Key: KARAF-5893 URL: https://issues.apache.org/jira/browse/KARAF-5893 Project: Karaf Issue Type: Task Components: karaf-examples Reporter: Francois Papon Assignee: Jean-Baptiste Onofré Fix For: 4.2.2 Add a Camel examples using Blueprint and a Camel custom processor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5883) Installing activemq-broker on karaf 4.2.1 doesn't work
[
https://issues.apache.org/jira/browse/KARAF-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602364#comment-16602364
]
Francois Papon commented on KARAF-5883:
---
I think it related to the upgrade of Apache Felix Gogo version to 1.1.0
https://issues.apache.org/jira/browse/KARAF-5800
Apache ActiveMQ feature depends on *org.apache.felix.gogo.commands*
(version>=0.16.0)(!(version>=1.0.0)))
> Installing activemq-broker on karaf 4.2.1 doesn't work
> --
>
> Key: KARAF-5883
> URL: https://issues.apache.org/jira/browse/KARAF-5883
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.2.1
>Reporter: Orlando Bedoya Marin
>Priority: Minor
> Labels: activemq
>
> Installing activemq-broker on karaf 4.2.1 doesn't work
>
> {code:java}
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.2.1)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> feature:repo-add spring-legacy
> Adding feature url
> mvn:org.apache.karaf.features/spring-legacy/4.2.1/xml/features
> karaf@root()> feature:install aries-blueprint
> karaf@root()> feature:repo-add activemq
> Adding feature url mvn:org.apache.activemq/activemq-karaf/RELEASE/xml/features
> karaf@root()> feature:install activemq-broker
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
> missing requirement [root] osgi.identity; osgi.identity=activemq-broker;
> type=karaf.feature; version="[5.15.5,5.15.5]";
> filter:="(&(osgi.identity=activemq-broker)(type=karaf.feature)(version>=5.15.5)(version<=5.15.5))"
> [caused by: Unable to resolve activemq-broker/5.15.5: missing requirement
> [activemq-broker/5.15.5] osgi.identity; osgi.identity=activemq;
> type=karaf.feature; version="[5.15.5,5.15.5]" [caused by: Unable to resolve
> activemq/5.15.5: missing requirement [activemq/5.15.5] osgi.identity;
> osgi.identity=activemq-karaf; type=osgi.bundle; version="[5.15.5,5.15.5]";
> resolution:=mandatory [caused by: Unable to resolve activemq-karaf/5.15.5:
> missing requirement [activemq-karaf/5.15.5] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.apache.felix.gogo.commands)(version>=0.16.0)(!(version>=1.0.0)))"]]]
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> at
> org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332)
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to
> resolve activemq-broker/5.15.5: missing requirement [activemq-broker/5.15.5]
> osgi.identity; osgi.identity=activemq; type=karaf.feature;
> version="[5.15.5,5.15.5]" [caused by: Unable to resolve activemq/5.15.5:
> missing requirement [activemq/5.15.5] osgi.identity;
> osgi.identity=activemq-karaf; type=osgi.bundle; version="[5.15.5,5.15.5]";
> resolution:=mandatory [caused by: Unable to resolve activemq-karaf/5.15.5:
> missing requirement [activemq-karaf/5.15.5] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.apache.felix.gogo.commands)(version>=0.16.0)(!(version>=1.0.0)))"]]
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> ... 12 more
> Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to
> resolve activemq/5.15.5: missing requirement [activemq/5.15.5] osgi.identity;
> osgi.identity=activemq-karaf; type=osgi.bundle; version="[5.15.5,5.15.5]";
> resolution:=mandatory [caused by: Unable to resolve activemq-karaf/5.15.5:
> missing requirement [activemq-karaf/5.15.5] osgi.wiring.package;
> filter:="(&(osgi.wiring.
[jira] [Commented] (KARAF-5883) Installing activemq-broker on karaf 4.2.1 doesn't work
[
https://issues.apache.org/jira/browse/KARAF-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602359#comment-16602359
]
Francois Papon commented on KARAF-5883:
---
I can reproduce on 4.2.1
> Installing activemq-broker on karaf 4.2.1 doesn't work
> --
>
> Key: KARAF-5883
> URL: https://issues.apache.org/jira/browse/KARAF-5883
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.2.1
>Reporter: Orlando Bedoya Marin
>Priority: Minor
> Labels: activemq
>
> Installing activemq-broker on karaf 4.2.1 doesn't work
>
> {code:java}
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.2.1)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> feature:repo-add spring-legacy
> Adding feature url
> mvn:org.apache.karaf.features/spring-legacy/4.2.1/xml/features
> karaf@root()> feature:install aries-blueprint
> karaf@root()> feature:repo-add activemq
> Adding feature url mvn:org.apache.activemq/activemq-karaf/RELEASE/xml/features
> karaf@root()> feature:install activemq-broker
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
> missing requirement [root] osgi.identity; osgi.identity=activemq-broker;
> type=karaf.feature; version="[5.15.5,5.15.5]";
> filter:="(&(osgi.identity=activemq-broker)(type=karaf.feature)(version>=5.15.5)(version<=5.15.5))"
> [caused by: Unable to resolve activemq-broker/5.15.5: missing requirement
> [activemq-broker/5.15.5] osgi.identity; osgi.identity=activemq;
> type=karaf.feature; version="[5.15.5,5.15.5]" [caused by: Unable to resolve
> activemq/5.15.5: missing requirement [activemq/5.15.5] osgi.identity;
> osgi.identity=activemq-karaf; type=osgi.bundle; version="[5.15.5,5.15.5]";
> resolution:=mandatory [caused by: Unable to resolve activemq-karaf/5.15.5:
> missing requirement [activemq-karaf/5.15.5] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.apache.felix.gogo.commands)(version>=0.16.0)(!(version>=1.0.0)))"]]]
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> at
> org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332)
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to
> resolve activemq-broker/5.15.5: missing requirement [activemq-broker/5.15.5]
> osgi.identity; osgi.identity=activemq; type=karaf.feature;
> version="[5.15.5,5.15.5]" [caused by: Unable to resolve activemq/5.15.5:
> missing requirement [activemq/5.15.5] osgi.identity;
> osgi.identity=activemq-karaf; type=osgi.bundle; version="[5.15.5,5.15.5]";
> resolution:=mandatory [caused by: Unable to resolve activemq-karaf/5.15.5:
> missing requirement [activemq-karaf/5.15.5] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.apache.felix.gogo.commands)(version>=0.16.0)(!(version>=1.0.0)))"]]
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> ... 12 more
> Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to
> resolve activemq/5.15.5: missing requirement [activemq/5.15.5] osgi.identity;
> osgi.identity=activemq-karaf; type=osgi.bundle; version="[5.15.5,5.15.5]";
> resolution:=mandatory [caused by: Unable to resolve activemq-karaf/5.15.5:
> missing requirement [activemq-karaf/5.15.5] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.apache.felix.gogo.commands)(version>=0.16.0)(!(version>=1.0.0)))"]
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> ... 13 mo
[jira] [Commented] (KARAF-5793) Provide an option replace the dot or not in json field in the JsonMarshaller
[
https://issues.apache.org/jira/browse/KARAF-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597123#comment-16597123
]
Francois Papon commented on KARAF-5793:
---
Hi,
May be it would be better to not transform data in the default marshaller and
let user make it's own.
Thoughts ?
> Provide an option replace the dot or not in json field in the JsonMarshaller
>
>
> Key: KARAF-5793
> URL: https://issues.apache.org/jira/browse/KARAF-5793
> Project: Karaf
> Issue Type: Improvement
> Components: decanter
>Affects Versions: decanter-2.0.0
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: decanter-2.1.0
>
>
> The dot "." is replaced by "_" in json fields after changes from KARAF-4295.
> The reason could be that the field names containing dots will be rejected in
> ES 2.x (https://github.com/elastic/elasticsearch/issues/15951). but ES 5.x,
> 6.x support it again (parse it as Object). see
> https://www.elastic.co/guide/en/elasticsearch/reference/2.4/dots-in-names.html#_enabling_support_for_dots_in_field_names
> . Also there is an ENV option provided by ES to allow dots in the field
> name:
> {code}
> export ES_JAVA_OPTS="-Dmapper.allow_dots_in_name=true"
> {code}
> To give more compatibility and flexibility to the user, we may provide an
> option "replaceDotInFields=true/false" for the Json Marshaller. for now any
> custom fields name with "." woud be replaced by "_" silently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5783) Change implementation of Cave Deployer REST to mimic Cave Server
[ https://issues.apache.org/jira/browse/KARAF-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16596290#comment-16596290 ] Francois Papon commented on KARAF-5783: --- +1 It make sense to align the base path. > Change implementation of Cave Deployer REST to mimic Cave Server > > > Key: KARAF-5783 > URL: https://issues.apache.org/jira/browse/KARAF-5783 > Project: Karaf > Issue Type: Improvement > Components: cave-server >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: cave-4.1.1 > > > Actually, the Cave Server Rest bundle use a CXFNonSpringJaxrsServlet in > order to publish the Rest endpoint. > We should use Blueprint as the Cave Deployer Rest bundle. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5880) Add itests module
[ https://issues.apache.org/jira/browse/KARAF-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594965#comment-16594965 ] Francois Papon commented on KARAF-5880: --- Yes, I'm agree. > Add itests module > - > > Key: KARAF-5880 > URL: https://issues.apache.org/jira/browse/KARAF-5880 > Project: Karaf > Issue Type: New Feature > Components: cave-build >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > Fix For: cave-4.2.0 > > > It would be great to add a module for the integration test of the Cave > features. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5880) Add itests module
Francois Papon created KARAF-5880: - Summary: Add itests module Key: KARAF-5880 URL: https://issues.apache.org/jira/browse/KARAF-5880 Project: Karaf Issue Type: New Feature Components: cave-build Reporter: Francois Papon Assignee: Francois Papon Fix For: cave-4.1.1 It would be great to add a module for the integration test of the Cave features. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5876) Examples path too long when extracting zip on Windows
Francois Papon created KARAF-5876: - Summary: Examples path too long when extracting zip on Windows Key: KARAF-5876 URL: https://issues.apache.org/jira/browse/KARAF-5876 Project: Karaf Issue Type: Task Components: karaf-demo Affects Versions: 4.2.1 Reporter: Francois Papon Assignee: Francois Papon Fix For: 4.2.2 When unpacking the zip on windows, a warning of path too long for BookingServiceImpl.java appear. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5857) Upgrade to maven-compiler-plugin 3.8.0
Francois Papon created KARAF-5857: - Summary: Upgrade to maven-compiler-plugin 3.8.0 Key: KARAF-5857 URL: https://issues.apache.org/jira/browse/KARAF-5857 Project: Karaf Issue Type: Dependency upgrade Components: karaf-build Reporter: Francois Papon Assignee: Francois Papon Fix For: 4.2.1 Upgrade to maven-compiler-plugin 3.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-4942) Webconsole branding does not work
[ https://issues.apache.org/jira/browse/KARAF-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563425#comment-16563425 ] Francois Papon commented on KARAF-4942: --- I tested with a Karaf 4.2.0 and it's look like a class loader issue. The webconsole.properties provided by the custom bundle fragment doesn't override the webconsole.properties include by the karaf-webconsole. I will try to fix it. > Webconsole branding does not work > - > > Key: KARAF-4942 > URL: https://issues.apache.org/jira/browse/KARAF-4942 > Project: Karaf > Issue Type: Bug > Components: webconsole-karaf >Affects Versions: 4.0.8 > Environment: Debian Linux >Reporter: Ivo Leitão >Assignee: Francois Papon >Priority: Major > > I've followed the documentation in the website to brand my webconsole however > it does not work. I've verified that my fragment bundle attaches to the karaf > webconsole bundle and provided all the files needed. It simply does not work. > I've done this for plain felix webconsole and it works fine. It must be > related with the karaf repackaging of webconsole. > I've checked online and found the > http://karaf.922171.n3.nabble.com/Can-t-brand-the-webconsole-td4038868.html. > The problem is the same actually. I've also found this example at > https://github.com/liveSense/org.liveSense.karaf/tree/master/webconsole-branding > which seems for a previous version. The only difference here is that > JaasSecurityProvider.java is provided also and I'm not doing this (this file > in the new version is not in the same place anyway...) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-4942) Webconsole branding does not work
[ https://issues.apache.org/jira/browse/KARAF-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon reassigned KARAF-4942: - Assignee: Francois Papon > Webconsole branding does not work > - > > Key: KARAF-4942 > URL: https://issues.apache.org/jira/browse/KARAF-4942 > Project: Karaf > Issue Type: Bug > Components: webconsole-karaf >Affects Versions: 4.0.8 > Environment: Debian Linux >Reporter: Ivo Leitão >Assignee: Francois Papon >Priority: Major > > I've followed the documentation in the website to brand my webconsole however > it does not work. I've verified that my fragment bundle attaches to the karaf > webconsole bundle and provided all the files needed. It simply does not work. > I've done this for plain felix webconsole and it works fine. It must be > related with the karaf repackaging of webconsole. > I've checked online and found the > http://karaf.922171.n3.nabble.com/Can-t-brand-the-webconsole-td4038868.html. > The problem is the same actually. I've also found this example at > https://github.com/liveSense/org.liveSense.karaf/tree/master/webconsole-branding > which seems for a previous version. The only difference here is that > JaasSecurityProvider.java is provided also and I'm not doing this (this file > in the new version is not in the same place anyway...) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5794) How to start Flowable in a Apache Karaf container
[ https://issues.apache.org/jira/browse/KARAF-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553840#comment-16553840 ] Francois Papon commented on KARAF-5794: --- I think it's better to ask in the mailing list. > How to start Flowable in a Apache Karaf container > - > > Key: KARAF-5794 > URL: https://issues.apache.org/jira/browse/KARAF-5794 > Project: Karaf > Issue Type: Question > Components: cave-maven, karaf-webcontainer >Affects Versions: 4.1.5 >Reporter: Ravi kumar >Priority: Major > > How to start Flowable in a Apache Karaf container -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (KARAF-5711) Add example section in documentation
[ https://issues.apache.org/jira/browse/KARAF-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon closed KARAF-5711. - Resolution: Fixed > Add example section in documentation > > > Key: KARAF-5711 > URL: https://issues.apache.org/jira/browse/KARAF-5711 > Project: Karaf > Issue Type: Improvement > Components: website >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > > The examples for Karaf will be included soon in the next release (4.2.1) and > it would be interesting to add a section related to them in the documentation > page. > We could add related link to the README.md source of each example on the > github project. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5711) Add example section in documentation
[ https://issues.apache.org/jira/browse/KARAF-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509521#comment-16509521 ] Francois Papon commented on KARAF-5711: --- This issue is included in KARAF-5712 -> close. > Add example section in documentation > > > Key: KARAF-5711 > URL: https://issues.apache.org/jira/browse/KARAF-5711 > Project: Karaf > Issue Type: Improvement > Components: website >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > > The examples for Karaf will be included soon in the next release (4.2.1) and > it would be interesting to add a section related to them in the documentation > page. > We could add related link to the README.md source of each example on the > github project. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5783) Change implementation of Cave server REST with Blueprint and Apache CXF
[ https://issues.apache.org/jira/browse/KARAF-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507397#comment-16507397 ] Francois Papon commented on KARAF-5783: --- Agree, this is what I was planned to do. > Change implementation of Cave server REST with Blueprint and Apache CXF > --- > > Key: KARAF-5783 > URL: https://issues.apache.org/jira/browse/KARAF-5783 > Project: Karaf > Issue Type: Improvement > Components: cave-server >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: cave-4.1.1 > > > Actually, the Cave Server Rest bundle use a CXFNonSpringJaxrsServlet in > order to publish the Rest endpoint. > We should use Blueprint as the Cave Deployer Rest bundle. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5783) Change implementation of Cave server REST with Blueprint and Apache CXF
Francois Papon created KARAF-5783: - Summary: Change implementation of Cave server REST with Blueprint and Apache CXF Key: KARAF-5783 URL: https://issues.apache.org/jira/browse/KARAF-5783 Project: Karaf Issue Type: Improvement Components: cave-server Reporter: Francois Papon Assignee: Francois Papon Fix For: cave-4.1.1 Actually, the Cave Server Rest bundle use a CXFNonSpringJaxrsServlet in order to publish the Rest endpoint. We should use Blueprint as the Cave Deployer Rest bundle. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5763) Rename the Cave server features
[ https://issues.apache.org/jira/browse/KARAF-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482937#comment-16482937 ] Francois Papon commented on KARAF-5763: --- Ok no problem, I had miss understood in the mail ;) > Rename the Cave server features > --- > > Key: KARAF-5763 > URL: https://issues.apache.org/jira/browse/KARAF-5763 > Project: Karaf > Issue Type: Improvement > Components: cave-server >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: cave-4.1.1 > > > In Cave subproject, we have this features : > > * cave-deployer > * cave-deployer-command > * cave-deployer-management > * cave-deployer-rest > * cave-deployer-service > * cave-http > * cave-maven > * cave-rest > * cave-server > * cave-storage > and we should rename the server feature like this : > * cave-server > * cave-server-http > * cave-server-maven > * cave-server-rest > * cave-server-storage -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5763) Rename the Cave server features
[ https://issues.apache.org/jira/browse/KARAF-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon updated KARAF-5763: -- Summary: Rename the Cave server features (was: Rename the server features) > Rename the Cave server features > --- > > Key: KARAF-5763 > URL: https://issues.apache.org/jira/browse/KARAF-5763 > Project: Karaf > Issue Type: Improvement > Components: cave-server >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > Fix For: cave-4.1.1 > > > In Cave subproject, we have this features : > > * cave-deployer > * cave-deployer-command > * cave-deployer-management > * cave-deployer-rest > * cave-deployer-service > * cave-http > * cave-maven > * cave-rest > * cave-server > * cave-storage > and we should rename the server feature like this : > * cave-server > * cave-server-http > * cave-server-maven > * cave-server-rest > * cave-server-storage -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5763) Rename the server features
Francois Papon created KARAF-5763: - Summary: Rename the server features Key: KARAF-5763 URL: https://issues.apache.org/jira/browse/KARAF-5763 Project: Karaf Issue Type: Improvement Components: cave-server Reporter: Francois Papon Assignee: Francois Papon Fix For: cave-4.1.1 In Cave subproject, we have this features : * cave-deployer * cave-deployer-command * cave-deployer-management * cave-deployer-rest * cave-deployer-service * cave-http * cave-maven * cave-rest * cave-server * cave-storage and we should rename the server feature like this : * cave-server * cave-server-http * cave-server-maven * cave-server-rest * cave-server-storage -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-5747) Add append file capability in decanter-appender-file
[ https://issues.apache.org/jira/browse/KARAF-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5747 started by Francois Papon. - > Add append file capability in decanter-appender-file > > > Key: KARAF-5747 > URL: https://issues.apache.org/jira/browse/KARAF-5747 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > Fix For: decanter-2.1.0 > > > The file created by the appender is cleaned at bootstrapping if already exist. > The use could choose if the appender append or not in the file already exist. > We could add a new property in the configuration file of the appender. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-5747) Add append file capability in decanter-appender-file
[ https://issues.apache.org/jira/browse/KARAF-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon reassigned KARAF-5747: - Assignee: Francois Papon > Add append file capability in decanter-appender-file > > > Key: KARAF-5747 > URL: https://issues.apache.org/jira/browse/KARAF-5747 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > Fix For: decanter-2.1.0 > > > The file created by the appender is cleaned at bootstrapping if already exist. > The use could choose if the appender append or not in the file already exist. > We could add a new property in the configuration file of the appender. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-5691) Add Http Service Filter Collector
[ https://issues.apache.org/jira/browse/KARAF-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5691 started by Francois Papon. - > Add Http Service Filter Collector > - > > Key: KARAF-5691 > URL: https://issues.apache.org/jira/browse/KARAF-5691 > Project: Karaf > Issue Type: Improvement > Components: decanter >Affects Versions: decanter-2.1.0 >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > Fix For: decanter-2.1.0 > > > Karaf Container propose a new HTTP Proxy feature. We could have a new > collector in order to probe the traffic. > We could use a Http Service Filter to capture the request/response > informations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-5691) Add Http Service Filter Collector
[ https://issues.apache.org/jira/browse/KARAF-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon reassigned KARAF-5691: - Assignee: Francois Papon > Add Http Service Filter Collector > - > > Key: KARAF-5691 > URL: https://issues.apache.org/jira/browse/KARAF-5691 > Project: Karaf > Issue Type: Improvement > Components: decanter >Affects Versions: decanter-2.1.0 >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > Fix For: decanter-2.1.0 > > > Karaf Container propose a new HTTP Proxy feature. We could have a new > collector in order to probe the traffic. > We could use a Http Service Filter to capture the request/response > informations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-5711) Add example section in documentation
[ https://issues.apache.org/jira/browse/KARAF-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5711 started by Francois Papon. - > Add example section in documentation > > > Key: KARAF-5711 > URL: https://issues.apache.org/jira/browse/KARAF-5711 > Project: Karaf > Issue Type: Improvement > Components: website >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > > The examples for Karaf will be included soon in the next release (4.2.1) and > it would be interesting to add a section related to them in the documentation > page. > We could add related link to the README.md source of each example on the > github project. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-5712) Upgrade website style to bootstrap 4
[ https://issues.apache.org/jira/browse/KARAF-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5712 started by Francois Papon. - > Upgrade website style to bootstrap 4 > > > Key: KARAF-5712 > URL: https://issues.apache.org/jira/browse/KARAF-5712 > Project: Karaf > Issue Type: Improvement > Components: website >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > > It would be great to upgrade the website style with Bootstrap 4 for > responsive design compatibility and to be more easy to upgrade content and > style. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-5712) Upgrade website style to bootstrap 4
[ https://issues.apache.org/jira/browse/KARAF-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon reassigned KARAF-5712: - Assignee: Francois Papon > Upgrade website style to bootstrap 4 > > > Key: KARAF-5712 > URL: https://issues.apache.org/jira/browse/KARAF-5712 > Project: Karaf > Issue Type: Improvement > Components: website >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > > It would be great to upgrade the website style with Bootstrap 4 for > responsive design compatibility and to be more easy to upgrade content and > style. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-5755) Publish javadoc on the website
[ https://issues.apache.org/jira/browse/KARAF-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon reassigned KARAF-5755: - Assignee: Francois Papon > Publish javadoc on the website > -- > > Key: KARAF-5755 > URL: https://issues.apache.org/jira/browse/KARAF-5755 > Project: Karaf > Issue Type: Improvement > Components: karaf-documentation, website >Reporter: Jean-Baptiste Onofré >Assignee: Francois Papon >Priority: Major > > In order to, at least, to provide the javadoc of the Karaf service interface, > it would be great to publish javadoc on the website (per version and per > subproject). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-5711) Add example section in documentation
[ https://issues.apache.org/jira/browse/KARAF-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Papon reassigned KARAF-5711: - Assignee: Francois Papon (was: Jean-Baptiste Onofré) > Add example section in documentation > > > Key: KARAF-5711 > URL: https://issues.apache.org/jira/browse/KARAF-5711 > Project: Karaf > Issue Type: Improvement > Components: website >Reporter: Francois Papon >Assignee: Francois Papon >Priority: Minor > > The examples for Karaf will be included soon in the next release (4.2.1) and > it would be interesting to add a section related to them in the documentation > page. > We could add related link to the README.md source of each example on the > github project. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5747) Add append file capability in decanter-appender-file
Francois Papon created KARAF-5747: - Summary: Add append file capability in decanter-appender-file Key: KARAF-5747 URL: https://issues.apache.org/jira/browse/KARAF-5747 Project: Karaf Issue Type: Improvement Components: decanter Reporter: Francois Papon Fix For: decanter-2.1.0 The file created by the appender is cleaned at bootstrapping if already exist. The use could choose if the appender append or not in the file already exist. We could add a new property in the configuration file of the appender. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-836) Add Karaf benefits page to Karaf website
[ https://issues.apache.org/jira/browse/KARAF-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471468#comment-16471468 ] Francois Papon commented on KARAF-836: -- Hi, is this issue still needed ? > Add Karaf benefits page to Karaf website > > > Key: KARAF-836 > URL: https://issues.apache.org/jira/browse/KARAF-836 > Project: Karaf > Issue Type: Improvement > Components: website >Reporter: Jamie goodyear >Priority: Major > > Add Karaf benefits page to Karaf website. > This should cover why Karaf is the best OSGi runtime, our extra features, > highlight our sub projects, and all the other cool things we have going for > Karaf :) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
