[jira] [Commented] (KARAF-3869) Use hazelcast-all artifact instead of hazelcast
[
https://issues.apache.org/jira/browse/KARAF-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130150#comment-15130150
]
Martin Fekete commented on KARAF-3869:
--
I think base one feature should be enough, either "simple" with core bundle
dependency mvn:com.hazelcast/hazelcast/${hazelcast.version} only,
or "all" with all bundles (except hibernate) that are merged into -all jar, it
seems all module bundles are fragments so theres no need to use hazelcast-all
bundle at all
"all" feature is way to go, if there was some requirements for functionality
from modules, if not then its better to stick with simple feature
> Use hazelcast-all artifact instead of hazelcast
> ---
>
> Key: KARAF-3869
> URL: https://issues.apache.org/jira/browse/KARAF-3869
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-hazelcast
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: cellar-4.0.0, cellar-3.0.4
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3869) Use hazelcast-all artifact instead of hazelcast
[ https://issues.apache.org/jira/browse/KARAF-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130100#comment-15130100 ] Martin Fekete commented on KARAF-3869: -- hazelcast-all includes hazelcast-hibernate3 this causes problem when someone want to use cellars hazelcast as 2nd level cache for hibernate4 > Use hazelcast-all artifact instead of hazelcast > --- > > Key: KARAF-3869 > URL: https://issues.apache.org/jira/browse/KARAF-3869 > Project: Karaf > Issue Type: Improvement > Components: cellar-hazelcast >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: cellar-4.0.0, cellar-3.0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3869) Use hazelcast-all artifact instead of hazelcast
[ https://issues.apache.org/jira/browse/KARAF-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130156#comment-15130156 ] Jean-Baptiste Onofré commented on KARAF-3869: - Fair enough, hazelcast-simple and hazelcast-all then ? > Use hazelcast-all artifact instead of hazelcast > --- > > Key: KARAF-3869 > URL: https://issues.apache.org/jira/browse/KARAF-3869 > Project: Karaf > Issue Type: Improvement > Components: cellar-hazelcast >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: cellar-4.0.0, cellar-3.0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3869) Use hazelcast-all artifact instead of hazelcast
[ https://issues.apache.org/jira/browse/KARAF-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130171#comment-15130171 ] Martin Fekete commented on KARAF-3869: -- hazelcast, hazelcast-all cellar-hazelcast depends on hazelcast hazelcast-all depends on hazelcast this will only affect 4.x if someone hazelcast feature (and needs functionality from -all) > Use hazelcast-all artifact instead of hazelcast > --- > > Key: KARAF-3869 > URL: https://issues.apache.org/jira/browse/KARAF-3869 > Project: Karaf > Issue Type: Improvement > Components: cellar-hazelcast >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: cellar-4.0.0, cellar-3.0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3869) Use hazelcast-all artifact instead of hazelcast
[ https://issues.apache.org/jira/browse/KARAF-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130184#comment-15130184 ] Jean-Baptiste Onofré commented on KARAF-3869: - Yes, it makes sense. Let me reopen this Jira to fix that. > Use hazelcast-all artifact instead of hazelcast > --- > > Key: KARAF-3869 > URL: https://issues.apache.org/jira/browse/KARAF-3869 > Project: Karaf > Issue Type: Improvement > Components: cellar-hazelcast >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: cellar-4.0.0, cellar-3.0.4, cellar-4.0.1, cellar-3.0.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3869) Use hazelcast-all artifact instead of hazelcast
[ https://issues.apache.org/jira/browse/KARAF-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3869: Fix Version/s: cellar-4.0.1 cellar-3.0.5 > Use hazelcast-all artifact instead of hazelcast > --- > > Key: KARAF-3869 > URL: https://issues.apache.org/jira/browse/KARAF-3869 > Project: Karaf > Issue Type: Improvement > Components: cellar-hazelcast >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: cellar-4.0.0, cellar-3.0.4, cellar-4.0.1, cellar-3.0.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (KARAF-3869) Use hazelcast-all artifact instead of hazelcast
[ https://issues.apache.org/jira/browse/KARAF-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reopened KARAF-3869: - > Use hazelcast-all artifact instead of hazelcast > --- > > Key: KARAF-3869 > URL: https://issues.apache.org/jira/browse/KARAF-3869 > Project: Karaf > Issue Type: Improvement > Components: cellar-hazelcast >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: cellar-4.0.0, cellar-3.0.4, cellar-4.0.1, cellar-3.0.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4296) Add mqtt appender
[ https://issues.apache.org/jira/browse/KARAF-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130301#comment-15130301 ] ASF subversion and git services commented on KARAF-4296: Commit 23959a0f7f979648de4feb7f02a8bd3b130059ca in karaf-decanter's branch refs/heads/master from [~ch...@die-schneider.net] [ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=23959a0 ] [KARAF-4296] Add mqtt appender > Add mqtt appender > - > > Key: KARAF-4296 > URL: https://issues.apache.org/jira/browse/KARAF-4296 > Project: Karaf > Issue Type: New Feature > Components: decanter >Affects Versions: decanter-1.0.1 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: decanter-1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4296) Add mqtt appender
[ https://issues.apache.org/jira/browse/KARAF-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated KARAF-4296: --- Description: Create new appender that sends to an mqtt server using eclipse paho mqtt client. Serialization will be json by default. > Add mqtt appender > - > > Key: KARAF-4296 > URL: https://issues.apache.org/jira/browse/KARAF-4296 > Project: Karaf > Issue Type: New Feature > Components: decanter >Affects Versions: decanter-1.0.1 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: decanter-1.0.2 > > > Create new appender that sends to an mqtt server using eclipse paho mqtt > client. Serialization will be json by default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4296) Add mqtt appender
[ https://issues.apache.org/jira/browse/KARAF-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved KARAF-4296. Resolution: Fixed > Add mqtt appender > - > > Key: KARAF-4296 > URL: https://issues.apache.org/jira/browse/KARAF-4296 > Project: Karaf > Issue Type: New Feature > Components: decanter >Affects Versions: decanter-1.0.1 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: decanter-1.0.2 > > > Create new appender that sends to an mqtt server using eclipse paho mqtt > client. Serialization will be json by default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4310) Installing kar causes karaf restart
[ https://issues.apache.org/jira/browse/KARAF-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131076#comment-15131076 ] Jean-Baptiste Onofré commented on KARAF-4310: - It's probably due to eventadmin: it triggers the refresh of shell console, so it's not a full restart, just a restart of the shell console IMHO. Does it happen with any kar file ? > Installing kar causes karaf restart > --- > > Key: KARAF-4310 > URL: https://issues.apache.org/jira/browse/KARAF-4310 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.4 > Environment: OpenSUSE Tumbleweed (4.4.0-2-default) oracle jdk 1.8.0_72 >Reporter: Michal Hlavac > > Prerequisites: > ```bash > feature:repo-add mvn:org.apache.cxf.karaf/apache-cxf/3.1.4/xml/features > feature:install pax-cdi war cxf eventadmin > ``` > In karaf 3.0.5 kar installation works properly (see attached log), but in > karaf 4.0.4 it seems instance is restarting and redeploy kar again which > cause some error (see attached log). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4310) Installing kar causes karaf restart
[
https://issues.apache.org/jira/browse/KARAF-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michal Hlavac updated KARAF-4310:
-
Description:
Prerequisites:
{code}
feature:repo-add mvn:org.apache.cxf.karaf/apache-cxf/3.1.4/xml/features
feature:install pax-cdi war cxf eventadmin
{code}
In karaf 3.0.5 kar installation works properly (see attached log), but in karaf
4.0.4 it seems instance is restarting and redeploy kar again which cause some
error (see attached log).
was:
Prerequisites:
```bash
feature:repo-add mvn:org.apache.cxf.karaf/apache-cxf/3.1.4/xml/features
feature:install pax-cdi war cxf eventadmin
```
In karaf 3.0.5 kar installation works properly (see attached log), but in karaf
4.0.4 it seems instance is restarting and redeploy kar again which cause some
error (see attached log).
> Installing kar causes karaf restart
> ---
>
> Key: KARAF-4310
> URL: https://issues.apache.org/jira/browse/KARAF-4310
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 4.0.4
> Environment: OpenSUSE Tumbleweed (4.4.0-2-default) oracle jdk 1.8.0_72
>Reporter: Michal Hlavac
> Attachments: karaf-3.0.5.log, karaf-4.0.4.log
>
>
> Prerequisites:
> {code}
> feature:repo-add mvn:org.apache.cxf.karaf/apache-cxf/3.1.4/xml/features
> feature:install pax-cdi war cxf eventadmin
> {code}
> In karaf 3.0.5 kar installation works properly (see attached log), but in
> karaf 4.0.4 it seems instance is restarting and redeploy kar again which
> cause some error (see attached log).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4310) Installing kar causes karaf restart
Michal Hlavac created KARAF-4310: Summary: Installing kar causes karaf restart Key: KARAF-4310 URL: https://issues.apache.org/jira/browse/KARAF-4310 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 4.0.4 Environment: OpenSUSE Tumbleweed (4.4.0-2-default) oracle jdk 1.8.0_72 Reporter: Michal Hlavac Prerequisites: ```bash feature:repo-add mvn:org.apache.cxf.karaf/apache-cxf/3.1.4/xml/features feature:install pax-cdi war cxf eventadmin ``` In karaf 3.0.5 kar installation works properly (see attached log), but in karaf 4.0.4 it seems instance is restarting and redeploy kar again which cause some error (see attached log). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4291) Add kafka appender
[ https://issues.apache.org/jira/browse/KARAF-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131099#comment-15131099 ] ASF subversion and git services commented on KARAF-4291: Commit f27337b55dd394338e53ba16630b8f8eced405bd in karaf-decanter's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=f27337b ] KARAF-4291 - Use marshaller service in kafka appender, gather all event in one kafka message > Add kafka appender > -- > > Key: KARAF-4291 > URL: https://issues.apache.org/jira/browse/KARAF-4291 > Project: Karaf > Issue Type: New Feature > Components: decanter >Affects Versions: decanter-1.0.1 >Reporter: Christian Schneider >Assignee: Jean-Baptiste Onofré > Fix For: decanter-1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4311) karaf maven plugin does not respect -s setting on maven
Raman Gupta created KARAF-4311: -- Summary: karaf maven plugin does not respect -s setting on maven Key: KARAF-4311 URL: https://issues.apache.org/jira/browse/KARAF-4311 Project: Karaf Issue Type: Bug Components: karaf-tooling Affects Versions: 4.0.4 Reporter: Raman Gupta The karaf maven plugin uses the pax maven resolver for some things, like verification for example. Pax has its own mechanism for finding the settings.xml, but mvn has the -s switch to specify a particular settings.xml at build time, which is often used by CI systems. The Karaf maven plugin should respect the settings provided by the -s switch when doing its internal maven resolution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4311) karaf maven plugin does not respect -s setting on maven
[ https://issues.apache.org/jira/browse/KARAF-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta updated KARAF-4311: --- Description: The karaf maven plugin uses the pax maven resolver for some things, like verification for example. However, mvn has the -s switch to specify a particular settings.xml at build time, which is often used by CI systems. Since the karaf-maven-plugin is running from a maven command, it should call or configure pax so that it uses the settings.xml specified by the user at the command line, if any. was: The karaf maven plugin uses the pax maven resolver for some things, like verification for example. Pax has its own mechanism for finding the settings.xml, but mvn has the -s switch to specify a particular settings.xml at build time, which is often used by CI systems. The Karaf maven plugin should respect the settings provided by the -s switch when doing its internal maven resolution. > karaf maven plugin does not respect -s setting on maven > --- > > Key: KARAF-4311 > URL: https://issues.apache.org/jira/browse/KARAF-4311 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.0.4 >Reporter: Raman Gupta > Labels: maven > > The karaf maven plugin uses the pax maven resolver for some things, like > verification for example. > However, mvn has the -s switch to specify a particular settings.xml at build > time, which is often used by CI systems. Since the karaf-maven-plugin is > running from a maven command, it should call or configure pax so that it uses > the settings.xml specified by the user at the command line, if any. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4105) karaf-assembly fails when used Maven versions do not match derived OSGi versions
[
https://issues.apache.org/jira/browse/KARAF-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4105:
Fix Version/s: 4.0.5
4.1.0
> karaf-assembly fails when used Maven versions do not match derived OSGi
> versions
>
>
> Key: KARAF-4105
> URL: https://issues.apache.org/jira/browse/KARAF-4105
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Affects Versions: 4.0.3
>Reporter: Oliver Lietz
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> e.g. {{$\{project.version\}}} {{0.1.1-SNAPSHOT}} and {{0.1.1.SNAPSHOT}} do
> not match in {{org.apache.karaf.profile.assembly.Builder}}
> See mail thread [\[K4.0.3\] custom distribution and
> kar|http://mail-archives.apache.org/mod_mbox/karaf-user/201511.mbox/%3c7781910.EKNrsAyV2X@madness%3e]
> for more.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4307) Archive Mojo does not set permissions properly in bin if usePathPrefix=false
[ https://issues.apache.org/jira/browse/KARAF-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130646#comment-15130646 ] Raman Gupta commented on KARAF-4307: Perhaps a better approach is to check the permissions of the files being tarred/zipped, and just pass the permissions on. The files in target/assembly already have the correct permissions so this should work. > Archive Mojo does not set permissions properly in bin if usePathPrefix=false > > > Key: KARAF-4307 > URL: https://issues.apache.org/jira/browse/KARAF-4307 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Reporter: Raman Gupta >Priority: Trivial > > The Karaf ArchiveMojo does not set executable permissions properly in bin if > usePathPrefix=false. > It is looking for "/bin/" but if usePathPrefix is false, it will only match > on "bin/". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4309) Missing dependency javax.transaction.TransactionManager with transaction feature and activemq-camel
David Croquette created KARAF-4309: -- Summary: Missing dependency javax.transaction.TransactionManager with transaction feature and activemq-camel Key: KARAF-4309 URL: https://issues.apache.org/jira/browse/KARAF-4309 Project: Karaf Issue Type: Bug Affects Versions: 4.0.4, 4.0.5 Reporter: David Croquette Installing features transaction and activemq-camel one at a time manually from console causes no problem. Installing them as dependent features either in a feature.xml or from console feature:repo-add activemq feature:repo-add camel feature:install transaction activemq-camel sets bundles in grace period: karaf@root()> diag Apache Aries Transaction Blueprint (58) --- Status: GracePeriod Blueprint 03/02/16 11:14 Missing dependencies: (objectClass=javax.transaction.TransactionManager) Apache Aries Transaction Blueprint (59) --- Status: GracePeriod Blueprint 03/02/16 11:14 Missing dependencies: (objectClass=javax.transaction.TransactionManager) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4303) Create decanter marshalling services
[ https://issues.apache.org/jira/browse/KARAF-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved KARAF-4303. Resolution: Fixed > Create decanter marshalling services > > > Key: KARAF-4303 > URL: https://issues.apache.org/jira/browse/KARAF-4303 > Project: Karaf > Issue Type: New Feature > Components: decanter >Affects Versions: decanter-1.0.1 >Reporter: Jean-Baptiste Onofré >Assignee: Christian Schneider > Fix For: decanter-1.0.2 > > > The decanter collectors collect the data as a key/value pair data (Map). > The decanter appenders directly uses this Map to store on the backend (it's > the case for Camel and ActiveMQ appenders), but other appenders marshall this > Map as a JSON string (it's the case of the Elasticsearch or JDBC appenders). > As a good design improvement, we can provide a DecanterMarshaller interface > that convert this Map as a Object. We can implement a first > JSONDecanterMarshaller service (we can imagine to provide new marshallers > later). The appenders can "filter" to pick the marshaller he wants to use or > just use one service (when multiple). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
