[jira] [Resolved] (KARAF-3937) Karaf Cave produces incomplete indexes
[ https://issues.apache.org/jira/browse/KARAF-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-3937. Resolution: Fixed Fix Version/s: cave-4.0.1 https://git1-us-west.apache.org/repos/asf?p=karaf-cave.git;a=commitdiff;h=e0913bc7fed4dce549f9f18ca17b8060075ae7f1 Karaf Cave produces incomplete indexes -- Key: KARAF-3937 URL: https://issues.apache.org/jira/browse/KARAF-3937 Project: Karaf Issue Type: Bug Affects Versions: 4.0.0 Reporter: Timothy Ward Assignee: Guillaume Nodet Priority: Critical Fix For: cave-4.0.1 The Cave indexer creates incomplete indexes for OSGi bundles. Section 132.4 of the OSGi spec defines the osgi.content namespace, and four mandatory attributes. Cave indexes only contain the URL, but miss the SHA-256 hash, length, and mime type (e.g. application/vnd.osgi.bundle). This breaks other tools and code that interact with the indexes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3937) Karaf Cave produces incomplete indexes
[ https://issues.apache.org/jira/browse/KARAF-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated KARAF-3937: --- Affects Version/s: (was: 4.0.0) cave-4.0.0 Karaf Cave produces incomplete indexes -- Key: KARAF-3937 URL: https://issues.apache.org/jira/browse/KARAF-3937 Project: Karaf Issue Type: Bug Affects Versions: cave-4.0.0 Reporter: Timothy Ward Assignee: Guillaume Nodet Priority: Critical Fix For: cave-4.0.1 The Cave indexer creates incomplete indexes for OSGi bundles. Section 132.4 of the OSGi spec defines the osgi.content namespace, and four mandatory attributes. Cave indexes only contain the URL, but miss the SHA-256 hash, length, and mime type (e.g. application/vnd.osgi.bundle). This breaks other tools and code that interact with the indexes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3949) Be able to load System properties from another file than etc/system.properties
[
https://issues.apache.org/jira/browse/KARAF-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709318#comment-14709318
]
Guillaume Nodet commented on KARAF-3949:
I don't think we should support additional files in the code.
However, we have the {{${includes}}} and {{${optionals}}} which do not seem to
be supported when loading the {{system.properties}} file. It should simply be
a matter of adding the two calls.
Be able to load System properties from another file than etc/system.properties
--
Key: KARAF-3949
URL: https://issues.apache.org/jira/browse/KARAF-3949
Project: Karaf
Issue Type: Improvement
Components: karaf-core
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
We can use etc/system.properties to define System properties.
The Karaf Main loads (and may override) System properties from this file.
When we create a custom distribution, and users want to add their own System
properties, they have to provision a complete etc/system.properties.
It makes sense to be able to provision a etc/systemuser.properties without
altering the etc/system.properties: Karaf Main can load the System.properties
from both, first from etc/system.properties and after from
etc/systemuser.properties (optional).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (KARAF-3949) Be able to load System properties from another file than etc/system.properties
[
https://issues.apache.org/jira/browse/KARAF-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709318#comment-14709318
]
Guillaume Nodet edited comment on KARAF-3949 at 8/24/15 1:52 PM:
-
I don't think we should support additional files in the code.
However, we have the {{\$\{includes\}}} and {{\$\{optionals\}}} which do not
seem to be supported when loading the {{system.properties}} file. It should
simply be a matter of adding the two calls.
was (Author: gnt):
I don't think we should support additional files in the code.
However, we have the {{${includes}}} and {{${optionals}}} which do not seem to
be supported when loading the {{system.properties}} file. It should simply be
a matter of adding the two calls.
Be able to load System properties from another file than etc/system.properties
--
Key: KARAF-3949
URL: https://issues.apache.org/jira/browse/KARAF-3949
Project: Karaf
Issue Type: Improvement
Components: karaf-core
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
We can use etc/system.properties to define System properties.
The Karaf Main loads (and may override) System properties from this file.
When we create a custom distribution, and users want to add their own System
properties, they have to provision a complete etc/system.properties.
It makes sense to be able to provision a etc/systemuser.properties without
altering the etc/system.properties: Karaf Main can load the System.properties
from both, first from etc/system.properties and after from
etc/systemuser.properties (optional).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (KARAF-3949) Be able to load System properties from another file than etc/system.properties
[
https://issues.apache.org/jira/browse/KARAF-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709318#comment-14709318
]
Guillaume Nodet edited comment on KARAF-3949 at 8/24/15 1:53 PM:
-
I don't think we should support additional files in the code.
However, we have the {{$\{includes\}}} and {{$\{optionals\}}} which do not seem
to be supported when loading the {{system.properties}} file. It should simply
be a matter of adding the two calls.
was (Author: gnt):
I don't think we should support additional files in the code.
However, we have the {{\$\{includes\}}} and {{\$\{optionals\}}} which do not
seem to be supported when loading the {{system.properties}} file. It should
simply be a matter of adding the two calls.
Be able to load System properties from another file than etc/system.properties
--
Key: KARAF-3949
URL: https://issues.apache.org/jira/browse/KARAF-3949
Project: Karaf
Issue Type: Improvement
Components: karaf-core
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
We can use etc/system.properties to define System properties.
The Karaf Main loads (and may override) System properties from this file.
When we create a custom distribution, and users want to add their own System
properties, they have to provision a complete etc/system.properties.
It makes sense to be able to provision a etc/systemuser.properties without
altering the etc/system.properties: Karaf Main can load the System.properties
from both, first from etc/system.properties and after from
etc/systemuser.properties (optional).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3937) Karaf Cave produces incomplete indexes
[ https://issues.apache.org/jira/browse/KARAF-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709342#comment-14709342 ] Timothy Ward commented on KARAF-3937: - I work on bndtools, and we're starting to allow users to specify a SHA requirement for dependencies that should not change over time. I was a bit surprised when I couldn't find the SHA in the cave index! We obviously have some defensive logic for the case where the SHA is missing, but in general it's better if we can rely on the spec properties. Karaf Cave produces incomplete indexes -- Key: KARAF-3937 URL: https://issues.apache.org/jira/browse/KARAF-3937 Project: Karaf Issue Type: Bug Affects Versions: cave-4.0.0 Reporter: Timothy Ward Assignee: Guillaume Nodet Priority: Critical Fix For: cave-4.0.1 The Cave indexer creates incomplete indexes for OSGi bundles. Section 132.4 of the OSGi spec defines the osgi.content namespace, and four mandatory attributes. Cave indexes only contain the URL, but miss the SHA-256 hash, length, and mime type (e.g. application/vnd.osgi.bundle). This breaks other tools and code that interact with the indexes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3953) Karaf fails to diagnose un-wire-able bundle in feature
[
https://issues.apache.org/jira/browse/KARAF-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709311#comment-14709311
]
Benson Margulies commented on KARAF-3953:
-
The problem here seems specific to a feature named 'feature'. When I rename it
to 'test-feature', I get a proper diagnosis.
Karaf fails to diagnose un-wire-able bundle in feature
--
Key: KARAF-3953
URL: https://issues.apache.org/jira/browse/KARAF-3953
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Benson Margulies
See https://github.com/bimargulies/karaf-wire-tc.
Build this, start the assembly. (assembly/target/assembly/bin/karaf)
{noformat}
feature:install feature
{noformat}
will not accomplish anything, and also not complain in the log that I can see.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (KARAF-3953) Karaf fails to diagnose un-wire-able bundle in feature
[
https://issues.apache.org/jira/browse/KARAF-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709311#comment-14709311
]
Benson Margulies edited comment on KARAF-3953 at 8/24/15 1:56 PM:
--
The problem here seems specific to a feature named 'feature'. When I rename it
to 'test-feature', I get a proper diagnosis.
However, my original unminimized problem was with a feature with a reasonable
name. So I don't know whether to bother tracking down this pathology with the
feature named 'feature', or whether to elaborate the test case to try to repro
the more interesting failure with a feature with another name.
was (Author: bmargulies):
The problem here seems specific to a feature named 'feature'. When I rename it
to 'test-feature', I get a proper diagnosis.
Karaf fails to diagnose un-wire-able bundle in feature
--
Key: KARAF-3953
URL: https://issues.apache.org/jira/browse/KARAF-3953
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Benson Margulies
See https://github.com/bimargulies/karaf-wire-tc.
Build this, start the assembly. (assembly/target/assembly/bin/karaf)
{noformat}
feature:install feature
{noformat}
will not accomplish anything, and also not complain in the log that I can see.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (KARAF-3944) Karaf Cave OBR Index osgi.content Capability Missing Mandatory Attributes
[ https://issues.apache.org/jira/browse/KARAF-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed KARAF-3944. -- Resolution: Duplicate Assignee: Guillaume Nodet Karaf Cave OBR Index osgi.content Capability Missing Mandatory Attributes - Key: KARAF-3944 URL: https://issues.apache.org/jira/browse/KARAF-3944 Project: Karaf Issue Type: Bug Components: cave-repository Affects Versions: cave-4.0.0 Reporter: Stephen Kahmann Assignee: Guillaume Nodet Priority: Minor Attachments: Screen Shot 2015-08-20 at 10.55.55 AM.png The osgi.content capability in OBR indexes created by Cave 4.0.0 are missing 3 mandatory attributes: osgi.content, size, and mime. Reference page 534 of the OSGI Enterprise R5 Spec. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3937) Karaf Cave produces incomplete indexes
[ https://issues.apache.org/jira/browse/KARAF-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709324#comment-14709324 ] Guillaume Nodet commented on KARAF-3937: Btw, which external tool are you using ? Karaf Cave produces incomplete indexes -- Key: KARAF-3937 URL: https://issues.apache.org/jira/browse/KARAF-3937 Project: Karaf Issue Type: Bug Affects Versions: cave-4.0.0 Reporter: Timothy Ward Assignee: Guillaume Nodet Priority: Critical Fix For: cave-4.0.1 The Cave indexer creates incomplete indexes for OSGi bundles. Section 132.4 of the OSGi spec defines the osgi.content namespace, and four mandatory attributes. Cave indexes only contain the URL, but miss the SHA-256 hash, length, and mime type (e.g. application/vnd.osgi.bundle). This breaks other tools and code that interact with the indexes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-511) When updating a bundle, completers are not always refreshed
[ https://issues.apache.org/jira/browse/KARAF-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated KARAF-511: -- Affects Version/s: 3.0.4 2.4.3 When updating a bundle, completers are not always refreshed --- Key: KARAF-511 URL: https://issues.apache.org/jira/browse/KARAF-511 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 3.0.4, 2.4.3 Reporter: Guillaume Nodet Priority: Minor The problem is that the CommandsCompleter#checkData checks for new/removed commands, but if the names are the same, completers aren't refreshed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3762) feature resolver for system.bundle (equinox) faulty
[ https://issues.apache.org/jira/browse/KARAF-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709462#comment-14709462 ] Markus Rathgeb commented on KARAF-3762: --- This is fixed at least with 4.0.1 (do not remember, but IMHO it was fixed with 4.0.0). feature resolver for system.bundle (equinox) faulty --- Key: KARAF-3762 URL: https://issues.apache.org/jira/browse/KARAF-3762 Project: Karaf Issue Type: Bug Components: karaf-feature, karaf-kar Affects Versions: 4.0.0.M2 Reporter: Markus Rathgeb Assignee: Jean-Baptiste Onofré I want to create a feature, that contains a jar (third party one). The manifest of that bundle contains: Require-Bundle: system.bundle If I am using karaf.framework=felix all seems to be working. If I am using karaf.framework=equinox and install the kar / feature that contains that bundle I get the following message: Error executing command: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=karaf-oh2-feature; type=karaf.feature; version=[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]; filter:=((osgi.identity=karaf-oh2-feature)(type=karaf.feature)(version=1.0.0.SNAPSHOT)(version=1.0.0.SNAPSHOT)) [caused by: Unable to resolve karaf-oh2-feature/1.0.0.SNAPSHOT: missing requirement [karaf-oh2-feature/1.0.0.SNAPSHOT] osgi.identity; osgi.identity=javax.activation; type=osgi.bundle; version=[1.1.0.v201211130549,1.1.0.v201211130549]; resolution:=mandatory [caused by: Unable to resolve javax.activation/1.1.0.v201211130549: missing requirement [javax.activation/1.1.0.v201211130549] osgi.wiring.bundle; osgi.wiring.bundle=system.bundle; filter:=(osgi.wiring.bundle=system.bundle)]] I can install that bundle using bundle:install. If I retry to install the feature, I can install it now. Here you could find a kar that demonstrate the problem: https://drive.google.com/file/d/0Bx99QXY8p6gvY3BoMXlZeXRIOWs/view?usp=sharing kar:install should write the above error message in your log. Installing the feature should trigger the error, too. You can extract the jar (javax.activation) of that kar and will see, that you are able to install it using bundle:install. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-3762) feature resolver for system.bundle (equinox) faulty
[ https://issues.apache.org/jira/browse/KARAF-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Rathgeb resolved KARAF-3762. --- Resolution: Fixed Fix Version/s: 4.0.1 feature resolver for system.bundle (equinox) faulty --- Key: KARAF-3762 URL: https://issues.apache.org/jira/browse/KARAF-3762 Project: Karaf Issue Type: Bug Components: karaf-feature, karaf-kar Affects Versions: 4.0.0.M2 Reporter: Markus Rathgeb Assignee: Jean-Baptiste Onofré Fix For: 4.0.1 I want to create a feature, that contains a jar (third party one). The manifest of that bundle contains: Require-Bundle: system.bundle If I am using karaf.framework=felix all seems to be working. If I am using karaf.framework=equinox and install the kar / feature that contains that bundle I get the following message: Error executing command: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=karaf-oh2-feature; type=karaf.feature; version=[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]; filter:=((osgi.identity=karaf-oh2-feature)(type=karaf.feature)(version=1.0.0.SNAPSHOT)(version=1.0.0.SNAPSHOT)) [caused by: Unable to resolve karaf-oh2-feature/1.0.0.SNAPSHOT: missing requirement [karaf-oh2-feature/1.0.0.SNAPSHOT] osgi.identity; osgi.identity=javax.activation; type=osgi.bundle; version=[1.1.0.v201211130549,1.1.0.v201211130549]; resolution:=mandatory [caused by: Unable to resolve javax.activation/1.1.0.v201211130549: missing requirement [javax.activation/1.1.0.v201211130549] osgi.wiring.bundle; osgi.wiring.bundle=system.bundle; filter:=(osgi.wiring.bundle=system.bundle)]] I can install that bundle using bundle:install. If I retry to install the feature, I can install it now. Here you could find a kar that demonstrate the problem: https://drive.google.com/file/d/0Bx99QXY8p6gvY3BoMXlZeXRIOWs/view?usp=sharing kar:install should write the above error message in your log. Installing the feature should trigger the error, too. You can extract the jar (javax.activation) of that kar and will see, that you are able to install it using bundle:install. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-2585) pax logger handles some stacktraces incorrectly
[ https://issues.apache.org/jira/browse/KARAF-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-2585. Resolution: Fixed pax logger handles some stacktraces incorrectly --- Key: KARAF-2585 URL: https://issues.apache.org/jira/browse/KARAF-2585 Project: Karaf Issue Type: Bug Reporter: Alexandr Palto I met situation when attempt to log original exception cause to next exception in karaf's log (and the application is failed completelly): 17:46:26,439 | INFO | on(33)-127.0.0.1 | f.runtime.logging.TestLoggerImpl 104 | 215 - tesb.tf.runtime.logging - 2.23.0.SNAPSHOT | [slr0013--1384357503773] Add new 'Exc eption' event: Executor org.talend.esb.test.stories.common.delegates.CommonRequestResponseExecutor@175595cc failed with source java.lang.NoClassDefFoundError: Could not initialize class sun.reflect.misc.Trampoline at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:188) at org.apache.log4j.OsgiThrowableRenderer.findClass(OsgiThrowableRenderer.java:226) at org.apache.log4j.OsgiThrowableRenderer.formatElement(OsgiThrowableRenderer.java:136) at org.apache.log4j.OsgiThrowableRenderer.doRender(OsgiThrowableRenderer.java:107) at org.apache.log4j.OsgiThrowableRenderer.doRender(OsgiThrowableRenderer.java:52) ... I had debugged mentioned codes and see that in original stacktrace I see class Trampoline. Looks like try\catch in formatElement method should be updated to catch Throwable, not Exception. I'd tried to create pull request with this, but looks like previous is not merged yet. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3953) Karaf fails to diagnose un-wire-able bundle in feature
[
https://issues.apache.org/jira/browse/KARAF-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709594#comment-14709594
]
Benson Margulies commented on KARAF-3953:
-
I've tried to recreate the original scenario:
A feature named {rosapi-worker}, consisting of a bundle that had two non-OSGi
dependencies (this was a mistake) and I excluded one but not the other. When I
set up a model of this, the feature is installable, even though it should have
a problem.
I fear that this JIRA, too, needs to be closed as invalid and I need to just
move on from this irritating incident.
Karaf fails to diagnose un-wire-able bundle in feature
--
Key: KARAF-3953
URL: https://issues.apache.org/jira/browse/KARAF-3953
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Benson Margulies
See https://github.com/bimargulies/karaf-wire-tc.
Build this, start the assembly. (assembly/target/assembly/bin/karaf)
{noformat}
feature:install feature
{noformat}
will not accomplish anything, and also not complain in the log that I can see.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3953) Karaf fails to diagnose un-wire-able bundle in feature
[
https://issues.apache.org/jira/browse/KARAF-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709586#comment-14709586
]
Guillaume Nodet commented on KARAF-3953:
The problem comes from the fact that the feature {{feature}} is already defined
by karaf.
Karaf should maybe warn or reject when adding a repository which contain
features with names already defined by other repositories.
Karaf fails to diagnose un-wire-able bundle in feature
--
Key: KARAF-3953
URL: https://issues.apache.org/jira/browse/KARAF-3953
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Benson Margulies
See https://github.com/bimargulies/karaf-wire-tc.
Build this, start the assembly. (assembly/target/assembly/bin/karaf)
{noformat}
feature:install feature
{noformat}
will not accomplish anything, and also not complain in the log that I can see.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3808) karaf-maven-plugin uses user_dir/.m2 as local repo even if settings.xml localRepository points to different folder
[
https://issues.apache.org/jira/browse/KARAF-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709557#comment-14709557
]
Guillaume Nodet commented on KARAF-3808:
Could you try with 4.0.1 ?
I've debugged a bit and the plugin uses the value specified in
~/.m2/settings.xml.
Unless you have the {{org.ops4j.pax.url.mvn.localRepository}} defined to
another location, that's what should happen.
karaf-maven-plugin uses user_dir/.m2 as local repo even if settings.xml
localRepository points to different folder
--
Key: KARAF-3808
URL: https://issues.apache.org/jira/browse/KARAF-3808
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 4.0.0
Environment: macos, java1.8.0_45, maven 3.3.3
Reporter: Dmytro Pishchukhin
Priority: Critical
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (KARAF-3953) Karaf fails to diagnose un-wire-able bundle in feature
[
https://issues.apache.org/jira/browse/KARAF-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709586#comment-14709586
]
Guillaume Nodet edited comment on KARAF-3953 at 8/24/15 4:43 PM:
-
The problem comes from the fact that the feature {{feature}} is already defined
by karaf.
So the install command works, but really does nothing as the feature is already
installed.
Karaf should maybe warn or reject when adding a repository which contain
features with names already defined by other repositories.
was (Author: gnt):
The problem comes from the fact that the feature {{feature}} is already defined
by karaf.
Karaf should maybe warn or reject when adding a repository which contain
features with names already defined by other repositories.
Karaf fails to diagnose un-wire-able bundle in feature
--
Key: KARAF-3953
URL: https://issues.apache.org/jira/browse/KARAF-3953
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Benson Margulies
See https://github.com/bimargulies/karaf-wire-tc.
Build this, start the assembly. (assembly/target/assembly/bin/karaf)
{noformat}
feature:install feature
{noformat}
will not accomplish anything, and also not complain in the log that I can see.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3942) Using ' and symbols with commands completion
[
https://issues.apache.org/jira/browse/KARAF-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709605#comment-14709605
]
Guillaume Nodet commented on KARAF-3942:
I think the goal is not to have the quotes in the string of the argument, but
rather to have them interpreted by the shell so the
{code}
kar:create '{http://talend.org/greeter}Greeter'
{code}
would receive a single argument.
However, when the completion is executed inside an unclosed quoted argument, an
exception is thrown by the parser and completion does not occur at all.
Using ' and symbols with commands completion
--
Key: KARAF-3942
URL: https://issues.apache.org/jira/browse/KARAF-3942
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 4.0.1
Reporter: Pavlo Vasylchenko
I need to use command completion with parameter, surrounded by quotes.
But when I type
{code}
test:mycommand ' + TAB
{code}
I will have an exception.
The same for default commands:
{code}
kar:create ‘ + TAB = Error executing command: String index out of range: 13
{code}
If I pass QName without quotes like:
{code}
{http://talend.org/greeter}Greeter
{code}
karaf thinks that it is two different arguments
{code}
{http://talend.org/greeter}
{code}
and
{code}
Greeter
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3953) Karaf fails to diagnose un-wire-able bundle in feature
[
https://issues.apache.org/jira/browse/KARAF-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709604#comment-14709604
]
Jean-Baptiste Onofré commented on KARAF-3953:
-
+1
Karaf fails to diagnose un-wire-able bundle in feature
--
Key: KARAF-3953
URL: https://issues.apache.org/jira/browse/KARAF-3953
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Benson Margulies
See https://github.com/bimargulies/karaf-wire-tc.
Build this, start the assembly. (assembly/target/assembly/bin/karaf)
{noformat}
feature:install feature
{noformat}
will not accomplish anything, and also not complain in the log that I can see.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-3953) Karaf fails to diagnose un-wire-able bundle in feature
[
https://issues.apache.org/jira/browse/KARAF-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved KARAF-3953.
-
Resolution: Cannot Reproduce
Karaf fails to diagnose un-wire-able bundle in feature
--
Key: KARAF-3953
URL: https://issues.apache.org/jira/browse/KARAF-3953
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Benson Margulies
See https://github.com/bimargulies/karaf-wire-tc.
Build this, start the assembly. (assembly/target/assembly/bin/karaf)
{noformat}
feature:install feature
{noformat}
will not accomplish anything, and also not complain in the log that I can see.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3938) NPE in Felix when installing camel-spark-rest feature
[
https://issues.apache.org/jira/browse/KARAF-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709874#comment-14709874
]
Guillaume Nodet commented on KARAF-3938:
Felix does not seem to support the {{Bundle-NativeCode: *}} header.
Event when running under equinox, Karaf features-core bundles throws an
exception too because of the degenerated filters that gets created.
NPE in Felix when installing camel-spark-rest feature
-
Key: KARAF-3938
URL: https://issues.apache.org/jira/browse/KARAF-3938
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Claus Ibsen
Use Java 8
Install Camel 2.16-SNAPSHOT
When installing the camel-spark-rest feature you get this NPE
{code}
2015-08-20 07:48:59,907 | ERROR | nsole user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.0.1 | Exception caught while
executing command
java.lang.NullPointerException
at
org.apache.felix.framework.capabilityset.CapabilitySet.match(CapabilitySet.java:197)[org.apache.felix.framework-5.0.1.jar:]
at
org.apache.felix.framework.capabilityset.CapabilitySet.match(CapabilitySet.java:187)[org.apache.felix.framework-5.0.1.jar:]
at
org.apache.felix.framework.StatefulResolver.findProvidersInternal(StatefulResolver.java:229)[org.apache.felix.framework-5.0.1.jar:]
at
org.apache.felix.framework.ResolveContextImpl.findProviders(ResolveContextImpl.java:89)[org.apache.felix.framework-5.0.1.jar:]
at
org.apache.felix.resolver.Candidates.populateResource(Candidates.java:288)[org.apache.felix.framework-5.0.1.jar:]
at
org.apache.felix.resolver.Candidates.populate(Candidates.java:177)[org.apache.felix.framework-5.0.1.jar:]
at
org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:168)[org.apache.felix.framework-5.0.1.jar:]
at
org.apache.felix.framework.StatefulResolver.resolve(StatefulResolver.java:431)[org.apache.felix.framework-5.0.1.jar:]
at
org.apache.felix.framework.Felix.resolveBundles(Felix.java:4073)[org.apache.felix.framework-5.0.1.jar:]
at
org.apache.felix.framework.FrameworkWiringImpl.resolveBundles(FrameworkWiringImpl.java:133)[org.apache.felix.framework-5.0.1.jar:]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.resolveBundles(FeaturesServiceImpl.java:1267)[8:org.apache.karaf.features.core:4.0.1]
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:823)[8:org.apache.karaf.features.core:4.0.1]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1079)[8:org.apache.karaf.features.core:4.0.1]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:975)[8:org.apache.karaf.features.core:4.0.1]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_31]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_31]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_31]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_31]
karaf@root() feature:install camel-spark-rest
Error executing command: java.lang.NullPointerException
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-3954) Convey terminal size changes through SSH
[ https://issues.apache.org/jira/browse/KARAF-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-3954. Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=23668b681c8dd6173385d45924952292eef0acef Convey terminal size changes through SSH Key: KARAF-3954 URL: https://issues.apache.org/jira/browse/KARAF-3954 Project: Karaf Issue Type: Improvement Reporter: Guillaume Nodet Assignee: Guillaume Nodet Priority: Minor Fix For: 4.0.2 When running bin/client, instance:connect or ssh:ssh, terminal size changes are not sent through SSH, leading to completion or commands that use the terminal width to not behave correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-3937) Karaf Cave produces incomplete indexes
[ https://issues.apache.org/jira/browse/KARAF-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned KARAF-3937: -- Assignee: Guillaume Nodet Karaf Cave produces incomplete indexes -- Key: KARAF-3937 URL: https://issues.apache.org/jira/browse/KARAF-3937 Project: Karaf Issue Type: Bug Affects Versions: 4.0.0 Reporter: Timothy Ward Assignee: Guillaume Nodet Priority: Critical The Cave indexer creates incomplete indexes for OSGi bundles. Section 132.4 of the OSGi spec defines the osgi.content namespace, and four mandatory attributes. Cave indexes only contain the URL, but miss the SHA-256 hash, length, and mime type (e.g. application/vnd.osgi.bundle). This breaks other tools and code that interact with the indexes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3954) Convey terminal size changes through SSH
Guillaume Nodet created KARAF-3954: -- Summary: Convey terminal size changes through SSH Key: KARAF-3954 URL: https://issues.apache.org/jira/browse/KARAF-3954 Project: Karaf Issue Type: Improvement Reporter: Guillaume Nodet Assignee: Guillaume Nodet Priority: Minor Fix For: 4.0.2 When running bin/client, instance:connect or ssh:ssh, terminal size changes are not sent through SSH, leading to completion or commands that use the terminal width to not behave correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3955) Use of negative shell exit codes is not delux
Benson Margulies created KARAF-3955: --- Summary: Use of negative shell exit codes is not delux Key: KARAF-3955 URL: https://issues.apache.org/jira/browse/KARAF-3955 Project: Karaf Issue Type: Bug Reporter: Benson Margulies Priority: Minor Fix For: 4.0.1 Main.java has a set of calls like: System.exit(-1);. EXIT_FAILURE is '1', not '-1', and in general negative values aren't necessary, since the definition of 'oops' is 'not 0'. I propose that these be adjusted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-3955) Use of negative shell exit codes is not delux
[ https://issues.apache.org/jira/browse/KARAF-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-3955: --- Assignee: Jean-Baptiste Onofré Use of negative shell exit codes is not delux - Key: KARAF-3955 URL: https://issues.apache.org/jira/browse/KARAF-3955 Project: Karaf Issue Type: Bug Reporter: Benson Margulies Assignee: Jean-Baptiste Onofré Priority: Minor Fix For: 4.0.1 Main.java has a set of calls like: System.exit(-1);. EXIT_FAILURE is '1', not '-1', and in general negative values aren't necessary, since the definition of 'oops' is 'not 0'. I propose that these be adjusted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3956) should also add xalan into the endorse folder of distributions
Freeman Fang created KARAF-3956: --- Summary: should also add xalan into the endorse folder of distributions Key: KARAF-3956 URL: https://issues.apache.org/jira/browse/KARAF-3956 Project: Karaf Issue Type: Bug Reporter: Freeman Fang as we already endorse the xerces, we should endorse the xalan as well, to ensure the classes from xalan and xerces get loaded by same classloader -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-3956) should also add xalan into the endorse folder of distributions
[ https://issues.apache.org/jira/browse/KARAF-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-3956 started by Freeman Fang. --- should also add xalan into the endorse folder of distributions -- Key: KARAF-3956 URL: https://issues.apache.org/jira/browse/KARAF-3956 Project: Karaf Issue Type: Bug Reporter: Freeman Fang Assignee: Freeman Fang as we already endorse the xerces, we should endorse the xalan as well, to ensure the classes from xalan and xerces get loaded by same classloader -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-3956) should also add xalan into the endorse folder of distributions
[ https://issues.apache.org/jira/browse/KARAF-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-3956: --- Assignee: Freeman Fang should also add xalan into the endorse folder of distributions -- Key: KARAF-3956 URL: https://issues.apache.org/jira/browse/KARAF-3956 Project: Karaf Issue Type: Bug Reporter: Freeman Fang Assignee: Freeman Fang as we already endorse the xerces, we should endorse the xalan as well, to ensure the classes from xalan and xerces get loaded by same classloader -- This message was sent by Atlassian JIRA (v6.3.4#6332)
