[jira] [Assigned] (KARAF-6047) can not install feature elasticsearch
[ https://issues.apache.org/jira/browse/KARAF-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-6047: --- Assignee: Jean-Baptiste Onofré > can not install feature elasticsearch > - > > Key: KARAF-6047 > URL: https://issues.apache.org/jira/browse/KARAF-6047 > Project: Karaf > Issue Type: Bug > Components: decanter >Affects Versions: decanter-2.1.0 >Reporter: sunlf >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: decanter-2.2.0 > > Attachments: image-2018-12-12-17-55-07-939.png > > > when i install feature elasticsearch under karaf 4.2.1, it can not install > properly. > Following is error : > > !image-2018-12-12-17-55-07-939.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5901) Create Aries JAXRS whiteboard example
[ https://issues.apache.org/jira/browse/KARAF-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719911#comment-16719911 ] ASF GitHub Bot commented on KARAF-5901: --- jbonofre opened a new pull request #697: [KARAF-5901] Bootstrap Aries JAXRS Whiteboard example URL: https://github.com/apache/karaf/pull/697 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Create Aries JAXRS whiteboard example > - > > Key: KARAF-5901 > URL: https://issues.apache.org/jira/browse/KARAF-5901 > Project: Karaf > Issue Type: Task > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Labels: example > Fix For: 4.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6047) can not install feature elasticsearch
[ https://issues.apache.org/jira/browse/KARAF-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-6047: Fix Version/s: (was: decanter-2.1.0) decanter-2.2.0 > can not install feature elasticsearch > - > > Key: KARAF-6047 > URL: https://issues.apache.org/jira/browse/KARAF-6047 > Project: Karaf > Issue Type: Bug > Components: decanter >Affects Versions: decanter-2.1.0 >Reporter: sunlf >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: decanter-2.2.0 > > Attachments: image-2018-12-12-17-55-07-939.png > > > when i install feature elasticsearch under karaf 4.2.1, it can not install > properly. > Following is error : > > !image-2018-12-12-17-55-07-939.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6048) Camel Test case prone to endless loop
Martin Krüger created KARAF-6048:
Summary: Camel Test case prone to endless loop
Key: KARAF-6048
URL: https://issues.apache.org/jira/browse/KARAF-6048
Project: Karaf
Issue Type: Bug
Components: karaf
Reporter: Martin Krüger
During my build the test case CamelExampleTest.testBlueprintDSL() ended up in
an endless loop.
The problem is {code}
while (true) {
if (!output.contains("Started")) {
Thread.sleep(500);
output = executeCommand("camel:route-list");
} else {
break;
}
}{code} in the verify method. This loop has to contain an exit path
with a failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-6048) Camel Test case prone to endless loop
[
https://issues.apache.org/jira/browse/KARAF-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Krüger updated KARAF-6048:
-
Fix Version/s: 4.2.2
> Camel Test case prone to endless loop
> -
>
> Key: KARAF-6048
> URL: https://issues.apache.org/jira/browse/KARAF-6048
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Martin Krüger
>Priority: Major
> Fix For: 4.2.2
>
>
> During my build the test case CamelExampleTest.testBlueprintDSL() ended up in
> an endless loop.
> The problem is {code}
> while (true) {
> if (!output.contains("Started")) {
> Thread.sleep(500);
> output = executeCommand("camel:route-list");
> } else {
> break;
> }
> }{code} in the verify method. This loop has to contain an exit path
> with a failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KARAF-6048) Camel Test case prone to endless loop
[
https://issues.apache.org/jira/browse/KARAF-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720180#comment-16720180
]
Martin Krüger edited comment on KARAF-6048 at 12/13/18 1:42 PM:
The patch just shortens the wile loop. The issue is not fixed. The endless loop
is still present.
A better way would be
{code}
String output = "";
for (int loopCounter = 0; loopCounter < 20; loopCounter++) {
output = executeCommand("camel:route-list");
if (output.contains("Started")) {
break;
}
Thread.sleep(500);
}
if (!output.contains("Started")) {
fail();
}
{code}
was (Author: martin.krueger):
The patch just shortens the wile loop. The issue is not fixed. The endless loop
is still present.
A better way would be
{code}
String output = "";
for (int loopCounter = 0; loopCounter < 20; loopCounter++) {
output = executeCommand("camel:route-list");
if (output.contains("Started")) {
break;
}
Thread.sleep(500);
}
if (!output.contains("Started")) {
fail();
}
{code}
> Camel Test case prone to endless loop
> -
>
> Key: KARAF-6048
> URL: https://issues.apache.org/jira/browse/KARAF-6048
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Martin Krüger
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2
>
>
> During my build the test case CamelExampleTest.testBlueprintDSL() ended up in
> an endless loop.
> The problem is {code}
> while (true) {
> if (!output.contains("Started")) {
> Thread.sleep(500);
> output = executeCommand("camel:route-list");
> } else {
> break;
> }
> }{code} in the verify method. This loop has to contain an exit path
> with a failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-6048) Camel Test case prone to endless loop
[
https://issues.apache.org/jira/browse/KARAF-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-6048.
-
Resolution: Fixed
> Camel Test case prone to endless loop
> -
>
> Key: KARAF-6048
> URL: https://issues.apache.org/jira/browse/KARAF-6048
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Martin Krüger
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2
>
>
> During my build the test case CamelExampleTest.testBlueprintDSL() ended up in
> an endless loop.
> The problem is {code}
> while (true) {
> if (!output.contains("Started")) {
> Thread.sleep(500);
> output = executeCommand("camel:route-list");
> } else {
> break;
> }
> }{code} in the verify method. This loop has to contain an exit path
> with a failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6048) Camel Test case prone to endless loop
[
https://issues.apache.org/jira/browse/KARAF-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720143#comment-16720143
]
ASF subversion and git services commented on KARAF-6048:
Commit b2e5c3d5133e8dc0107b38dae0e90fc331448da7 in karaf's branch
refs/heads/master from [~j...@nanthrax.net]
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=b2e5c3d ]
[KARAF-6048] Change waiting loop in CamelExampleTest
> Camel Test case prone to endless loop
> -
>
> Key: KARAF-6048
> URL: https://issues.apache.org/jira/browse/KARAF-6048
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Martin Krüger
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2
>
>
> During my build the test case CamelExampleTest.testBlueprintDSL() ended up in
> an endless loop.
> The problem is {code}
> while (true) {
> if (!output.contains("Started")) {
> Thread.sleep(500);
> output = executeCommand("camel:route-list");
> } else {
> break;
> }
> }{code} in the verify method. This loop has to contain an exit path
> with a failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KARAF-6048) Camel Test case prone to endless loop
[
https://issues.apache.org/jira/browse/KARAF-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720180#comment-16720180
]
Martin Krüger edited comment on KARAF-6048 at 12/13/18 1:42 PM:
The patch just shortens the wile loop. The issue is not fixed. The endless loop
is still present.
A better way would be
{code}
String output = "";
for (int loopCounter = 0; loopCounter < 20; loopCounter++) {
output = executeCommand("camel:route-list");
if (output.contains("Started")) {
break;
}
Thread.sleep(500);
}
if (!output.contains("Started")) {
fail();
}
{code}
was (Author: martin.krueger):
The patch just shortens the wile loop. The issue is not fixed. The endless loop
is still present.
A better way would be
{code}
String output = "";
for (int loopCounter = 0; loopCounter < 20; loopCounter++) {
output = executeCommand("camel:route-list");
if (output.contains("Started")) {
break;
}
Thread.sleep(500);
}
assertEquals("Started", output);
{code}
> Camel Test case prone to endless loop
> -
>
> Key: KARAF-6048
> URL: https://issues.apache.org/jira/browse/KARAF-6048
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Martin Krüger
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2
>
>
> During my build the test case CamelExampleTest.testBlueprintDSL() ended up in
> an endless loop.
> The problem is {code}
> while (true) {
> if (!output.contains("Started")) {
> Thread.sleep(500);
> output = executeCommand("camel:route-list");
> } else {
> break;
> }
> }{code} in the verify method. This loop has to contain an exit path
> with a failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KARAF-6048) Camel Test case prone to endless loop
[
https://issues.apache.org/jira/browse/KARAF-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-6048:
---
Assignee: Jean-Baptiste Onofré
> Camel Test case prone to endless loop
> -
>
> Key: KARAF-6048
> URL: https://issues.apache.org/jira/browse/KARAF-6048
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Martin Krüger
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2
>
>
> During my build the test case CamelExampleTest.testBlueprintDSL() ended up in
> an endless loop.
> The problem is {code}
> while (true) {
> if (!output.contains("Started")) {
> Thread.sleep(500);
> output = executeCommand("camel:route-list");
> } else {
> break;
> }
> }{code} in the verify method. This loop has to contain an exit path
> with a failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (KARAF-6048) Camel Test case prone to endless loop
[
https://issues.apache.org/jira/browse/KARAF-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Krüger reopened KARAF-6048:
--
The patch just shortens the wile loop. The issue is not fixed. The endless loop
is still present.
A better way would be
{code}
String output = "";
for (int loopCounter = 0; loopCounter < 20; loopCounter++) {
output = executeCommand("camel:route-list");
if (output.contains("Started")) {
break;
}
Thread.sleep(500);
}
assertEquals("Started", output);
{code}
> Camel Test case prone to endless loop
> -
>
> Key: KARAF-6048
> URL: https://issues.apache.org/jira/browse/KARAF-6048
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Martin Krüger
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2
>
>
> During my build the test case CamelExampleTest.testBlueprintDSL() ended up in
> an endless loop.
> The problem is {code}
> while (true) {
> if (!output.contains("Started")) {
> Thread.sleep(500);
> output = executeCommand("camel:route-list");
> } else {
> break;
> }
> }{code} in the verify method. This loop has to contain an exit path
> with a failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-5873) Add spring-security 5.0.7.RELEASE feature
[ https://issues.apache.org/jira/browse/KARAF-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5873: Fix Version/s: (was: 4.2.2) 4.2.3 > Add spring-security 5.0.7.RELEASE feature > - > > Key: KARAF-5873 > URL: https://issues.apache.org/jira/browse/KARAF-5873 > Project: Karaf > Issue Type: New Feature > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5469) Installation of a non blueprint feature triggers the installation of the blueprint compatibility bundle
[
https://issues.apache.org/jira/browse/KARAF-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-5469:
Fix Version/s: 4.1.8
4.2.2
> Installation of a non blueprint feature triggers the installation of the
> blueprint compatibility bundle
> ---
>
> Key: KARAF-5469
> URL: https://issues.apache.org/jira/browse/KARAF-5469
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.1.3
>Reporter: Joao Assuncao
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2, 4.1.8
>
> Attachments: wiring.txt
>
>
> In Karaf 4.1.3 when installing some custom made features karaf triggers the
> installation of the org.apache.aries.blueprint.core.compatibility bundle
> causing a refresh of all bundles and a Karaf shutdown.
> None of the bundles in the feature uses blueprint and the more exotic thing
> is that one of the bundles uses a Contional-Package instruction.
> The feature I'm trying to install:
> {code}
> karaf@root()> feature:info paybox-io-modbus
> Feature paybox-io-modbus 0.1.0.SNAPSHOT
> Description:
> Modbus I/O implementation
> Feature has no configuration
> Feature has no configuration files
> Feature has no dependencies.
> Feature contains followed bundles:
> mvn:pt.brisa.common/common-service-core/1.3.0
> mvn:pt.brisa.paybox/io-api/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-modbus/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-commands/0.1.0-SNAPSHOT
> Feature has no conditionals.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6047) can not install feature elasticsearch
[ https://issues.apache.org/jira/browse/KARAF-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720278#comment-16720278 ] Jean-Baptiste Onofré commented on KARAF-6047: - That's an issue in the ServiceMix Elasticsearch bundle. I'm thinking that. > can not install feature elasticsearch > - > > Key: KARAF-6047 > URL: https://issues.apache.org/jira/browse/KARAF-6047 > Project: Karaf > Issue Type: Bug > Components: decanter >Affects Versions: decanter-2.1.0 >Reporter: sunlf >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: decanter-2.2.0 > > Attachments: image-2018-12-12-17-55-07-939.png > > > when i install feature elasticsearch under karaf 4.2.1, it can not install > properly. > Following is error : > > !image-2018-12-12-17-55-07-939.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5469) Installation of a non blueprint feature triggers the installation of the blueprint compatibility bundle
[
https://issues.apache.org/jira/browse/KARAF-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720271#comment-16720271
]
Martin Lichtin commented on KARAF-5469:
---
Running into the same issue and the cause is [~gnt]'s change to load the
fragment bundle with dependency=true. Without dependency=true, the fragment is
attached to the host bundle rightaway and no refresh will happen later on.
> Installation of a non blueprint feature triggers the installation of the
> blueprint compatibility bundle
> ---
>
> Key: KARAF-5469
> URL: https://issues.apache.org/jira/browse/KARAF-5469
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.1.3
>Reporter: Joao Assuncao
>Priority: Major
> Attachments: wiring.txt
>
>
> In Karaf 4.1.3 when installing some custom made features karaf triggers the
> installation of the org.apache.aries.blueprint.core.compatibility bundle
> causing a refresh of all bundles and a Karaf shutdown.
> None of the bundles in the feature uses blueprint and the more exotic thing
> is that one of the bundles uses a Contional-Package instruction.
> The feature I'm trying to install:
> {code}
> karaf@root()> feature:info paybox-io-modbus
> Feature paybox-io-modbus 0.1.0.SNAPSHOT
> Description:
> Modbus I/O implementation
> Feature has no configuration
> Feature has no configuration files
> Feature has no dependencies.
> Feature contains followed bundles:
> mvn:pt.brisa.common/common-service-core/1.3.0
> mvn:pt.brisa.paybox/io-api/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-modbus/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-commands/0.1.0-SNAPSHOT
> Feature has no conditionals.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5469) Installation of a non blueprint feature triggers the installation of the blueprint compatibility bundle
[
https://issues.apache.org/jira/browse/KARAF-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720280#comment-16720280
]
Jean-Baptiste Onofré commented on KARAF-5469:
-
I'm fixing. Sorry about that.
> Installation of a non blueprint feature triggers the installation of the
> blueprint compatibility bundle
> ---
>
> Key: KARAF-5469
> URL: https://issues.apache.org/jira/browse/KARAF-5469
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.1.3
>Reporter: Joao Assuncao
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2, 4.1.8
>
> Attachments: wiring.txt
>
>
> In Karaf 4.1.3 when installing some custom made features karaf triggers the
> installation of the org.apache.aries.blueprint.core.compatibility bundle
> causing a refresh of all bundles and a Karaf shutdown.
> None of the bundles in the feature uses blueprint and the more exotic thing
> is that one of the bundles uses a Contional-Package instruction.
> The feature I'm trying to install:
> {code}
> karaf@root()> feature:info paybox-io-modbus
> Feature paybox-io-modbus 0.1.0.SNAPSHOT
> Description:
> Modbus I/O implementation
> Feature has no configuration
> Feature has no configuration files
> Feature has no dependencies.
> Feature contains followed bundles:
> mvn:pt.brisa.common/common-service-core/1.3.0
> mvn:pt.brisa.paybox/io-api/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-modbus/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-commands/0.1.0-SNAPSHOT
> Feature has no conditionals.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KARAF-5469) Installation of a non blueprint feature triggers the installation of the blueprint compatibility bundle
[
https://issues.apache.org/jira/browse/KARAF-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-5469:
---
Assignee: Jean-Baptiste Onofré
> Installation of a non blueprint feature triggers the installation of the
> blueprint compatibility bundle
> ---
>
> Key: KARAF-5469
> URL: https://issues.apache.org/jira/browse/KARAF-5469
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.1.3
>Reporter: Joao Assuncao
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2, 4.1.8
>
> Attachments: wiring.txt
>
>
> In Karaf 4.1.3 when installing some custom made features karaf triggers the
> installation of the org.apache.aries.blueprint.core.compatibility bundle
> causing a refresh of all bundles and a Karaf shutdown.
> None of the bundles in the feature uses blueprint and the more exotic thing
> is that one of the bundles uses a Contional-Package instruction.
> The feature I'm trying to install:
> {code}
> karaf@root()> feature:info paybox-io-modbus
> Feature paybox-io-modbus 0.1.0.SNAPSHOT
> Description:
> Modbus I/O implementation
> Feature has no configuration
> Feature has no configuration files
> Feature has no dependencies.
> Feature contains followed bundles:
> mvn:pt.brisa.common/common-service-core/1.3.0
> mvn:pt.brisa.paybox/io-api/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-modbus/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-commands/0.1.0-SNAPSHOT
> Feature has no conditionals.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6003) IllegalStateException: Need active coordination - cannot use JPA and Jasypt
[
https://issues.apache.org/jira/browse/KARAF-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721003#comment-16721003
]
ASF GitHub Bot commented on KARAF-6003:
---
jbonofre opened a new pull request #700: [KARAF-6003] Upgrade to Aries
Blueprint Web 1.1.1
URL: https://github.com/apache/karaf/pull/700
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> IllegalStateException: Need active coordination - cannot use JPA and Jasypt
> ---
>
> Key: KARAF-6003
> URL: https://issues.apache.org/jira/browse/KARAF-6003
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Marek Łuniewski
>Assignee: Jean-Baptiste Onofré
>Priority: Blocker
> Fix For: 4.2.2
>
>
> In version 4.2.1 one cannot use JPA because it causes
> java.lang.IllegalStateException: Need active coordination. After my
> investigation I have found that it is caused because proxy service is not
> created properly. When someone use JPA in the same bundle, as in Karaf tests,
> it works fine. But problem occurs when using osgi service and osgi reference.
> Downgrading to version 4.1.5 of Karaf results in no possibility of using
> Jasypt (to protect passwords) [using:
> org.jasypt.encryption.pbe.StandardPBEStringEncryptor]. It does not decrypt
> passwords having marks ENC(...).
> I found that upgrading Blueprint fixes problem, so that JPA and Jasypt works
> perfectly. I know that sometime ago ticket on Camel blocked Blueprint
> upgrade. It was: https://issues.apache.org/jira/browse/CAMEL-12570. Currently
> this ticket is closed.
> Patch (for current code, which is version 4.2.1) is:
> {code:java}
> diff --git a/pom.xml b/pom.xml
> index 3d314da48c..f049b7ff86 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -218,10 +218,11 @@
> 1.0.0
>
> 1.0.0
> 1.0.1
> - 1.9.0
> + 1.10.0
>
> 1.0.0
> - 1.2.0
> - 1.0.1
> + 1.3.0
> + 1.1.1
> +
> 1.0.1
>
> 0.6.0
>
> 0.4.0
> 1.1.5
> {code}
> and
> {code:java}
> diff --git a/assemblies/features/standard/src/main/feature/feature.xml
> b/assemblies/features/standard/src/main/feature/feature.xml
> index d19b87eb00..1813b2a0a5 100644
> --- a/assemblies/features/standard/src/main/feature/feature.xml
> +++ b/assemblies/features/standard/src/main/feature/feature.xml
> @@ -1429,7 +1429,7 @@ org.apache.felix.eventadmin.AddSubject=true
> blueprint inside web-bundle containers" version="${project.version}">
> war
> aries-blueprint
> -
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.web.version}
> +
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.webosgi.version}
>
>
> version="${pax.url.version}">
> {code}
> Hope it helps.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-6048) Camel Test case prone to endless loop
[
https://issues.apache.org/jira/browse/KARAF-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-6048.
-
Resolution: Fixed
> Camel Test case prone to endless loop
> -
>
> Key: KARAF-6048
> URL: https://issues.apache.org/jira/browse/KARAF-6048
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Martin Krüger
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2
>
>
> During my build the test case CamelExampleTest.testBlueprintDSL() ended up in
> an endless loop.
> The problem is {code}
> while (true) {
> if (!output.contains("Started")) {
> Thread.sleep(500);
> output = executeCommand("camel:route-list");
> } else {
> break;
> }
> }{code} in the verify method. This loop has to contain an exit path
> with a failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6048) Camel Test case prone to endless loop
[
https://issues.apache.org/jira/browse/KARAF-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721007#comment-16721007
]
Martin Krüger commented on KARAF-6048:
--
[~jbonofre]: Yes. The timeout solution is way better.
> Camel Test case prone to endless loop
> -
>
> Key: KARAF-6048
> URL: https://issues.apache.org/jira/browse/KARAF-6048
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Martin Krüger
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2
>
>
> During my build the test case CamelExampleTest.testBlueprintDSL() ended up in
> an endless loop.
> The problem is {code}
> while (true) {
> if (!output.contains("Started")) {
> Thread.sleep(500);
> output = executeCommand("camel:route-list");
> } else {
> break;
> }
> }{code} in the verify method. This loop has to contain an exit path
> with a failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-6045) Upgrade to Pax Web 7.2.5
[ https://issues.apache.org/jira/browse/KARAF-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-6045. - Resolution: Fixed > Upgrade to Pax Web 7.2.5 > > > Key: KARAF-6045 > URL: https://issues.apache.org/jira/browse/KARAF-6045 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.2 > > > I'm working Pax Web 7.2.5, especially with contract capability in > pax-web-runtime instead of features (allowing to work with Aries JAXRS > Whiteboard for instance). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6045) Upgrade to Pax Web 7.2.5
[ https://issues.apache.org/jira/browse/KARAF-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721018#comment-16721018 ] ASF GitHub Bot commented on KARAF-6045: --- jbonofre closed pull request #698: [KARAF-6045] Upgrade to Pax Web 7.2.5 URL: https://github.com/apache/karaf/pull/698 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/pom.xml b/pom.xml index 8d9604d95f..eaf0734968 100644 --- a/pom.xml +++ b/pom.xml @@ -281,7 +281,7 @@ 1.5.0 1.8.3 2.5.4 -7.2.4 +7.2.5 3.0.0 1.3.1 1.0.2 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to Pax Web 7.2.5 > > > Key: KARAF-6045 > URL: https://issues.apache.org/jira/browse/KARAF-6045 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.2 > > > I'm working Pax Web 7.2.5, especially with contract capability in > pax-web-runtime instead of features (allowing to work with Aries JAXRS > Whiteboard for instance). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5854) KAR file installation is not atomic
[ https://issues.apache.org/jira/browse/KARAF-5854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720988#comment-16720988 ] Jean-Baptiste Onofré commented on KARAF-5854: - If the exception is uncatched, I don't see an obvious way to handle this. > KAR file installation is not atomic > --- > > Key: KARAF-5854 > URL: https://issues.apache.org/jira/browse/KARAF-5854 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.1.4 >Reporter: Lars Ollén >Assignee: Jean-Baptiste Onofré >Priority: Major > Labels: kar > Fix For: 4.1.8, 4.2.3 > > > The KAR file installation process isn't atomic and handles exceptions poorly. > If a shutdown signal is sent to Karaf while the KAR file is being installed > the KAR file can be unpacked to the data folder but the rest of the > installation steps will fail, leaving an uninstalled KAR file unpacked. That > will hinder the KAR file from being installed during the next startup of > Karaf (since Karaf checks only if the KAR file is unpacked and not if it was > installed). > My initial though was that: > '_org.apache.karaf.kar.internal.KarServiceImpl#install(java.net.URI, > java.io.File, java.io.File, boolean)_' should rollback and delete the kar > folder in case the methods such as > 'org.apache.karaf.kar.internal.KarServiceImpl#addToFeaturesRepositories' gets > and exception, not sure how that would fit into the Karaf philosophy. > > Below are the exceptions that we see (a bit redacted though): > 2018-07-05T12:17:07.223+0200 | WARN | XX | > o.a.karaf.kar.internal.KarServiceImpl | 51 - org.apache.karaf.kar.core - > 4.1.4 | Unable to add repository 'mvn:/xml/features' > java.lang.IllegalStateException: BundleContext is no longer valid > at > org.eclipse.osgi.internal.framework.BundleContextImpl.checkValid(BundleContextImpl.java:989) > at > org.eclipse.osgi.internal.framework.BundleContextImpl.getDataFile(BundleContextImpl.java:694) > at > org.apache.karaf.features.internal.osgi.Activator$1.getOutputStream(Activator.java:205) > at > org.apache.karaf.features.internal.service.StateStorage.save(StateStorage.java:56) > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.saveState(FeaturesServiceImpl.java:360) > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:505) > at > org.apache.karaf.kar.internal.KarServiceImpl.addToFeaturesRepositories(KarServiceImpl.java:266) > at > org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:111) > at > org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:95) > at > org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:87) > at > org.apache.karaf.deployer.kar.KarArtifactInstaller.install(KarArtifactInstaller.java:50) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:950) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:884) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:489) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) > 2018-07-05T12:17:07.226+0200 | WARN | XXX | > o.a.karaf.kar.internal.KarServiceImpl | 51 - org.apache.karaf.kar.core - > 4.1.4 | Unable to install Kar feature X > java.util.concurrent.RejectedExecutionException: Task > java.util.concurrent.FutureTask@5222a1f2 rejected from > java.util.concurrent.ThreadPoolExecutor@36cfb96[Terminated, pool size = 0, > active threads = 0, queued tasks = 0, completed tasks = 1] > at > java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063) > at > java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830) > at > java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379) > at > java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) > at > java.util.concurrent.Executors$DelegatedExecutorService.submit(Executors.java:681) > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvisionInThread(FeaturesServiceImpl.java:1146) > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:1022) > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:915) > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:900) > at >
[jira] [Updated] (KARAF-5854) KAR file installation is not atomic
[ https://issues.apache.org/jira/browse/KARAF-5854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5854: Fix Version/s: (was: 4.2.2) 4.2.3 > KAR file installation is not atomic > --- > > Key: KARAF-5854 > URL: https://issues.apache.org/jira/browse/KARAF-5854 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.1.4 >Reporter: Lars Ollén >Assignee: Jean-Baptiste Onofré >Priority: Major > Labels: kar > Fix For: 4.1.8, 4.2.3 > > > The KAR file installation process isn't atomic and handles exceptions poorly. > If a shutdown signal is sent to Karaf while the KAR file is being installed > the KAR file can be unpacked to the data folder but the rest of the > installation steps will fail, leaving an uninstalled KAR file unpacked. That > will hinder the KAR file from being installed during the next startup of > Karaf (since Karaf checks only if the KAR file is unpacked and not if it was > installed). > My initial though was that: > '_org.apache.karaf.kar.internal.KarServiceImpl#install(java.net.URI, > java.io.File, java.io.File, boolean)_' should rollback and delete the kar > folder in case the methods such as > 'org.apache.karaf.kar.internal.KarServiceImpl#addToFeaturesRepositories' gets > and exception, not sure how that would fit into the Karaf philosophy. > > Below are the exceptions that we see (a bit redacted though): > 2018-07-05T12:17:07.223+0200 | WARN | XX | > o.a.karaf.kar.internal.KarServiceImpl | 51 - org.apache.karaf.kar.core - > 4.1.4 | Unable to add repository 'mvn:/xml/features' > java.lang.IllegalStateException: BundleContext is no longer valid > at > org.eclipse.osgi.internal.framework.BundleContextImpl.checkValid(BundleContextImpl.java:989) > at > org.eclipse.osgi.internal.framework.BundleContextImpl.getDataFile(BundleContextImpl.java:694) > at > org.apache.karaf.features.internal.osgi.Activator$1.getOutputStream(Activator.java:205) > at > org.apache.karaf.features.internal.service.StateStorage.save(StateStorage.java:56) > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.saveState(FeaturesServiceImpl.java:360) > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:505) > at > org.apache.karaf.kar.internal.KarServiceImpl.addToFeaturesRepositories(KarServiceImpl.java:266) > at > org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:111) > at > org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:95) > at > org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:87) > at > org.apache.karaf.deployer.kar.KarArtifactInstaller.install(KarArtifactInstaller.java:50) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:950) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:884) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:489) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) > 2018-07-05T12:17:07.226+0200 | WARN | XXX | > o.a.karaf.kar.internal.KarServiceImpl | 51 - org.apache.karaf.kar.core - > 4.1.4 | Unable to install Kar feature X > java.util.concurrent.RejectedExecutionException: Task > java.util.concurrent.FutureTask@5222a1f2 rejected from > java.util.concurrent.ThreadPoolExecutor@36cfb96[Terminated, pool size = 0, > active threads = 0, queued tasks = 0, completed tasks = 1] > at > java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063) > at > java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830) > at > java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379) > at > java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) > at > java.util.concurrent.Executors$DelegatedExecutorService.submit(Executors.java:681) > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvisionInThread(FeaturesServiceImpl.java:1146) > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:1022) > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:915) > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:900) > at >
[jira] [Commented] (KARAF-6048) Camel Test case prone to endless loop
[
https://issues.apache.org/jira/browse/KARAF-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720935#comment-16720935
]
Jean-Baptiste Onofré commented on KARAF-6048:
-
No need, timeout on {{@Test}} is better. I thought I already did that.
> Camel Test case prone to endless loop
> -
>
> Key: KARAF-6048
> URL: https://issues.apache.org/jira/browse/KARAF-6048
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Martin Krüger
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2
>
>
> During my build the test case CamelExampleTest.testBlueprintDSL() ended up in
> an endless loop.
> The problem is {code}
> while (true) {
> if (!output.contains("Started")) {
> Thread.sleep(500);
> output = executeCommand("camel:route-list");
> } else {
> break;
> }
> }{code} in the verify method. This loop has to contain an exit path
> with a failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6045) Upgrade to Pax Web 7.2.5
[ https://issues.apache.org/jira/browse/KARAF-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721021#comment-16721021 ] ASF subversion and git services commented on KARAF-6045: Commit 158b3a435db98de3a875e336134a16338409c260 in karaf's branch refs/heads/master from [~j...@nanthrax.net] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=158b3a4 ] Merge pull request #698 from jbonofre/KARAF-6045 [KARAF-6045] Upgrade to Pax Web 7.2.5 > Upgrade to Pax Web 7.2.5 > > > Key: KARAF-6045 > URL: https://issues.apache.org/jira/browse/KARAF-6045 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.2 > > > I'm working Pax Web 7.2.5, especially with contract capability in > pax-web-runtime instead of features (allowing to work with Aries JAXRS > Whiteboard for instance). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6045) Upgrade to Pax Web 7.2.5
[ https://issues.apache.org/jira/browse/KARAF-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721020#comment-16721020 ] ASF subversion and git services commented on KARAF-6045: Commit 158b3a435db98de3a875e336134a16338409c260 in karaf's branch refs/heads/master from [~j...@nanthrax.net] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=158b3a4 ] Merge pull request #698 from jbonofre/KARAF-6045 [KARAF-6045] Upgrade to Pax Web 7.2.5 > Upgrade to Pax Web 7.2.5 > > > Key: KARAF-6045 > URL: https://issues.apache.org/jira/browse/KARAF-6045 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.2 > > > I'm working Pax Web 7.2.5, especially with contract capability in > pax-web-runtime instead of features (allowing to work with Aries JAXRS > Whiteboard for instance). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6045) Upgrade to Pax Web 7.2.5
[ https://issues.apache.org/jira/browse/KARAF-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721019#comment-16721019 ] ASF subversion and git services commented on KARAF-6045: Commit 63232ab2b4641e252b841440b22adb6686401d4c in karaf's branch refs/heads/master from [~j...@nanthrax.net] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=63232ab ] [KARAF-6045] Upgrade to Pax Web 7.2.5 > Upgrade to Pax Web 7.2.5 > > > Key: KARAF-6045 > URL: https://issues.apache.org/jira/browse/KARAF-6045 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.2 > > > I'm working Pax Web 7.2.5, especially with contract capability in > pax-web-runtime instead of features (allowing to work with Aries JAXRS > Whiteboard for instance). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6045) Upgrade to Pax Web 7.2.5
[ https://issues.apache.org/jira/browse/KARAF-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720934#comment-16720934 ] ASF GitHub Bot commented on KARAF-6045: --- jbonofre opened a new pull request #698: [KARAF-6045] Upgrade to Pax Web 7.2.5 URL: https://github.com/apache/karaf/pull/698 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to Pax Web 7.2.5 > > > Key: KARAF-6045 > URL: https://issues.apache.org/jira/browse/KARAF-6045 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.2 > > > I'm working Pax Web 7.2.5, especially with contract capability in > pax-web-runtime instead of features (allowing to work with Aries JAXRS > Whiteboard for instance). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5469) Installation of a non blueprint feature triggers the installation of the blueprint compatibility bundle
[
https://issues.apache.org/jira/browse/KARAF-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720983#comment-16720983
]
ASF GitHub Bot commented on KARAF-5469:
---
jbonofre opened a new pull request #699: [KARAF-5469] Remove dependency flag
from aries blueprint compatability bundle
URL: https://github.com/apache/karaf/pull/699
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Installation of a non blueprint feature triggers the installation of the
> blueprint compatibility bundle
> ---
>
> Key: KARAF-5469
> URL: https://issues.apache.org/jira/browse/KARAF-5469
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.1.3
>Reporter: Joao Assuncao
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2, 4.1.8
>
> Attachments: wiring.txt
>
>
> In Karaf 4.1.3 when installing some custom made features karaf triggers the
> installation of the org.apache.aries.blueprint.core.compatibility bundle
> causing a refresh of all bundles and a Karaf shutdown.
> None of the bundles in the feature uses blueprint and the more exotic thing
> is that one of the bundles uses a Contional-Package instruction.
> The feature I'm trying to install:
> {code}
> karaf@root()> feature:info paybox-io-modbus
> Feature paybox-io-modbus 0.1.0.SNAPSHOT
> Description:
> Modbus I/O implementation
> Feature has no configuration
> Feature has no configuration files
> Feature has no dependencies.
> Feature contains followed bundles:
> mvn:pt.brisa.common/common-service-core/1.3.0
> mvn:pt.brisa.paybox/io-api/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-modbus/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-commands/0.1.0-SNAPSHOT
> Feature has no conditionals.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
