[jira] [Created] (KARAF-4356) Unable to uninstall feature that was not directly installed
Keith Wire created KARAF-4356:
-
Summary: Unable to uninstall feature that was not directly
installed
Key: KARAF-4356
URL: https://issues.apache.org/jira/browse/KARAF-4356
Project: Karaf
Issue Type: Bug
Components: karaf-feature
Affects Versions: 4.0.4
Reporter: Keith Wire
To reproduce do the following:
unzip apache-karaf-4.0.4
{code}
karaf@root()> feature:repo-add cxf 3.1.4
karaf@root()> feature:install cxf
karaf@root()> feature:uninstall cxf-transports-jms/3.1.4
{code}
The FeatureService will not attempt to uninstall `cxf-transports-jms` because
it is not in the requirements list. If that feature is installed directly
(which adds it to the requirements list), and then uninstalled, the bundles are
still not stopped. The only way to stop the bundles defined within a given
feature, is to install that feature directly, and no other features that refer
to it (ie don't install the root `cxf` feature)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4344) Migrate decanter to DS
[ https://issues.apache.org/jira/browse/KARAF-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158647#comment-15158647 ] ASF subversion and git services commented on KARAF-4344: Commit 31098cd7fc88ba2682e92c8315a08ca4213df862 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=31098cd ] [KARAF-4344] Migrating to DS using target feature > Migrate decanter to DS > -- > > Key: KARAF-4344 > URL: https://issues.apache.org/jira/browse/KARAF-4344 > Project: Karaf > Issue Type: Improvement > Components: decanter >Affects Versions: decanter-1.0.1 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: decanter-1.1.0 > > > Currently we are using osgi APIs to bind services and configuration. > This is becoming increasingly complicated and error prone. > For example for some of the decanter components we need two services and > multiple configurations (ManagedServiceFactory). This results in two stacked > service trackers and a ManagedServiceFactoryImpl. It is difficult to make > sure this code works correctly in all circumstances. > So I plan to switch to declarative services where all of the above can be > controlled by annoations. Additionally we can use the new type safe > configurations that make it a lot easier to work with the configuration both > as a user and as a developer of a component. > One important question is the minimum environment we want to support with > decanter 1.1.0. Older karaf versions do not support scr 2 (and DS spec 1.3) > which is needed for some interesting DS features like field injection and > type safe configs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4309) Missing dependency javax.transaction.TransactionManager with transaction feature and activemq-camel
[
https://issues.apache.org/jira/browse/KARAF-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158693#comment-15158693
]
Guillaume Nodet commented on KARAF-4309:
The problem is mainly caused because the {{javax.transaction}} packages are
provided by two different jars:
{{mvn:javax.transaction/javax.transaction-api/1.2}} and
{{mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/1.1.1}}.
I think it should work if you explicitly install {{transaction/1.3.0}} instead.
> 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] [Commented] (KARAF-4347) Define scr feature as featureBoot in standard distribution
[ https://issues.apache.org/jira/browse/KARAF-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158716#comment-15158716 ] Guillaume Nodet commented on KARAF-4347: I'm not really sure we should install more optional features by default. I'd rather go into the opposite direction and remove some optional features for 4.1 such as blueprint, etc... The reason is that when features should reference the SCR feature or extender and so those parts should be installed automatically. Another possible way to ease the user pain would be to define "default" optional features, i.e. some features which would be automatically installed "on demand". So blueprint and scr would not be installed by default, but if they are needed by a feature, they could be installed automatically. The danger would be to start making all features this way, which would then severely limit the amount of control the user has when actually installing features. > Define scr feature as featureBoot in standard distribution > -- > > Key: KARAF-4347 > URL: https://issues.apache.org/jira/browse/KARAF-4347 > Project: Karaf > Issue Type: Improvement > Components: karaf-core, karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.5 > > > As more and more people use DS/SCR, it's not always obvious to them that they > need to install the scr feature. As blueprint programming model is installed > by default, and regarding the very low overhead of scr feature, it would make > sense to install scr at boot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4357) OBR R5 Resources do not have Presentation Names
Stephen Kahmann created KARAF-4357: -- Summary: OBR R5 Resources do not have Presentation Names Key: KARAF-4357 URL: https://issues.apache.org/jira/browse/KARAF-4357 Project: Karaf Issue Type: Bug Affects Versions: 4.0.4 Reporter: Stephen Kahmann OBR R5 resources do not have Presentation Names so various OBR commands throw exceptions or present null to user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4357) OBR R5 Resources do not have Presentation Names
[ https://issues.apache.org/jira/browse/KARAF-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15160075#comment-15160075 ] Stephen Kahmann commented on KARAF-4357: PR here https://github.com/apache/karaf/pull/156 > OBR R5 Resources do not have Presentation Names > --- > > Key: KARAF-4357 > URL: https://issues.apache.org/jira/browse/KARAF-4357 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.4 >Reporter: Stephen Kahmann > > OBR R5 resources do not have Presentation Names so various OBR commands throw > exceptions or present null to user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4309) Missing dependency javax.transaction.TransactionManager with transaction feature and activemq-camel
[
https://issues.apache.org/jira/browse/KARAF-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158801#comment-15158801
]
David Croquette commented on KARAF-4309:
I can also see the problem with the java.transaction but when repeating this
issue in Karaf 4.0.4 it is transaction/1.3.0 that is installed.
{{karaf@root()> feature:list | grep transaction
transaction-api | 1.1.0| | Uninstalled |
enterprise-4.0.4 |
transaction-api | 1.2.0| | Uninstalled |
enterprise-4.0.4 |
transaction | 1.3.0| | Uninstalled |
enterprise-4.0.4 | OSGi Transaction Manager
feature:repo-add activemq
feature:repo-add camel
feature:install transaction activemq-camel
karaf@root()> feature:list | grep transaction
transaction-api | 1.1.0| | Started
| enterprise-4.0.4|
transaction-api | 1.2.0| | Started
| enterprise-4.0.4|
transaction | 1.3.0| x| Started
| enterprise-4.0.4| OSGi Transaction Manager}}
So that is unfortunately not the way around this issue.
> 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] [Comment Edited] (KARAF-4309) Missing dependency javax.transaction.TransactionManager with transaction feature and activemq-camel
[
https://issues.apache.org/jira/browse/KARAF-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158801#comment-15158801
]
David Croquette edited comment on KARAF-4309 at 2/23/16 12:40 PM:
--
I can also see the problem with the java.transaction but when repeating this
issue in Karaf 4.0.4 it is transaction/1.3.0 that is installed.
karaf@root()> feature:list | grep transaction
transaction-api | 1.1.0| | Uninstalled |
enterprise-4.0.4 |
transaction-api | 1.2.0| | Uninstalled |
enterprise-4.0.4 |
transaction | 1.3.0| | Uninstalled |
enterprise-4.0.4 | OSGi Transaction Manager
feature:repo-add activemq
feature:repo-add camel
feature:install transaction activemq-camel
karaf@root()> feature:list | grep transaction
transaction-api | 1.1.0| | Started
| enterprise-4.0.4|
transaction-api | 1.2.0| | Started
| enterprise-4.0.4|
transaction | 1.3.0| x| Started
| enterprise-4.0.4| OSGi Transaction Manager
So that is unfortunately not the way around this issue.
was (Author: croque):
I can also see the problem with the java.transaction but when repeating this
issue in Karaf 4.0.4 it is transaction/1.3.0 that is installed.
{{karaf@root()> feature:list | grep transaction
transaction-api | 1.1.0| | Uninstalled |
enterprise-4.0.4 |
transaction-api | 1.2.0| | Uninstalled |
enterprise-4.0.4 |
transaction | 1.3.0| | Uninstalled |
enterprise-4.0.4 | OSGi Transaction Manager
feature:repo-add activemq
feature:repo-add camel
feature:install transaction activemq-camel
karaf@root()> feature:list | grep transaction
transaction-api | 1.1.0| | Started
| enterprise-4.0.4|
transaction-api | 1.2.0| | Started
| enterprise-4.0.4|
transaction | 1.3.0| x| Started
| enterprise-4.0.4| OSGi Transaction Manager}}
So that is unfortunately not the way around this issue.
> 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] [Created] (KARAF-4355) suppress wrap without error
Benson Margulies created KARAF-4355: --- Summary: suppress wrap without error Key: KARAF-4355 URL: https://issues.apache.org/jira/browse/KARAF-4355 Project: Karaf Issue Type: New Feature Reporter: Benson Margulies We run into a lot of maven artifacts that contain OSGi metadata but have spurious non-OSGi dependencies. Generally, they are jars that somehow are incorporated into the artifact. As things are, we laboriously maintain export lists to avoid the wraps. We would be happy to just suppress 'wrapping', and take our lumps from missing packages if one of these things actually turns out to be necessary when we test it. If I don't see an unhappy comment on this, I'll make a PR for it. -- 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=15158982#comment-15158982
]
Guillaume Nodet commented on KARAF-4310:
Looking at the kar service, it may be interesting to change it so that all
features are installed in one go. This would be much more efficient (avoiding
recomputing everything at each step), with the drawback of not being able to
install only a subset of features if some can not be installed.
Anyway, it seems the framework is being shut down at some point, but I can't
get any reason from the log. Could you attach the kar you use to this issue ?
> 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)
