[jira] [Assigned] (KARAF-4564) Can't start karaf using symbolic link
[ https://issues.apache.org/jira/browse/KARAF-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-4564: --- Assignee: Jean-Baptiste Onofré > Can't start karaf using symbolic link > -- > > Key: KARAF-4564 > URL: https://issues.apache.org/jira/browse/KARAF-4564 > Project: Karaf > Issue Type: Bug >Affects Versions: 3.0.6 > Environment: Ubuntu (Linux vagrant 3.19.0-25-generic > #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 > GNU/Linux) > OSX (Darwin inocybe.local 14.5.0 Darwin Kernel Version 14.5.0: Tue Sep 1 > 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64) > Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc) >Reporter: Alexis de Talhouët >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.7, 4.0.6 > > > When using a symbolic link to use the scripts defined here: > https://github.com/apache/karaf/tree/karaf-3.0.6/assemblies/features/framework/src/main/filtered-resources/resources/bin > e.g. karaf or client and so on, it's failing to start the container and show > this error: > Error: Could not find or load main class org.apache.karaf.main.Main > This issue is related to the DIRNAME variable and the way it is setup. > This bug has been found in OpenDaylight, here is the ticket with more > information https://bugs.opendaylight.org/show_bug.cgi?id=6027 > I have also propose a candidate fix in ODL: > https://git.opendaylight.org/gerrit/#/c/39982/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4566) "karaf" script invokes /bin/sh but requires /bin/bash functions
[ https://issues.apache.org/jira/browse/KARAF-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-4566: --- Assignee: Jean-Baptiste Onofré > "karaf" script invokes /bin/sh but requires /bin/bash functions > > > Key: KARAF-4566 > URL: https://issues.apache.org/jira/browse/KARAF-4566 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.6 > Environment: Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc) >Reporter: Alexis de Talhouët >Assignee: Jean-Baptiste Onofré > > The bin/karaf script uses the "local" command which is a shell builtin of > bash and similar shells, but is not required for POSIX-compliance in sh. When > I attempt to run karaf on a Solaris system, I see the following output: > root@solaris:/opendaylight/bin# ./karaf > ./karaf[172]: local: not found [No such file or directory] > ./karaf[182]: local: not found [No such file or directory] > ./karaf[183]: local: not found [No such file or directory] > Lines 172, 182 and 183 invoke "local" to make local variables to the > function. According to "man bash", this is a shell builtin. However, > bin/karaf is invoked as: > #!/bin/sh > On most flavors of linux, this resolves to bash or dash which probably runs > in a restricted environment after checking to see that its $0 is sh. But on > Solaris's /bin/sh is actually ksh93 for backwards compatibility. > Since "local" is not part of a POSIX-compliant /bin/sh, depending on it in a > script that is invoked with /bin/sh is a bug. > (this explaination is borrowed from > https://issues.apache.org/jira/browse/MNG-5852) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4564) Can't start karaf using symbolic link
[ https://issues.apache.org/jira/browse/KARAF-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4564: Fix Version/s: 4.0.6 3.0.7 4.1.0 > Can't start karaf using symbolic link > -- > > Key: KARAF-4564 > URL: https://issues.apache.org/jira/browse/KARAF-4564 > Project: Karaf > Issue Type: Bug >Affects Versions: 3.0.6 > Environment: Ubuntu (Linux vagrant 3.19.0-25-generic > #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 > GNU/Linux) > OSX (Darwin inocybe.local 14.5.0 Darwin Kernel Version 14.5.0: Tue Sep 1 > 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64) > Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc) >Reporter: Alexis de Talhouët >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.7, 4.0.6 > > > When using a symbolic link to use the scripts defined here: > https://github.com/apache/karaf/tree/karaf-3.0.6/assemblies/features/framework/src/main/filtered-resources/resources/bin > e.g. karaf or client and so on, it's failing to start the container and show > this error: > Error: Could not find or load main class org.apache.karaf.main.Main > This issue is related to the DIRNAME variable and the way it is setup. > This bug has been found in OpenDaylight, here is the ticket with more > information https://bugs.opendaylight.org/show_bug.cgi?id=6027 > I have also propose a candidate fix in ODL: > https://git.opendaylight.org/gerrit/#/c/39982/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4527) The number in "Display all n possibilities?" differs from the actual number of commands listed
[ https://issues.apache.org/jira/browse/KARAF-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tadayoshi Sato resolved KARAF-4527. --- Resolution: Fixed JLine is already upgrade at KARAF-4555 > The number in "Display all n possibilities?" differs from the actual number > of commands listed > -- > > Key: KARAF-4527 > URL: https://issues.apache.org/jira/browse/KARAF-4527 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.0.5 >Reporter: Tadayoshi Sato >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6 > > > Hitting {{}} in the console shows, for example: > {code} > Display all 301 possibilities? (y or n) > {code} > However, counting the actual number of commands listed that follows typing > {{'y'}}, it is 275. There is a mismatch in numbers in the prompt message and > actual result. > This issue should be resolved by upgrading jLine to 2.14.2 (unreleased yet) > or higher: > https://github.com/jline/jline2/issues/247 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4527) The number in "Display all n possibilities?" differs from the actual number of commands listed
[ https://issues.apache.org/jira/browse/KARAF-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321828#comment-15321828 ] ASF GitHub Bot commented on KARAF-4527: --- Github user tadayosi closed the pull request at: https://github.com/apache/karaf/pull/191 > The number in "Display all n possibilities?" differs from the actual number > of commands listed > -- > > Key: KARAF-4527 > URL: https://issues.apache.org/jira/browse/KARAF-4527 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.0.5 >Reporter: Tadayoshi Sato >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6 > > > Hitting {{}} in the console shows, for example: > {code} > Display all 301 possibilities? (y or n) > {code} > However, counting the actual number of commands listed that follows typing > {{'y'}}, it is 275. There is a mismatch in numbers in the prompt message and > actual result. > This issue should be resolved by upgrading jLine to 2.14.2 (unreleased yet) > or higher: > https://github.com/jline/jline2/issues/247 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4566) "karaf" script invokes /bin/sh but requires /bin/bash functions
[ https://issues.apache.org/jira/browse/KARAF-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321508#comment-15321508 ] ASF GitHub Bot commented on KARAF-4566: --- GitHub user adetalhouet opened a pull request: https://github.com/apache/karaf/pull/197 KARAF-4566 "karaf" script invokes /bin/sh but requires /bin/bash functions The bin/karaf script uses the "local" command which is a shell builtin of bash and similar shells, but is not required for POSIX-compliance in sh. When I attempt to run karaf on a Solaris system, I see the following output: root@solaris:/opendaylight/bin# ./karaf ./karaf[172]: local: not found [No such file or directory] ./karaf[182]: local: not found [No such file or directory] ./karaf[183]: local: not found [No such file or directory] Lines 172, 182 and 183 invoke "local" to make local variables to the function. According to "man bash", this is a shell builtin. However, bin/karaf is invoked as: #!/bin/sh On most flavors of linux, this resolves to bash or dash which probably runs in a restricted environment after checking to see that its $0 is sh. But on Solaris's /bin/sh is actually ksh93 for backwards compatibility. Since "local" is not part of a POSIX-compliant /bin/sh, depending on it in a script that is invoked with /bin/sh is a bug. (this explaination is borrowed from https://issues.apache.org/jira/browse/MNG-5852) Signed-off-by: Alexis de TalhouëtYou can merge this pull request into a Git repository by running: $ git pull https://github.com/adetalhouet/karaf solaris-bash-local Alternatively you can review and apply these changes as the patch at: https://github.com/apache/karaf/pull/197.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #197 commit 9469d4a30d21d8c0418d1200d93e8951a8f9 Author: Alexis de Talhouët Date: 2016-06-08T21:51:18Z KARAF-4566 "karaf" script invokes /bin/sh but requires /bin/bash functions Signed-off-by: Alexis de Talhouët > "karaf" script invokes /bin/sh but requires /bin/bash functions > > > Key: KARAF-4566 > URL: https://issues.apache.org/jira/browse/KARAF-4566 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.6 > Environment: Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc) >Reporter: Alexis de Talhouët > > The bin/karaf script uses the "local" command which is a shell builtin of > bash and similar shells, but is not required for POSIX-compliance in sh. When > I attempt to run karaf on a Solaris system, I see the following output: > root@solaris:/opendaylight/bin# ./karaf > ./karaf[172]: local: not found [No such file or directory] > ./karaf[182]: local: not found [No such file or directory] > ./karaf[183]: local: not found [No such file or directory] > Lines 172, 182 and 183 invoke "local" to make local variables to the > function. According to "man bash", this is a shell builtin. However, > bin/karaf is invoked as: > #!/bin/sh > On most flavors of linux, this resolves to bash or dash which probably runs > in a restricted environment after checking to see that its $0 is sh. But on > Solaris's /bin/sh is actually ksh93 for backwards compatibility. > Since "local" is not part of a POSIX-compliant /bin/sh, depending on it in a > script that is invoked with /bin/sh is a bug. > (this explaination is borrowed from > https://issues.apache.org/jira/browse/MNG-5852) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4566) "karaf" script invokes /bin/sh but requires /bin/bash functions
Alexis de Talhouët created KARAF-4566: - Summary: "karaf" script invokes /bin/sh but requires /bin/bash functions Key: KARAF-4566 URL: https://issues.apache.org/jira/browse/KARAF-4566 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 3.0.6 Environment: Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc) Reporter: Alexis de Talhouët The bin/karaf script uses the "local" command which is a shell builtin of bash and similar shells, but is not required for POSIX-compliance in sh. When I attempt to run karaf on a Solaris system, I see the following output: root@solaris:/opendaylight/bin# ./karaf ./karaf[172]: local: not found [No such file or directory] ./karaf[182]: local: not found [No such file or directory] ./karaf[183]: local: not found [No such file or directory] Lines 172, 182 and 183 invoke "local" to make local variables to the function. According to "man bash", this is a shell builtin. However, bin/karaf is invoked as: #!/bin/sh On most flavors of linux, this resolves to bash or dash which probably runs in a restricted environment after checking to see that its $0 is sh. But on Solaris's /bin/sh is actually ksh93 for backwards compatibility. Since "local" is not part of a POSIX-compliant /bin/sh, depending on it in a script that is invoked with /bin/sh is a bug. (this explaination is borrowed from https://issues.apache.org/jira/browse/MNG-5852) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4564) Can't start karaf using symbolic link
[ https://issues.apache.org/jira/browse/KARAF-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321486#comment-15321486 ] Alexis de Talhouët commented on KARAF-4564: --- Pull request opened: https://github.com/apache/karaf/pull/196 > Can't start karaf using symbolic link > -- > > Key: KARAF-4564 > URL: https://issues.apache.org/jira/browse/KARAF-4564 > Project: Karaf > Issue Type: Bug >Affects Versions: 3.0.6 > Environment: Ubuntu (Linux vagrant 3.19.0-25-generic > #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 > GNU/Linux) > OSX (Darwin inocybe.local 14.5.0 Darwin Kernel Version 14.5.0: Tue Sep 1 > 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64) > Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc) >Reporter: Alexis de Talhouët > > When using a symbolic link to use the scripts defined here: > https://github.com/apache/karaf/tree/karaf-3.0.6/assemblies/features/framework/src/main/filtered-resources/resources/bin > e.g. karaf or client and so on, it's failing to start the container and show > this error: > Error: Could not find or load main class org.apache.karaf.main.Main > This issue is related to the DIRNAME variable and the way it is setup. > This bug has been found in OpenDaylight, here is the ticket with more > information https://bugs.opendaylight.org/show_bug.cgi?id=6027 > I have also propose a candidate fix in ODL: > https://git.opendaylight.org/gerrit/#/c/39982/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4564) Can't start karaf using symbolic link
[ https://issues.apache.org/jira/browse/KARAF-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321485#comment-15321485 ] ASF GitHub Bot commented on KARAF-4564: --- GitHub user adetalhouet opened a pull request: https://github.com/apache/karaf/pull/196 KARAF-4564 Can't start karaf using symbolic link Signed-off-by: Alexis de TalhouëtYou can merge this pull request into a Git repository by running: $ git pull https://github.com/adetalhouet/karaf symbolic-link Alternatively you can review and apply these changes as the patch at: https://github.com/apache/karaf/pull/196.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #196 commit 93dcdbc32f723621992c8fae616780e50d8f739f Author: Alexis de Talhouët Date: 2016-06-08T21:28:59Z KARAF-4564 Can't start karaf using symbolic link Signed-off-by: Alexis de Talhouët > Can't start karaf using symbolic link > -- > > Key: KARAF-4564 > URL: https://issues.apache.org/jira/browse/KARAF-4564 > Project: Karaf > Issue Type: Bug >Affects Versions: 3.0.6 > Environment: Ubuntu (Linux vagrant 3.19.0-25-generic > #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 > GNU/Linux) > OSX (Darwin inocybe.local 14.5.0 Darwin Kernel Version 14.5.0: Tue Sep 1 > 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64) > Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc) >Reporter: Alexis de Talhouët > > When using a symbolic link to use the scripts defined here: > https://github.com/apache/karaf/tree/karaf-3.0.6/assemblies/features/framework/src/main/filtered-resources/resources/bin > e.g. karaf or client and so on, it's failing to start the container and show > this error: > Error: Could not find or load main class org.apache.karaf.main.Main > This issue is related to the DIRNAME variable and the way it is setup. > This bug has been found in OpenDaylight, here is the ticket with more > information https://bugs.opendaylight.org/show_bug.cgi?id=6027 > I have also propose a candidate fix in ODL: > https://git.opendaylight.org/gerrit/#/c/39982/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4565) Set ConfigurationPolicy.REQUIRE for decanter appenders and collectors
[ https://issues.apache.org/jira/browse/KARAF-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320888#comment-15320888 ] Jean-Baptiste Onofré commented on KARAF-4565: - It seems related to spring-boot support (as it works fine in Karaf): if it doesn't impact the default behavior, that's fine for me. > Set ConfigurationPolicy.REQUIRE for decanter appenders and collectors > - > > Key: KARAF-4565 > URL: https://issues.apache.org/jira/browse/KARAF-4565 > Project: Karaf > Issue Type: Improvement > Components: decanter >Affects Versions: decanter-1.1.0 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: decanter-1.1.1 > > > Currently decanter components start with defaults if no config is supplied. > I would like to change this so the component only starts if a config is > supplied. Defaults still apply but the presence of an empty config can then > be used to swtich the component on and off. > This is especially important for fixed deployments were a set of components > is deployed but you want to configure which ones to actually use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4565) Set ConfigurationPolicy.REQUIRE for decanter appenders and collectors
Christian Schneider created KARAF-4565: -- Summary: Set ConfigurationPolicy.REQUIRE for decanter appenders and collectors Key: KARAF-4565 URL: https://issues.apache.org/jira/browse/KARAF-4565 Project: Karaf Issue Type: Improvement Components: decanter Affects Versions: decanter-1.1.0 Reporter: Christian Schneider Assignee: Christian Schneider Fix For: decanter-1.1.1 Currently decanter components start with defaults if no config is supplied. I would like to change this so the component only starts if a config is supplied. Defaults still apply but the presence of an empty config can then be used to swtich the component on and off. This is especially important for fixed deployments were a set of components is deployed but you want to configure which ones to actually use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4564) Can't start karaf using symbolic link
Alexis de Talhouët created KARAF-4564: - Summary: Can't start karaf using symbolic link Key: KARAF-4564 URL: https://issues.apache.org/jira/browse/KARAF-4564 Project: Karaf Issue Type: Bug Affects Versions: 3.0.6 Environment: Ubuntu (Linux vagrant 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux) OSX (Darwin inocybe.local 14.5.0 Darwin Kernel Version 14.5.0: Tue Sep 1 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64) Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc) Reporter: Alexis de Talhouët When using a symbolic link to use the scripts defined here: https://github.com/apache/karaf/tree/karaf-3.0.6/assemblies/features/framework/src/main/filtered-resources/resources/bin e.g. karaf or client and so on, it's failing to start the container and show this error: Error: Could not find or load main class org.apache.karaf.main.Main This issue is related to the DIRNAME variable and the way it is setup. This bug has been found in OpenDaylight, here is the ticket with more information https://bugs.opendaylight.org/show_bug.cgi?id=6027 I have also propose a candidate fix in ODL: https://git.opendaylight.org/gerrit/#/c/39982/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4556) Upgrade to Aries Blueprint CM 1.0.9
[ https://issues.apache.org/jira/browse/KARAF-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4556. - Resolution: Invalid > Upgrade to Aries Blueprint CM 1.0.9 > --- > > Key: KARAF-4556 > URL: https://issues.apache.org/jira/browse/KARAF-4556 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4556) Upgrade to Aries Blueprint CM 1.0.9
[ https://issues.apache.org/jira/browse/KARAF-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320259#comment-15320259 ] ASF subversion and git services commented on KARAF-4556: Commit 28fed08751a278e6148448431cbd6752dcfca29d in karaf's branch refs/heads/karaf-4.0.x from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=28fed08 ] Revert "[KARAF-4556] Upgrade to Aries Blueprint CM 1.0.9" This reverts commit 7cf848268c0e77f1f7421c2e518f4bdd891d579b. > Upgrade to Aries Blueprint CM 1.0.9 > --- > > Key: KARAF-4556 > URL: https://issues.apache.org/jira/browse/KARAF-4556 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4556) Upgrade to Aries Blueprint CM 1.0.9
[ https://issues.apache.org/jira/browse/KARAF-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320262#comment-15320262 ] ASF subversion and git services commented on KARAF-4556: Commit 94467d10c3cea34aacf028c919e814eb9e9b25dd in karaf's branch refs/heads/karaf-3.0.x from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=94467d1 ] Revert "[KARAF-4556] Upgrade to Aries Blueprint CM 1.0.9" This reverts commit e9a0c8966d0bb24f58d221919e1fd8aa6be98462. > Upgrade to Aries Blueprint CM 1.0.9 > --- > > Key: KARAF-4556 > URL: https://issues.apache.org/jira/browse/KARAF-4556 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4556) Upgrade to Aries Blueprint CM 1.0.9
[ https://issues.apache.org/jira/browse/KARAF-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320258#comment-15320258 ] ASF subversion and git services commented on KARAF-4556: Commit 76d64a9d2f814f39cfe0f38f13d944b410596e54 in karaf's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=76d64a9 ] Revert "[KARAF-4556] Upgrade to Aries Blueprint CM 1.0.9" This reverts commit 243ed0b2391d5df9825bb33f9b2ab8007af6c604. > Upgrade to Aries Blueprint CM 1.0.9 > --- > > Key: KARAF-4556 > URL: https://issues.apache.org/jira/browse/KARAF-4556 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (KARAF-4556) Upgrade to Aries Blueprint CM 1.0.9
[ https://issues.apache.org/jira/browse/KARAF-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reopened KARAF-4556: - Aries Blueprint CM 1.0.9 release has been canceled. It's an update mistake there. Reverting. > Upgrade to Aries Blueprint CM 1.0.9 > --- > > Key: KARAF-4556 > URL: https://issues.apache.org/jira/browse/KARAF-4556 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4556) Upgrade to Aries Blueprint CM 1.0.9
[ https://issues.apache.org/jira/browse/KARAF-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4556: Fix Version/s: (was: 4.0.6) (was: 3.0.7) (was: 4.1.0) > Upgrade to Aries Blueprint CM 1.0.9 > --- > > Key: KARAF-4556 > URL: https://issues.apache.org/jira/browse/KARAF-4556 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4563) Upgrade Cglib to version 3.2.2
[ https://issues.apache.org/jira/browse/KARAF-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved KARAF-4563. - Resolution: Fixed > Upgrade Cglib to version 3.2.2 > -- > > Key: KARAF-4563 > URL: https://issues.apache.org/jira/browse/KARAF-4563 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.1.0, 4.0.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4563) Upgrade Cglib to version 3.2.2
[ https://issues.apache.org/jira/browse/KARAF-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320105#comment-15320105 ] ASF subversion and git services commented on KARAF-4563: Commit 954f7d48479b09ee92af2d927675ed278a3750c0 in karaf's branch refs/heads/karaf-4.0.x from [~ancosen] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=954f7d4 ] [KARAF-4563] Upgrade Cglib to version 3.2.2 > Upgrade Cglib to version 3.2.2 > -- > > Key: KARAF-4563 > URL: https://issues.apache.org/jira/browse/KARAF-4563 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.1.0, 4.0.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4563) Upgrade Cglib to version 3.2.2
[ https://issues.apache.org/jira/browse/KARAF-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320100#comment-15320100 ] ASF subversion and git services commented on KARAF-4563: Commit 8a5a4bb2a7153affd21167df6c48668fe5977735 in karaf's branch refs/heads/master from [~ancosen] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=8a5a4bb ] [KARAF-4563] Upgrade Cglib to version 3.2.2 > Upgrade Cglib to version 3.2.2 > -- > > Key: KARAF-4563 > URL: https://issues.apache.org/jira/browse/KARAF-4563 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.1.0, 4.0.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4563) Upgrade Cglib to version 3.2.2
Andrea Cosentino created KARAF-4563: --- Summary: Upgrade Cglib to version 3.2.2 Key: KARAF-4563 URL: https://issues.apache.org/jira/browse/KARAF-4563 Project: Karaf Issue Type: Dependency upgrade Components: karaf-core Reporter: Andrea Cosentino Assignee: Andrea Cosentino Priority: Minor Fix For: 4.1.0, 4.0.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)