[jira] [Resolved] (KARAF-4157) Provide system script to start Karaf without service wrapper
[ https://issues.apache.org/jira/browse/KARAF-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-4157. - Resolution: Fixed Fix Version/s: 4.0.5 4.1.0 patch applied on behalf of Luca Burgazzoli with thanks > Provide system script to start Karaf without service wrapper > > > Key: KARAF-4157 > URL: https://issues.apache.org/jira/browse/KARAF-4157 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Freeman Fang >Priority: Minor > Fix For: 4.1.0, 4.0.5 > > > For some user/scenario it may be needed to start karaf as a service without > the service wrapper i.e. on architectures not supported by JSW -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4157) Provide system script to start Karaf without service wrapper
[ https://issues.apache.org/jira/browse/KARAF-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101142#comment-15101142 ] ASF subversion and git services commented on KARAF-4157: Commit 3cb0a002fffcf2d90e8732922813dd4ebc15fb84 in karaf's branch refs/heads/master from [~ffang] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=3cb0a00 ] [KARAF-4157]adding license header (cherry picked from commit 13dfc233ffdc0991bf8c6ce8ce0ffb5d5e6bebe0) > Provide system script to start Karaf without service wrapper > > > Key: KARAF-4157 > URL: https://issues.apache.org/jira/browse/KARAF-4157 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Freeman Fang >Priority: Minor > > For some user/scenario it may be needed to start karaf as a service without > the service wrapper i.e. on architectures not supported by JSW -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4157) Provide system script to start Karaf without service wrapper
[ https://issues.apache.org/jira/browse/KARAF-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101136#comment-15101136 ] ASF subversion and git services commented on KARAF-4157: Commit 13dfc233ffdc0991bf8c6ce8ce0ffb5d5e6bebe0 in karaf's branch refs/heads/karaf-4.0.x from [~ffang] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=13dfc23 ] [KARAF-4157]adding license header > Provide system script to start Karaf without service wrapper > > > Key: KARAF-4157 > URL: https://issues.apache.org/jira/browse/KARAF-4157 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Freeman Fang >Priority: Minor > > For some user/scenario it may be needed to start karaf as a service without > the service wrapper i.e. on architectures not supported by JSW -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4157) Provide system script to start Karaf without service wrapper
[ https://issues.apache.org/jira/browse/KARAF-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101129#comment-15101129 ] ASF subversion and git services commented on KARAF-4157: Commit 4f600555c986d18990f884512e8d1fdaa2ca8c35 in karaf's branch refs/heads/karaf-4.0.x from [~lb] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=4f60055 ] KARAF-4157: Provide system script templates to start karaf without service wrapper (cherry picked from commit f8d510f59e3453cd648b378c079c2231e9fd4bea) > Provide system script to start Karaf without service wrapper > > > Key: KARAF-4157 > URL: https://issues.apache.org/jira/browse/KARAF-4157 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Freeman Fang >Priority: Minor > > For some user/scenario it may be needed to start karaf as a service without > the service wrapper i.e. on architectures not supported by JSW -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4157) Provide system script to start Karaf without service wrapper
[ https://issues.apache.org/jira/browse/KARAF-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101128#comment-15101128 ] ASF GitHub Bot commented on KARAF-4157: --- Github user asfgit closed the pull request at: https://github.com/apache/karaf/pull/113 > Provide system script to start Karaf without service wrapper > > > Key: KARAF-4157 > URL: https://issues.apache.org/jira/browse/KARAF-4157 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Freeman Fang >Priority: Minor > > For some user/scenario it may be needed to start karaf as a service without > the service wrapper i.e. on architectures not supported by JSW -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4157) Provide system script to start Karaf without service wrapper
[ https://issues.apache.org/jira/browse/KARAF-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101127#comment-15101127 ] ASF subversion and git services commented on KARAF-4157: Commit f8d510f59e3453cd648b378c079c2231e9fd4bea in karaf's branch refs/heads/master from [~lb] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=f8d510f ] KARAF-4157: Provide system script templates to start karaf without service wrapper > Provide system script to start Karaf without service wrapper > > > Key: KARAF-4157 > URL: https://issues.apache.org/jira/browse/KARAF-4157 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Freeman Fang >Priority: Minor > > For some user/scenario it may be needed to start karaf as a service without > the service wrapper i.e. on architectures not supported by JSW -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4269) Jetty logs backtrace for combination of jolokia and async
[
https://issues.apache.org/jira/browse/KARAF-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098823#comment-15098823
]
Achim Nierbeck commented on KARAF-4269:
---
I tend to close this, as this has been rather lengthly been investigated at the
Pax-Web project.
In the end it turned out to be an issue of Jetty itself, though in that case of
a jetty 8 issue. Don't know if this is also an issue with Jetty 9. But looks a
lot like:
https://ops4j1.jira.com/browse/PAXWEB-863
> Jetty logs backtrace for combination of jolokia and async
> -
>
> Key: KARAF-4269
> URL: https://issues.apache.org/jira/browse/KARAF-4269
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.4
>Reporter: Benson Margulies
>
> If I install the jolokia feature, plus my CXF 3.1.4 services that are async
> (use @Suspended AsyncResponse params), each call to my service results in the
> following in the log:
> {noformat}
> 2016-01-14 09:41:36,034 | WARN | qtp465679012-170 | HttpChannel
> | 197 - org.eclipse.jetty.util - 9.2.14.v20151106 |
> /rest/v1/morphology/parts-of-speech
> java.lang.IllegalStateException: STREAM
> at
> org.eclipse.jetty.server.Response.getWriter(Response.java:910)[194:org.eclipse.jetty.server:9.2.14.v20151106]
> at
> org.apache.cxf.transport.servlet.ServletController.generateNotFound(ServletController.java:247)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:184)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:180)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:293)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:212)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:707)[83:javax.servlet-api:3.1.0]
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:268)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)[195:org.eclipse.jetty.servlet:9.2.14.v20151106]
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)[195:org.eclipse.jetty.servlet:9.2.14.v20151106]
> at
> org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:70)[216:org.ops4j.pax.web.pax-web-jetty:4.2.4]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)[194:org.eclipse.jetty.server:9.2.14.v20151106]
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)[193:org.eclipse.jetty.security:9.2.14.v20151106]
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)[194:org.eclipse.jetty.server:9.2.14.v20151106]
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)[194:org.eclipse.jetty.server:9.2.14.v20151106]
> at
> org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:271)[216:org.ops4j.pax.web.pax-web-jetty:4.2.4]
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)[195:org.eclipse.jetty.servlet:9.2.14.v20151106]
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)[194:org.eclipse.jetty.server:9.2.14.v20151106]
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)[194:org.eclipse.jetty.server:9.2.14.v20151106]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)[194:org.eclipse.jetty.server:9.2.14.v20151106]
> at
> org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:99)[216:org.ops4j.pax.web.pax-web-jetty:4.2.4]
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)[194:org.eclipse.jetty.server:9.2.14.v20151106]
> at
> org.eclipse.jetty.server.Server.handleAsync(Server.java:549)[194:org.eclipse.jetty.server:9.2.14.v20151106]
> at
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:318)[194:org.eclipse.jetty.server:9.2.14.v20151106]
> at
> org.eclipse.jetty.server.HttpChannel.run(HttpChannel.ja
[jira] [Commented] (KARAF-4222) Add a flag to add-features-to-repo and install-kar to include conditions
[ https://issues.apache.org/jira/browse/KARAF-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098652#comment-15098652 ] Amichai Rothman commented on KARAF-4222: I see it was indeed added only in 4.0.4. Now that it's released I tried it and it looks ok. Perhaps backward-compatibility-breaking changes like this one (needing an extra config flag that wasn't necessary before) should be mentioned in the release notes... just a thought. Thanks for the fix! > Add a flag to add-features-to-repo and install-kar to include conditions > > > Key: KARAF-4222 > URL: https://issues.apache.org/jira/browse/KARAF-4222 > Project: Karaf > Issue Type: Improvement > Components: karaf-tooling >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > > Right now, the add-features-to-repo goal (and depending of the config, the > install-kar one) doesn't include the conditional artifacts in the resulting > system folder. > It may cause issue to create an offline-ready distribution. > I will add a flag in the add-features-to-repo and install-kar goals to > include all conditional resources. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4272) Karaf freezes when a circular dependency is introduced where a feature references itself over a chain of other features
[
https://issues.apache.org/jira/browse/KARAF-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Hauser updated KARAF-4272:
-
Summary: Karaf freezes when a circular dependency is introduced where a
feature references itself over a chain of other features (was: Karaf freezes
when a circular dependency is introduced where a features references itself
over a chain of other features)
> Karaf freezes when a circular dependency is introduced where a feature
> references itself over a chain of other features
> ---
>
> Key: KARAF-4272
> URL: https://issues.apache.org/jira/browse/KARAF-4272
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.4
>Reporter: Roland Hauser
>
> Karaf freezes when a circular dependency is introduced where a features
> references itself over a chain of other features
> I did some experiments with circular dependencies where a feature references
> itself indirectly over some other features. In this case it does not matter
> if attribute {{prerequisite}} is set or not. After command {{feature:install
> c-references-a}} Karaf freezes and must be restarted.
>
> I would expect, that the feature:install command fails with an error message
> like this:
> "Feature com.foo.bar could not be installed because a circular reference:
> a-references-b
> b-references-c
> c-references-a"
> You can checkout a project which helps to reproduce the case from
> [https://github.com/SourcePond/reproduce-feature-circular-dependency.git]
> (Maven-Modules c-references-a and c-references-a-prerequisite-true). Simply
> install the root-project to have all necessary Maven dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4272) Karaf freezes when a circular dependency is introduced where a features references itself over a chain of other features
Roland Hauser created KARAF-4272:
Summary: Karaf freezes when a circular dependency is introduced
where a features references itself over a chain of other features
Key: KARAF-4272
URL: https://issues.apache.org/jira/browse/KARAF-4272
Project: Karaf
Issue Type: Bug
Components: karaf-feature
Affects Versions: 4.0.4
Reporter: Roland Hauser
Karaf freezes when a circular dependency is introduced where a features
references itself over a chain of other features
I did some experiments with circular dependencies where a feature references
itself indirectly over some other features. In this case it does not matter if
attribute {{prerequisite}} is set or not. After command {{feature:install
c-references-a}} Karaf freezes and must be restarted.
I would expect, that the feature:install command fails with an error message
like this:
"Feature com.foo.bar could not be installed because a circular reference:
a-references-b
b-references-c
c-references-a"
You can checkout a project which helps to reproduce the case from
[https://github.com/SourcePond/reproduce-feature-circular-dependency.git]
(Maven-Modules c-references-a and c-references-a-prerequisite-true). Simply
install the root-project to have all necessary Maven dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4271) Circular dependency not handled properly when a feature references itself directly
[
https://issues.apache.org/jira/browse/KARAF-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Hauser updated KARAF-4271:
-
Description:
I did some experiments with circular dependencies where a feature references
itself directly. When attribute {{prerequisite}} is set to {{false}} then the
feature install succeeds with following log-message
{code}
2016-01-14 17:44:25,509 | INFO | e user appsrvadm | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Adding features:
self-circular-dependency/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
2016-01-14 17:44:25,795 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | No deployment change.
2016-01-14 17:44:25,803 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Done.
{code}
When {{prerequisite}} is set to {{true}}, the feature installation fails with a
StackOverFlowError:
{code}
java.lang.StackOverflowError
at
org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:117)
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:103)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
...
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]}}
{code}
I would expect in both cases, that the feature:install command fails with an
error message like this: "Feature com.foo.bar could not be installed because it
references itself"
You can checkout a project which helps to reproduce the case from
[https://github.com/SourcePond/reproduce-feature-circular-dependency.git]
(Maven-Modules self-circular-dependency and
self-circular-dependency-prerequisite-true). Simply install the root-project to
have all necessary Maven dependencies.
was:
I did some experiments with circular dependencies where a feature references
itself directly. When attribute {{prerequisite}} is set to {{false}} then the
feature install succeeds with following log-message
2016-01-14 17:44:25,509 | INFO | e user appsrvadm | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Adding features:
self-circular-dependency/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
2016-01-14 17:44:25,795 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | No deployment change.
2016-01-14 17:44:25,803 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Done.
When prerequisite is set to true, the feature installation fails with a
StackOverFlowError:
{code}
java.lang.StackOverflowError
at
org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:117)
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:103)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.d
[jira] [Updated] (KARAF-4271) Circular dependency not handled properly when a feature references itself directly
[
https://issues.apache.org/jira/browse/KARAF-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Hauser updated KARAF-4271:
-
Description:
I did some experiments with circular dependencies where a feature references
itself directly. When attribute {{prerequisite}} is set to {{false}} then the
feature install succeeds with following log-message
2016-01-14 17:44:25,509 | INFO | e user appsrvadm | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Adding features:
self-circular-dependency/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
2016-01-14 17:44:25,795 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | No deployment change.
2016-01-14 17:44:25,803 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Done.
When prerequisite is set to true, the feature installation fails with a
StackOverFlowError:
{code}
java.lang.StackOverflowError
at
org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:117)
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:103)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
...
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]}}
{code}
I would expect in both cases, that the feature:install command fails with an
error message like this: "Feature com.foo.bar could not be installed because it
references itself"
You can checkout a project which helps to reproduce the case from
[https://github.com/SourcePond/reproduce-feature-circular-dependency.git]
(Maven-Modules self-circular-dependency and
self-circular-dependency-prerequisite-true). Simply install the root-project to
have all necessary Maven dependencies.
was:
I did some experiments with circular dependencies where a feature references
itself directly. When attribute {{prerequisite}} is set to {{false}} then the
feature install succeeds with following log-message
2016-01-14 17:44:25,509 | INFO | e user appsrvadm | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Adding features:
self-circular-dependency/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
2016-01-14 17:44:25,795 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | No deployment change.
2016-01-14 17:44:25,803 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Done.
When prerequisite is set to true, the feature installation fails with a
StackOverFlowError:
{{java.lang.StackOverflowError
at
org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:117)
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:103)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
[jira] [Updated] (KARAF-4271) Circular dependency not handled properly when a feature references itself directly
[
https://issues.apache.org/jira/browse/KARAF-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Hauser updated KARAF-4271:
-
Description:
I did some experiments with circular dependencies where a feature references
itself directly. When attribute {{prerequisite}} is set to {{false}} then the
feature install succeeds with following log-message
2016-01-14 17:44:25,509 | INFO | e user appsrvadm | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Adding features:
self-circular-dependency/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
2016-01-14 17:44:25,795 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | No deployment change.
2016-01-14 17:44:25,803 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Done.
When prerequisite is set to true, the feature installation fails with a
StackOverFlowError:
{{java.lang.StackOverflowError
at
org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:117)
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:103)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
...
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]}}
I would expect in both cases, that the feature:install command fails with an
error message like this: "Feature com.foo.bar could not be installed because it
references itself"
You can checkout a project which helps to reproduce the case from
[https://github.com/SourcePond/reproduce-feature-circular-dependency.git]
(Maven-Modules self-circular-dependency and
self-circular-dependency-prerequisite-true). Simply install the root-project to
have all necessary Maven dependencies.
was:
I did some experiments with circular dependencies where a feature references
itself directly. When attribute {{prerequisite}} is set to {{false}} then the
feature install succeeds with following log-message
2016-01-14 17:44:25,509 | INFO | e user appsrvadm | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Adding features:
self-circular-dependency/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
2016-01-14 17:44:25,795 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | No deployment change.
2016-01-14 17:44:25,803 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Done.
When prerequisite is set to true, the feature installation fails with a
StackOverFlowError:
java.lang.StackOverflowError
at
org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:117)
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:103)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
[jira] [Created] (KARAF-4271) Circular dependency not handled properly when a feature references itself directly
Roland Hauser created KARAF-4271:
Summary: Circular dependency not handled properly when a feature
references itself directly
Key: KARAF-4271
URL: https://issues.apache.org/jira/browse/KARAF-4271
Project: Karaf
Issue Type: Bug
Components: karaf-feature
Affects Versions: 4.0.4
Reporter: Roland Hauser
I did some experiments with circular dependencies where a feature references
itself directly. When attribute {{prerequisite}} is set to {{false}} then the
feature install succeeds with following log-message
{{
2016-01-14 17:44:25,509 | INFO | e user appsrvadm | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Adding features:
self-circular-dependency/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
2016-01-14 17:44:25,795 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | No deployment change.
2016-01-14 17:44:25,803 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Done.
}}
When prerequisite is set to true, the feature installation fails with a
StackOverFlowError:
{{
java.lang.StackOverflowError
at
org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:117)
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:103)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
...
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
}}
I would expect in both cases, that the feature:install command fails with an
error message like this: "Feature com.foo.bar could not be installed because it
references itself"
You can checkout a project which helps to reproduce the case from
[https://github.com/SourcePond/reproduce-feature-circular-dependency.git]
(Maven-Modules self-circular-dependency and
self-circular-dependency-prerequisite-true). Simply install the root-project to
have all necessary Maven dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4271) Circular dependency not handled properly when a feature references itself directly
[
https://issues.apache.org/jira/browse/KARAF-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Hauser updated KARAF-4271:
-
Description:
I did some experiments with circular dependencies where a feature references
itself directly. When attribute {{prerequisite}} is set to {{false}} then the
feature install succeeds with following log-message
2016-01-14 17:44:25,509 | INFO | e user appsrvadm | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Adding features:
self-circular-dependency/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
2016-01-14 17:44:25,795 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | No deployment change.
2016-01-14 17:44:25,803 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Done.
When prerequisite is set to true, the feature installation fails with a
StackOverFlowError:
java.lang.StackOverflowError
at
org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:117)
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:103)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
...
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
I would expect in both cases, that the feature:install command fails with an
error message like this: "Feature com.foo.bar could not be installed because it
references itself"
You can checkout a project which helps to reproduce the case from
[https://github.com/SourcePond/reproduce-feature-circular-dependency.git]
(Maven-Modules self-circular-dependency and
self-circular-dependency-prerequisite-true). Simply install the root-project to
have all necessary Maven dependencies.
was:
I did some experiments with circular dependencies where a feature references
itself directly. When attribute {{prerequisite}} is set to {{false}} then the
feature install succeeds with following log-message
{{
2016-01-14 17:44:25,509 | INFO | e user appsrvadm | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Adding features:
self-circular-dependency/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
2016-01-14 17:44:25,795 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | No deployment change.
2016-01-14 17:44:25,803 | INFO | pool-47-thread-1 | FeaturesServiceImpl
| 7 - org.apache.karaf.features.core - 4.0.4 | Done.
}}
When prerequisite is set to true, the feature installation fails with a
StackOverFlowError:
{{
java.lang.StackOverflowError
at
org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:117)
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:103)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
[jira] [Created] (KARAF-4270) Shell-compat gets NPE trying to give help for combo of local and compat commands
Benson Margulies created KARAF-4270:
---
Summary: Shell-compat gets NPE trying to give help for combo of
local and compat commands
Key: KARAF-4270
URL: https://issues.apache.org/jira/browse/KARAF-4270
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.4
Reporter: Benson Margulies
{noformat}
karaf@root>help scr
pipe: java.lang.NullPointerException
karaf@root>
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4269) Jetty logs backtrace for combination of jolokia and async
Benson Margulies created KARAF-4269:
---
Summary: Jetty logs backtrace for combination of jolokia and async
Key: KARAF-4269
URL: https://issues.apache.org/jira/browse/KARAF-4269
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.4
Reporter: Benson Margulies
If I install the jolokia feature, plus my CXF 3.1.4 services that are async
(use @Suspended AsyncResponse params), each call to my service results in the
following in the log:
{noformat}
2016-01-14 09:41:36,034 | WARN | qtp465679012-170 | HttpChannel
| 197 - org.eclipse.jetty.util - 9.2.14.v20151106 |
/rest/v1/morphology/parts-of-speech
java.lang.IllegalStateException: STREAM
at
org.eclipse.jetty.server.Response.getWriter(Response.java:910)[194:org.eclipse.jetty.server:9.2.14.v20151106]
at
org.apache.cxf.transport.servlet.ServletController.generateNotFound(ServletController.java:247)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:184)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:180)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:293)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:212)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:707)[83:javax.servlet-api:3.1.0]
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:268)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)[195:org.eclipse.jetty.servlet:9.2.14.v20151106]
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)[195:org.eclipse.jetty.servlet:9.2.14.v20151106]
at
org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:70)[216:org.ops4j.pax.web.pax-web-jetty:4.2.4]
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)[194:org.eclipse.jetty.server:9.2.14.v20151106]
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)[193:org.eclipse.jetty.security:9.2.14.v20151106]
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)[194:org.eclipse.jetty.server:9.2.14.v20151106]
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)[194:org.eclipse.jetty.server:9.2.14.v20151106]
at
org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:271)[216:org.ops4j.pax.web.pax-web-jetty:4.2.4]
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)[195:org.eclipse.jetty.servlet:9.2.14.v20151106]
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)[194:org.eclipse.jetty.server:9.2.14.v20151106]
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)[194:org.eclipse.jetty.server:9.2.14.v20151106]
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)[194:org.eclipse.jetty.server:9.2.14.v20151106]
at
org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:99)[216:org.ops4j.pax.web.pax-web-jetty:4.2.4]
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)[194:org.eclipse.jetty.server:9.2.14.v20151106]
at
org.eclipse.jetty.server.Server.handleAsync(Server.java:549)[194:org.eclipse.jetty.server:9.2.14.v20151106]
at
org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:318)[194:org.eclipse.jetty.server:9.2.14.v20151106]
at
org.eclipse.jetty.server.HttpChannel.run(HttpChannel.java:262)[194:org.eclipse.jetty.server:9.2.14.v20151106]
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[197:org.eclipse.jetty.util:9.2.14.v20151106]
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)[197:org.eclipse.jetty.util:9.2.14.v20151106]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_60]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4253) Two EntityManagers present if two hibernate bundles are available
[ https://issues.apache.org/jira/browse/KARAF-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved KARAF-4253. Resolution: Won't Fix It seems this behaviour is expected by the spec. Unfortunately I did not get responses from the OSGi-dev list. > Two EntityManagers present if two hibernate bundles are available > - > > Key: KARAF-4253 > URL: https://issues.apache.org/jira/browse/KARAF-4253 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Christian Niehues >Assignee: Christian Schneider > > If two hibernate bundles are active in karaf two EntityManager will be > available for each datasource. > ID | State | Lvl | Version | Name > - > 52 | Active | 80 | 1.1.0 | ClassMate > 53 | Active | 80 | 3.18.1.GA | Javassist > 55 | Active | 80 | 1.2.0 | CDI APIs > 56 | Active | 80 | 1.2 | javax.interceptor API > 58 | Active | 80 | 2.1.0.v201304241213 | Java Persistence API 2.1 > 60 | Active | 80 | 1.2 | javax.transaction API > 62 | Active | 80 | 1.0.0.SNAPSHOT | angular-ui > 63 | Active | 80 | 1.0.0.SNAPSHOT | model > 64 | Active | 80 | 1.0.0.SNAPSHOT | persistence > 65 | Active | 80 | 1.0.0.SNAPSHOT | service > 71 | Active | 80 | 2.2.0 | Apache Aries JPA Container API > 72 | Active | 80 | 2.2.0 | Apache Aries JPA blueprint > 73 | Active | 80 | 2.2.0 | Apache Aries JPA container > 74 | Active | 80 | 2.2.0 | Apache Aries JPA support > 75 | Active | 80 | 1.1.1 | Apache Aries Transaction Blueprint > 76 | Active | 80 | 2.0.0 | Apache Aries Transaction Blueprint > 77 | Active | 80 | 1.3.0 | Apache Aries Transaction Manager > 78 | Active | 80 | 2.1.0 | Apache Commons DBCP > 79 | Active | 80 | 2.4.1 | Apache Commons Pool > 89 | Active | 80 | 1.0.0 | Apache Felix Coordinator Service > 95 | Active | 80 | 1.8.2.2 | Apache ServiceMix :: Bundles :: ant > 96 | Active | 80 | 2.7.7.5 | Apache ServiceMix :: Bundles :: > antlr > 97 | Active | 80 | 3.0.0.1 | Apache ServiceMix :: Bundles :: > cglib > 98 | Active | 80 | 1.6.1.5 | Apache ServiceMix :: Bundles :: > dom4j > 100 | Active | 80 | 1.0.0.2 | Apache ServiceMix :: Bundles :: > javax.inject > 136 | Active | 80 | 1.3.172 | H2 Database Engine > 137 | Active | 80 | 4.0.4.Final | hibernate-commons-annotations > 138 | Active | 80 | 4.3.6.Final | hibernate-core > 139 | Active | 80 | 4.3.6.Final | hibernate-entitymanager > 140 | Active | 80 | 4.3.6.Final | hibernate-osgi > 143 | Active | 80 | 1.0.2.Final | JACC 1.4 API > 144 | Active | 80 | 0.7.0 | OPS4J Pax JDBC Config > 145 | Active | 80 | 0.7.0 | OPS4J Pax JDBC Pooling Support Base > 146 | Active | 80 | 0.7.0 | OPS4J Pax JDBC Pooling Support > using Commons-DBCP2 > 156 | Active | 80 | 1.0.0.201505202023 | org.osgi:org.osgi.service.jdbc > 159 | Active | 80 | 5.0.6.Final-karaf | hibernate-osgi > 160 | Active | 80 | 1.1.1 | geronimo-jta_1.1_spec > 161 | Active | 80 | 5.0.1.Final | hibernate-commons-annotations > 162 | Active | 80 | 5.0.6.Final | hibernate-core > 163 | Active | 80 | 5.0.6.Final | hibernate-entitymanager > 164 | Active | 80 | 1.0.0.Final | hibernate-jpa-2.1-api > 165 | Active | 80 | 5.0.6.Final | hibernate-osgi > 166 | Active | 80 | 2.0.0.Final | Java Annotation Indexer > 167 | Active | 80 | 3.3.0.Final | JBoss Logging 3 > karaf@root()> ls EntityManager > [javax.persistence.EntityManager] > - > osgi.unit.name = tasklist > service.bundleid = 63 > service.id = 202 > service.scope = singleton > Provided by : > model (63) > Used by: > persistence (64) > [javax.persistence.EntityManager] > - > osgi.unit.name = tasklist > service.bundleid = 63 > service.id = 211 > service.scope = singleton > Provided by : > model (63) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4157) Provide system script to start Karaf without service wrapper
[ https://issues.apache.org/jira/browse/KARAF-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098075#comment-15098075 ] Luca Burgazzoli commented on KARAF-4157: Now squashed in a single commit > Provide system script to start Karaf without service wrapper > > > Key: KARAF-4157 > URL: https://issues.apache.org/jira/browse/KARAF-4157 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Freeman Fang >Priority: Minor > > For some user/scenario it may be needed to start karaf as a service without > the service wrapper i.e. on architectures not supported by JSW -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4180) Document overrides configuration
[ https://issues.apache.org/jira/browse/KARAF-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved KARAF-4180. Resolution: Fixed > Document overrides configuration > > > Key: KARAF-4180 > URL: https://issues.apache.org/jira/browse/KARAF-4180 > Project: Karaf > Issue Type: Documentation > Components: karaf-documentation, karaf-feature >Affects Versions: 4.0.3 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: 4.0.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4180) Document overrides configuration
[ https://issues.apache.org/jira/browse/KARAF-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098063#comment-15098063 ] ASF subversion and git services commented on KARAF-4180: Commit c0c373d1b42855914a763f54bf2f458e2569416b in karaf's branch refs/heads/master from [~ch...@die-schneider.net] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=c0c373d ] [KARAF-4180] Overrides documentation > Document overrides configuration > > > Key: KARAF-4180 > URL: https://issues.apache.org/jira/browse/KARAF-4180 > Project: Karaf > Issue Type: Documentation > Components: karaf-documentation, karaf-feature >Affects Versions: 4.0.3 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: 4.0.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-2752) Provide a way to override bundles at feature installation time
[
https://issues.apache.org/jira/browse/KARAF-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098064#comment-15098064
]
ASF subversion and git services commented on KARAF-2752:
Commit 84b1981fe26f974414c9b7e7b768fddc8c1cd1db in karaf's branch
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=84b1981 ]
[KARAF-2752] Small refactoring
> Provide a way to override bundles at feature installation time
> --
>
> Key: KARAF-2752
> URL: https://issues.apache.org/jira/browse/KARAF-2752
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 3.0.1
>
>
> This would be very beneficial when trying to provide some kind of "patched"
> distributions of Karaf and based applications.
> When installing features, if you want to modify a bundle, the only way is to
> release a new feature file which can be problematic, especially when the
> target bundle is a transitive dependency, because you then need to release
> multiple features descriptors in various projects.
> The idea is to provide a simple file in etc/overrides.properties which will
> contain a list of bundle urls to consider as replacements when installing
> features. Before installation, bundles will be scanned for matching
> overrides.
> Matching is done so that the target and override bundles must have the same
> symbolic name and the target bundle version must has the same major and minor
> version than the override bundle. This version range can be specified
> manually using something like:
> {code}
> url;range="[2,3)"
> {code}
> in which case, any target bundle matching the version range and the symbolic
> name will be overriden.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4268) Documentation has obsolete jetty configuration
[
https://issues.apache.org/jira/browse/KARAF-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098026#comment-15098026
]
Jean-Baptiste Onofré commented on KARAF-4268:
-
Part is documented:
http://karaf.apache.org/manual/latest/users-guide/webcontainer.html
I will improve there as well.
Thanks.
> Documentation has obsolete jetty configuration
> --
>
> Key: KARAF-4268
> URL: https://issues.apache.org/jira/browse/KARAF-4268
> Project: Karaf
> Issue Type: Bug
> Components: karaf-documentation
>Reporter: Benson Margulies
>Assignee: Jean-Baptiste Onofré
>
> {noformat}
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.jetty.server.nio.SelectChannelConnector not found by
> org.eclipse.jetty.server [137]
> {noformat}
> resulted from following the example at
> https://karaf.apache.org/manual/latest/users-guide/tuning.html
> The correct replacement is:
> {code}
>
>
>
>
>
>
> 8282
> metrics
>
>
>
>
> {code}
> Also note that this doc neglects to mention to need to point to this file
> from the pax-web .cfg file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4266) Upgrade to Spring 4.2.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4266. - Resolution: Fixed > Upgrade to Spring 4.2.4.RELEASE > --- > > Key: KARAF-4266 > URL: https://issues.apache.org/jira/browse/KARAF-4266 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 3.0.6, 4.0.5 > > > I'll push commit for this. > Actually I'm unable to assign issue to myself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4266) Upgrade to Spring 4.2.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098024#comment-15098024 ] ASF subversion and git services commented on KARAF-4266: Commit 4bd9e95130924dfefc6a240205e3e979e2d98db1 in karaf's branch refs/heads/karaf-3.0.x from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=4bd9e95 ] KARAF-4266 - Upgrade to Spring 4.2.4.RELEASE > Upgrade to Spring 4.2.4.RELEASE > --- > > Key: KARAF-4266 > URL: https://issues.apache.org/jira/browse/KARAF-4266 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 3.0.6, 4.0.5 > > > I'll push commit for this. > Actually I'm unable to assign issue to myself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4266) Upgrade to Spring 4.2.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098013#comment-15098013 ] ASF subversion and git services commented on KARAF-4266: Commit d8ff3a3cae8439a45553208c0c51a6bb077575c8 in karaf's branch refs/heads/karaf-4.0.x from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=d8ff3a3 ] KARAF-4266 - Upgrade to Spring 4.2.4.RELEASE > Upgrade to Spring 4.2.4.RELEASE > --- > > Key: KARAF-4266 > URL: https://issues.apache.org/jira/browse/KARAF-4266 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 3.0.6, 4.0.5 > > > I'll push commit for this. > Actually I'm unable to assign issue to myself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4268) Documentation has obsolete jetty configuration
[
https://issues.apache.org/jira/browse/KARAF-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4268:
Summary: Documentation has obsolete jetty configuration (was: Website has
obsolete jetty configuration)
> Documentation has obsolete jetty configuration
> --
>
> Key: KARAF-4268
> URL: https://issues.apache.org/jira/browse/KARAF-4268
> Project: Karaf
> Issue Type: Bug
> Components: karaf-documentation
>Reporter: Benson Margulies
>Assignee: Jean-Baptiste Onofré
>
> {noformat}
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.jetty.server.nio.SelectChannelConnector not found by
> org.eclipse.jetty.server [137]
> {noformat}
> resulted from following the example at
> https://karaf.apache.org/manual/latest/users-guide/tuning.html
> The correct replacement is:
> {code}
>
>
>
>
>
>
> 8282
> metrics
>
>
>
>
> {code}
> Also note that this doc neglects to mention to need to point to this file
> from the pax-web .cfg file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4268) Website has obsolete jetty configuration
[
https://issues.apache.org/jira/browse/KARAF-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4268:
Component/s: karaf-documentation
> Website has obsolete jetty configuration
>
>
> Key: KARAF-4268
> URL: https://issues.apache.org/jira/browse/KARAF-4268
> Project: Karaf
> Issue Type: Bug
> Components: karaf-documentation
>Reporter: Benson Margulies
>Assignee: Jean-Baptiste Onofré
>
> {noformat}
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.jetty.server.nio.SelectChannelConnector not found by
> org.eclipse.jetty.server [137]
> {noformat}
> resulted from following the example at
> https://karaf.apache.org/manual/latest/users-guide/tuning.html
> The correct replacement is:
> {code}
>
>
>
>
>
>
> 8282
> metrics
>
>
>
>
> {code}
> Also note that this doc neglects to mention to need to point to this file
> from the pax-web .cfg file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (KARAF-4268) Website has obsolete jetty configuration
[
https://issues.apache.org/jira/browse/KARAF-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-4268:
---
Assignee: Jean-Baptiste Onofré
> Website has obsolete jetty configuration
>
>
> Key: KARAF-4268
> URL: https://issues.apache.org/jira/browse/KARAF-4268
> Project: Karaf
> Issue Type: Bug
>Reporter: Benson Margulies
>Assignee: Jean-Baptiste Onofré
>
> {noformat}
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.jetty.server.nio.SelectChannelConnector not found by
> org.eclipse.jetty.server [137]
> {noformat}
> resulted from following the example at
> https://karaf.apache.org/manual/latest/users-guide/tuning.html
> The correct replacement is:
> {code}
>
>
>
>
>
>
> 8282
> metrics
>
>
>
>
> {code}
> Also note that this doc neglects to mention to need to point to this file
> from the pax-web .cfg file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4268) Website has obsolete jetty configuration
Benson Margulies created KARAF-4268:
---
Summary: Website has obsolete jetty configuration
Key: KARAF-4268
URL: https://issues.apache.org/jira/browse/KARAF-4268
Project: Karaf
Issue Type: Bug
Reporter: Benson Margulies
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.eclipse.jetty.server.nio.SelectChannelConnector not found by
org.eclipse.jetty.server [137]
{noformat}
resulted from following the example at
https://karaf.apache.org/manual/latest/users-guide/tuning.html
The correct replacement is:
{code}
8282
metrics
{code}
Also note that this doc neglects to mention to need to point to this file from
the pax-web .cfg file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4157) Provide system script to start Karaf without service wrapper
[
https://issues.apache.org/jira/browse/KARAF-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097999#comment-15097999
]
Luca Burgazzoli commented on KARAF-4157:
Implemented via
[5ee6a6964267f129a9bd1cfbde1e67f650121218|https://github.com/lburgazzoli/apache-karaf/commit/5ee6a6964267f129a9bd1cfbde1e67f650121218]
{code}
$ tar tvf ./assemblies/apache-karaf/target/apache-karaf-4.0.4-SNAPSHOT.tar.gz |
grep contrib
drwxr-xr-x 0/0 0 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/
-rwxr-xr-x 0/0 542 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-template.systemd
-rwxr-xr-x 0/02587 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-template.solaris-smf
-rwxr-xr-x 0/01541 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-win.xml
-rwxr-xr-x 0/02969 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-template.init
-rwxr-xr-x 0/03394 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-template.init-redhat
-rwxr-xr-x 0/0 360 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-template.conf
-rwxr-xr-x 0/05515 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-template.init-debian
-rwxr-xr-x 0/0 59392 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-win.exe
-rwxr-xr-x 0/05599 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service.sh
{code}
> Provide system script to start Karaf without service wrapper
>
>
> Key: KARAF-4157
> URL: https://issues.apache.org/jira/browse/KARAF-4157
> Project: Karaf
> Issue Type: New Feature
>Reporter: Luca Burgazzoli
>Assignee: Freeman Fang
>Priority: Minor
>
> For some user/scenario it may be needed to start karaf as a service without
> the service wrapper i.e. on architectures not supported by JSW
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3880) Provide a standard feature just wrapping all boot features from the standard distribution
[ https://issues.apache.org/jira/browse/KARAF-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097968#comment-15097968 ] Christian Schneider commented on KARAF-3880: For documentation : The feature "standard" represents the karaf standard feature set and "minimal" represents the minimal distro feature set. > Provide a standard feature just wrapping all boot features from the standard > distribution > - > > Key: KARAF-3880 > URL: https://issues.apache.org/jira/browse/KARAF-3880 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 4.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.4 > > > In order to simplify creation of custom distribution 'on top' of Karaf, it > would be great to provide (*again*) the standard feature containing all > standard distribution boot features. > Else, the users have to know the list of all features (shell, > aries-blueprint, etc). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4159) FeatureResolver: Wrong dependencies installed
[
https://issues.apache.org/jira/browse/KARAF-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097903#comment-15097903
]
J. Brébec commented on KARAF-4159:
--
a note on this issue : spring 3.1.4 is not installed with this patch, but the
jar should be present in production : karaf try to download spring 3.1.4.
i have to package it in my distribution in order to work in "offline mode"
(without a maven repository).
> FeatureResolver: Wrong dependencies installed
> -
>
> Key: KARAF-4159
> URL: https://issues.apache.org/jira/browse/KARAF-4159
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.3
> Environment: Reproduced in MacOS (JRE1.8) or Windows 7 (JRE 1.7)
>Reporter: J. Brébec
>Assignee: Guillaume Nodet
>Priority: Critical
> Fix For: 4.0.4
>
>
> In a fresh Karaf 4.0.3 installation
> 1. install spring/3.2.14.RELEASE_1
> {code}
> feature:install spring/3.2.14.RELEASE_1
> {code}
> 2. test an installation of spring-dm. Randomly, Karaf try to install spring
> 3.1.4.RELEASE
> {code}
> karaf@root()> feature:install -t -v spring-dm
> Adding features: spring-dm/[1.2.1,1.2.1]
> Changes to perform:
> Region: root
> Bundles to install:
> mvn:org.apache.karaf.bundle/org.apache.karaf.bundle.springstate/4.0.3
>
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.cglib/3.0_1
> mvn:org.springframework/spring-aop/3.1.4.RELEASE
> mvn:org.springframework/spring-asm/3.1.4.RELEASE
> mvn:org.springframework/spring-beans/3.1.4.RELEASE
> mvn:org.springframework/spring-context/3.1.4.RELEASE
> mvn:org.springframework/spring-context-support/3.1.4.RELEASE
> mvn:org.springframework/spring-core/3.1.4.RELEASE
> mvn:org.springframework/spring-expression/3.1.4.RELEASE
> mvn:org.springframework.osgi/spring-osgi-core/1.2.1
> mvn:org.springframework.osgi/spring-osgi-extender/1.2.1
> mvn:org.springframework.osgi/spring-osgi-annotation/1.2.1
> mvn:org.springframework.osgi/spring-osgi-io/1.2.1
> Bundles to refresh:
> org.apache.servicemix.bundles.spring-aop/3.2.14.RELEASE_1 (Wired to
> org.apache.servicemix.bundles.spring-core/3.2.14.RELEASE_1 which is being
> refreshed)
> org.apache.servicemix.bundles.spring-beans/3.2.14.RELEASE_1 (Wired to
> org.apache.servicemix.bundles.spring-core/3.2.14.RELEASE_1 which is being
> refreshed)
> org.apache.servicemix.bundles.spring-context/3.2.14.RELEASE_1 (Wired to
> org.apache.servicemix.bundles.spring-aop/3.2.14.RELEASE_1 which is being
> refreshed)
> org.apache.servicemix.bundles.spring-context-support/3.2.14.RELEASE_1
> (Wired to org.apache.servicemix.bundles.spring-beans/3.2.14.RELEASE_1 which
> is being refreshed)
> org.apache.servicemix.bundles.spring-core/3.2.14.RELEASE_1 (Should be
> wired to: org.apache.servicemix.bundles.cglib/3.0.0.1 (through
> [org.apache.servicemix.bundles.spring-core/3.2.14.RELEASE_1]
> osgi.wiring.package;
> filter:="(&(osgi.wiring.package=net.sf.cglib.beans)(version>=3.0.0)(!(version>=4.0.0)))";
> resolution:=optional))
> org.apache.servicemix.bundles.spring-expression/3.2.14.RELEASE_1 (Wired
> to org.apache.servicemix.bundles.spring-core/3.2.14.RELEASE_1 which is being
> refreshed)
> {code}
> Note: This can happen too when installing spring and spring-dm in the same
> command or in a boot feature (staged or not).
> 3. install any unrelated feature (when spring-dm has installed spring 3.1) :
> Karaf uninstall spring 3.1 and refresh the world
> {code}
> karaf@root()> feature:install -t -v scheduler
> Adding features: scheduler/[4.0.3,4.0.3]
> Changes to perform:
> Region: root
> Bundles to uninstall:
> org.springframework.expression/3.1.4.RELEASE
> org.springframework.context.support/3.1.4.RELEASE
> org.springframework.core/3.1.4.RELEASE
> org.springframework.beans/3.1.4.RELEASE
> org.springframework.context/3.1.4.RELEASE
> org.springframework.aop/3.1.4.RELEASE
> org.springframework.asm/3.1.4.RELEASE
> Bundles to install:
> mvn:org.apache.karaf.scheduler/org.apache.karaf.scheduler.core/4.0.3
> Bundles to refresh:
> org.springframework.aop/3.1.4.RELEASE (Bundle will be uninstalled)
> org.springframework.asm/3.1.4.RELEASE (Bundle will be uninstalled)
> org.springframework.beans/3.1.4.RELEASE (Bundle will be uninstalled)
> org.springframework.context/3.1.4.RELEASE (Bundle will be uninstalled)
> org.springframework.context.support/3.1.4.RELEASE (Bundle will be
> uninstalled)
> org.springframework.core/3.1.4.RELEASE (Bundle will be uninstalled)
> org.springframework.expression/3.1.4.RELEASE (Bundle will be uninstalled)
> {code}
> this is critical in my environment :
[jira] [Commented] (KARAF-4266) Upgrade to Spring 4.2.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097886#comment-15097886 ] ASF subversion and git services commented on KARAF-4266: Commit 67744469abb5760e62db6e328b990360eb505c00 in karaf's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=6774446 ] KARAF-4266 - Upgrade to Spring 4.2.4.RELEASE > Upgrade to Spring 4.2.4.RELEASE > --- > > Key: KARAF-4266 > URL: https://issues.apache.org/jira/browse/KARAF-4266 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 3.0.6, 4.0.5 > > > I'll push commit for this. > Actually I'm unable to assign issue to myself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4267) Remove derby config from windows karaf.bat
[ https://issues.apache.org/jira/browse/KARAF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4267: Fix Version/s: (was: 2.x) 2.4.4 > Remove derby config from windows karaf.bat > -- > > Key: KARAF-4267 > URL: https://issues.apache.org/jira/browse/KARAF-4267 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 2.4.4, 3.0.6, 4.0.5 > > > The windows version of the launch script configures derby. > I assume it is not used, because it is not done in linux, so this should be > probably removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4267) Remove derby config from windows karaf.bat
[ https://issues.apache.org/jira/browse/KARAF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4267. - Resolution: Fixed > Remove derby config from windows karaf.bat > -- > > Key: KARAF-4267 > URL: https://issues.apache.org/jira/browse/KARAF-4267 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 2.4.4, 3.0.6, 4.0.5 > > > The windows version of the launch script configures derby. > I assume it is not used, because it is not done in linux, so this should be > probably removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4267) Remove derby config from windows karaf.bat
[ https://issues.apache.org/jira/browse/KARAF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097811#comment-15097811 ] ASF subversion and git services commented on KARAF-4267: Commit 3ace2b875b6314988f4427e8cb91f925f4927e01 in karaf's branch refs/heads/karaf-2.x from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=3ace2b8 ] KARAF-4267 - Remove unused derby references > Remove derby config from windows karaf.bat > -- > > Key: KARAF-4267 > URL: https://issues.apache.org/jira/browse/KARAF-4267 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 2.x, 4.1.0, 3.0.6, 4.0.5 > > > The windows version of the launch script configures derby. > I assume it is not used, because it is not done in linux, so this should be > probably removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4267) Remove derby config from windows karaf.bat
[ https://issues.apache.org/jira/browse/KARAF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4267: Fix Version/s: 2.x > Remove derby config from windows karaf.bat > -- > > Key: KARAF-4267 > URL: https://issues.apache.org/jira/browse/KARAF-4267 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 2.x, 4.1.0, 3.0.6, 4.0.5 > > > The windows version of the launch script configures derby. > I assume it is not used, because it is not done in linux, so this should be > probably removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4267) Remove derby config from windows karaf.bat
[ https://issues.apache.org/jira/browse/KARAF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4267: Fix Version/s: 3.0.6 > Remove derby config from windows karaf.bat > -- > > Key: KARAF-4267 > URL: https://issues.apache.org/jira/browse/KARAF-4267 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 3.0.6, 4.0.5 > > > The windows version of the launch script configures derby. > I assume it is not used, because it is not done in linux, so this should be > probably removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4267) Remove derby config from windows karaf.bat
[ https://issues.apache.org/jira/browse/KARAF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097805#comment-15097805 ] ASF subversion and git services commented on KARAF-4267: Commit cf76a9a8b865dd4f6fed38dc51c32e6888aa1b1e in karaf's branch refs/heads/karaf-3.0.x from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=cf76a9a ] KARAF-4267 - Remove unused derby references > Remove derby config from windows karaf.bat > -- > > Key: KARAF-4267 > URL: https://issues.apache.org/jira/browse/KARAF-4267 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 3.0.6, 4.0.5 > > > The windows version of the launch script configures derby. > I assume it is not used, because it is not done in linux, so this should be > probably removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4267) Remove derby config from windows karaf.bat
[ https://issues.apache.org/jira/browse/KARAF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097802#comment-15097802 ] ASF subversion and git services commented on KARAF-4267: Commit b44f04be758c7cd516d7b8a0f8d133f2da86d337 in karaf's branch refs/heads/karaf-4.0.x from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=b44f04b ] KARAF-4267 - Remove unused derby references > Remove derby config from windows karaf.bat > -- > > Key: KARAF-4267 > URL: https://issues.apache.org/jira/browse/KARAF-4267 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.5 > > > The windows version of the launch script configures derby. > I assume it is not used, because it is not done in linux, so this should be > probably removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4267) Remove derby config from windows karaf.bat
[ https://issues.apache.org/jira/browse/KARAF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4267: Fix Version/s: 4.0.5 > Remove derby config from windows karaf.bat > -- > > Key: KARAF-4267 > URL: https://issues.apache.org/jira/browse/KARAF-4267 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.5 > > > The windows version of the launch script configures derby. > I assume it is not used, because it is not done in linux, so this should be > probably removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4266) Upgrade to Spring 4.2.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4266: Fix Version/s: 3.0.6 > Upgrade to Spring 4.2.4.RELEASE > --- > > Key: KARAF-4266 > URL: https://issues.apache.org/jira/browse/KARAF-4266 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 3.0.6, 4.0.5 > > > I'll push commit for this. > Actually I'm unable to assign issue to myself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4267) Remove derby config from windows karaf.bat
[ https://issues.apache.org/jira/browse/KARAF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4267: Fix Version/s: 4.1.0 > Remove derby config from windows karaf.bat > -- > > Key: KARAF-4267 > URL: https://issues.apache.org/jira/browse/KARAF-4267 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.5 > > > The windows version of the launch script configures derby. > I assume it is not used, because it is not done in linux, so this should be > probably removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4266) Upgrade to Spring 4.2.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-4266: --- Assignee: Jean-Baptiste Onofré > Upgrade to Spring 4.2.4.RELEASE > --- > > Key: KARAF-4266 > URL: https://issues.apache.org/jira/browse/KARAF-4266 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 3.0.6, 4.0.5 > > > I'll push commit for this. > Actually I'm unable to assign issue to myself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4267) Remove derby config from windows karaf.bat
[ https://issues.apache.org/jira/browse/KARAF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097800#comment-15097800 ] ASF subversion and git services commented on KARAF-4267: Commit 767627e9934f0499da70a1e7c38491ccd101ed35 in karaf's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=767627e ] KARAF-4267 - Remove unused derby references > Remove derby config from windows karaf.bat > -- > > Key: KARAF-4267 > URL: https://issues.apache.org/jira/browse/KARAF-4267 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.5 > > > The windows version of the launch script configures derby. > I assume it is not used, because it is not done in linux, so this should be > probably removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4267) Remove derby config from windows karaf.bat
[ https://issues.apache.org/jira/browse/KARAF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-4267: --- Assignee: Jean-Baptiste Onofré > Remove derby config from windows karaf.bat > -- > > Key: KARAF-4267 > URL: https://issues.apache.org/jira/browse/KARAF-4267 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré >Priority: Minor > > The windows version of the launch script configures derby. > I assume it is not used, because it is not done in linux, so this should be > probably removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4267) Remove derby config from windows karaf.bat
[ https://issues.apache.org/jira/browse/KARAF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097799#comment-15097799 ] Jean-Baptiste Onofré commented on KARAF-4267: - Good catch, it comes from an old old old old old time ;) > Remove derby config from windows karaf.bat > -- > > Key: KARAF-4267 > URL: https://issues.apache.org/jira/browse/KARAF-4267 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré >Priority: Minor > > The windows version of the launch script configures derby. > I assume it is not used, because it is not done in linux, so this should be > probably removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
