[jira] [Resolved] (KARAF-4355) suppress wrap without error
[ https://issues.apache.org/jira/browse/KARAF-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved KARAF-4355. - Resolution: Invalid > suppress wrap without error > --- > > Key: KARAF-4355 > URL: https://issues.apache.org/jira/browse/KARAF-4355 > Project: Karaf > Issue Type: New Feature >Reporter: Benson Margulies > > We run into a lot of maven artifacts that contain OSGi metadata but have > spurious non-OSGi dependencies. Generally, they are jars that somehow are > incorporated into the artifact. > As things are, we laboriously maintain export lists to avoid the wraps. > We would be happy to just suppress 'wrapping', and take our lumps from > missing packages if one of these things actually turns out to be necessary > when we test it. > If I don't see an unhappy comment on this, I'll make a PR for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4167) Accidently shared config files diagnosed
[ https://issues.apache.org/jira/browse/KARAF-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved KARAF-4167. - Resolution: Invalid > Accidently shared config files diagnosed > > > Key: KARAF-4167 > URL: https://issues.apache.org/jira/browse/KARAF-4167 > Project: Karaf > Issue Type: Improvement >Reporter: Benson Margulies > > If you stupidly tell two different @Components to use the same > configurationPid, one of them will just get stuck, and neither > bundle:services nor any of the scr commands will reveal what the problem is. > It sure would be nice to have a log message, or some detail from one of the > commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4741) karaf-maven-plugin creates 'wrap' bundle specs for non-jar dependencies
Benson Margulies created KARAF-4741:
---
Summary: karaf-maven-plugin creates 'wrap' bundle specs for
non-jar dependencies
Key: KARAF-4741
URL: https://issues.apache.org/jira/browse/KARAF-4741
Project: Karaf
Issue Type: Improvement
Affects Versions: 4.0.6
Reporter: Benson Margulies
For reasons of managing bnd default, I have a dependency:
{code}
mygroup
myartifact
bnd
{code}
this is a text file (a bnd.bnd file, to be exact).
I was bemused to discover:
wrap_file__Users_benson_x_rosapi1.5_assemblies_full-test_target_assembly_system_com_basistech_buildtools_14.1.1_buildtools-14.1.1.bnd
in my bundle list: the maven plugin has asked the wrap feature to convert my
text file into an OSGi bundle.
I submit that it would be better if the maven plugin excluded this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4462) Allow control of attachment of generated assembly artifacts
Benson Margulies created KARAF-4462:
---
Summary: Allow control of attachment of generated assembly
artifacts
Key: KARAF-4462
URL: https://issues.apache.org/jira/browse/KARAF-4462
Project: Karaf
Issue Type: New Feature
Affects Versions: 4.0.4
Reporter: Benson Margulies
It would be helpful to be able to say {{false}} to create
an assembly and not make it part of the project. It would be helpful to be able
to specify a classifier. Both of these are useful when using the assembly or
archive goal without using a packaging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4355) suppress wrap without error
Benson Margulies created KARAF-4355: --- Summary: suppress wrap without error Key: KARAF-4355 URL: https://issues.apache.org/jira/browse/KARAF-4355 Project: Karaf Issue Type: New Feature Reporter: Benson Margulies We run into a lot of maven artifacts that contain OSGi metadata but have spurious non-OSGi dependencies. Generally, they are jars that somehow are incorporated into the artifact. As things are, we laboriously maintain export lists to avoid the wraps. We would be happy to just suppress 'wrapping', and take our lumps from missing packages if one of these things actually turns out to be necessary when we test it. If I don't see an unhappy comment on this, I'll make a PR for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4270) Shell-compat gets NPE trying to give help for combo of local and compat commands
[
https://issues.apache.org/jira/browse/KARAF-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101832#comment-15101832
]
Benson Margulies commented on KARAF-4270:
-
Backporting to 4.0.x would make sense, of course.
> 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-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] [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] [Created] (KARAF-4183) Plain gogo commands (for scr) don't work from the karaf shell
Benson Margulies created KARAF-4183:
---
Summary: Plain gogo commands (for scr) don't work from the karaf
shell
Key: KARAF-4183
URL: https://issues.apache.org/jira/browse/KARAF-4183
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.2
Reporter: Benson Margulies
{noformat}
araf@root>bundle:list -t 0 | grep -i scr
104 | Active | 80 | 3.1.2 | Apache CXF JAX-RS Service
Description
127 | Active | 30 | 4.0.2 | Apache Karaf :: SCR :: Shell
Commands
128 | Active | 30 | 4.0.2 | Apache Karaf :: SCR ::
Management MBeans
karaf@root>bundle:uninstall 127
karaf@root>bundle:uninstall 128
{noformat}
restart the Karaf.
Try to use 'scr:info' from the Felix scr bundle. Not found. but:
{noformat}
karaf@root>bundle:services -p 107
Apache Felix Declarative Services (107) provides:
-
objectClass = [org.osgi.service.cm.ConfigurationListener]
service.bundleid = 107
service.description = Declarative Services Configuration Support Listener
service.id = 56
service.scope = singleton
service.vendor = The Apache Software Foundation
objectClass = [org.osgi.service.component.runtime.ServiceComponentRuntime]
service.bundleid = 107
service.id = 57
service.scope = singleton
objectClass = [org.apache.felix.scr.impl.ScrGogoCommand]
osgi.command.function = [config, disable, enable, info, list]
osgi.command.scope = scr
service.bundleid = 107
service.description = SCR Gogo Shell Support
service.id = 58
service.scope = singleton
service.vendor = The Apache Software Foundation
objectClass = [org.osgi.service.cm.ManagedService]
service.bundleid = 107
service.description = SCR Configurator
service.id = 59
service.pid = org.apache.felix.scr.ScrService
service.scope = bundle
service.vendor = The Apache Software Foundation
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4181) blacklist.properties is not a properties file
Benson Margulies created KARAF-4181: --- Summary: blacklist.properties is not a properties file Key: KARAF-4181 URL: https://issues.apache.org/jira/browse/KARAF-4181 Project: Karaf Issue Type: Bug Reporter: Benson Margulies It's confusing that a file named 'blacklist.properties' does not, in fact, contain a properties file. Rather, it's just a list of blacklisted bundles. It seems to me that the name 'blacklist.properties' might be deprecated and the name 'bundle-blacklist.txt' would be more informative. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4176) client jar should not contain an slf4j binding
Benson Margulies created KARAF-4176: --- Summary: client jar should not contain an slf4j binding Key: KARAF-4176 URL: https://issues.apache.org/jira/browse/KARAF-4176 Project: Karaf Issue Type: Bug Reporter: Benson Margulies The following is a bad thing, I claim. Logging bindings should be left to the overall application. SLF4J: Found binding in [jar:file:/Users/benson/.m2/repository/org/apache/karaf/org.apache.karaf.client/4.0.2/org.apache.karaf.client-4.0.2.jar!/org/slf4j/impl/StaticLoggerBinder.class] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4167) Accidently shared config files diagnosed
Benson Margulies created KARAF-4167: --- Summary: Accidently shared config files diagnosed Key: KARAF-4167 URL: https://issues.apache.org/jira/browse/KARAF-4167 Project: Karaf Issue Type: Improvement Reporter: Benson Margulies If you stupidly tell two different @Components to use the same configurationPid, one of them will just get stuck, and neither bundle:services nor any of the scr commands will reveal what the problem is. It sure would be nice to have a log message, or some detail from one of the commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3967) Seemingly simple Karaf application fails with equinox as framework
[
https://issues.apache.org/jira/browse/KARAF-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022423#comment-15022423
]
Benson Margulies commented on KARAF-3967:
-
So you can no longer repro this with
g...@github.com:bimargulies/karaf-loop-tc.git?
> Seemingly simple Karaf application fails with equinox as framework
> --
>
> Key: KARAF-3967
> URL: https://issues.apache.org/jira/browse/KARAF-3967
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.1
> Environment: Java 1.8.
>Reporter: Benson Margulies
>
> If you clone g...@github.com:bimargulies/karaf-loop-tc.git, and checkout the
> 'equinox' branch, and run mvn install with Maven 3.2.5, you will see the
> following exception, followed by the test hanging. jstack shows all karaf
> threads sitting around, none of them are doing anything. Eventually, pax-exam
> gives up and quits.
> {noformat}
> 2015-09-01 11:02:07,533 | WARN | pool-1-thread-1 | Activator
> | 8 - org.apache.karaf.features.core - 4.0.1 | Error starting
> activator
> java.lang.IllegalStateException: BundleContext is no longer valid
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.checkValid(BundleContextImpl.java:983)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:463)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
> at
> org.apache.karaf.util.tracker.BaseActivator.registerMBean(BaseActivator.java:290)[8:org.apache.karaf.features.core:4.0.1]
> at
> org.apache.karaf.features.internal.osgi.Activator.doStart(Activator.java:262)[8:org.apache.karaf.features.core:4.0.1]
> at
> org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:233)[8:org.apache.karaf.features.core:4.0.1]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_05]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_05]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_05]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_05]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_05]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4102) It should be possible to change the primary feature name to be other than the artifact id
Benson Margulies created KARAF-4102: --- Summary: It should be possible to change the primary feature name to be other than the artifact id Key: KARAF-4102 URL: https://issues.apache.org/jira/browse/KARAF-4102 Project: Karaf Issue Type: Improvement Reporter: Benson Margulies In some cases it would be handy to be able to create a feature whose name is not the same as project.artifactId and which receives the dependencies (and main artifact). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4102) It should be possible to change the primary feature name to be other than the artifact id
[ https://issues.apache.org/jira/browse/KARAF-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996719#comment-14996719 ] Benson Margulies commented on KARAF-4102: - https://github.com/apache/karaf/pull/90 is the pull request. > It should be possible to change the primary feature name to be other than the > artifact id > - > > Key: KARAF-4102 > URL: https://issues.apache.org/jira/browse/KARAF-4102 > Project: Karaf > Issue Type: Improvement >Reporter: Benson Margulies > > In some cases it would be handy to be able to create a feature whose name is > not the same as project.artifactId and which receives the dependencies (and > main artifact). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4071) Tell me what bundle has a version 1 manifest, please.
[ https://issues.apache.org/jira/browse/KARAF-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved KARAF-4071. - Resolution: Invalid > Tell me what bundle has a version 1 manifest, please. > - > > Key: KARAF-4071 > URL: https://issues.apache.org/jira/browse/KARAF-4071 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.0.2 >Reporter: Benson Margulies > > Caused by: org.osgi.framework.BundleException: Unable to build resource for > mvn:com.basistech.ws/rosapi-worker-res-sdk/1.5.0-SNAPSHOT: Unsupported > 'Bundle-ManifestVersion' value: 1 > at > org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[6:org.apache.karaf.features.core:4.0.2] > at > org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:69)[6:org.apache.karaf.features.core:4.0.2] > at > org.apache.karaf.features.internal.region.Subsystem.createResource(Subsystem.java:565)[6:org.apache.karaf.features.core:4.0.2] > ... 15 more > Caused by: org.osgi.framework.BundleException: Unsupported > 'Bundle-ManifestVersion' value: 1 > at > org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[6:org.apache.karaf.features.core:4.0.2] > at > org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[6:org.apache.karaf.features.core:4.0.2] > ... 17 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4103) It should be possible to forbid the use of 'wrap'
Benson Margulies created KARAF-4103: --- Summary: It should be possible to forbid the use of 'wrap' Key: KARAF-4103 URL: https://issues.apache.org/jira/browse/KARAF-4103 Project: Karaf Issue Type: Improvement Reporter: Benson Margulies The feature plugin cheerfully creates 'wrap' instructions whenever it sees a dependency that is not a bundle. Some of us really don't want to use wrap. I propose a boolean parameter to forbid and fail when a wrap would be needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4071) Tell me what bundle has a version 1 manifest, please.
Benson Margulies created KARAF-4071: --- Summary: Tell me what bundle has a version 1 manifest, please. Key: KARAF-4071 URL: https://issues.apache.org/jira/browse/KARAF-4071 Project: Karaf Issue Type: Improvement Affects Versions: 4.0.2 Reporter: Benson Margulies Caused by: org.osgi.framework.BundleException: Unable to build resource for mvn:com.basistech.ws/rosapi-worker-res-sdk/1.5.0-SNAPSHOT: Unsupported 'Bundle-ManifestVersion' value: 1 at org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[6:org.apache.karaf.features.core:4.0.2] at org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:69)[6:org.apache.karaf.features.core:4.0.2] at org.apache.karaf.features.internal.region.Subsystem.createResource(Subsystem.java:565)[6:org.apache.karaf.features.core:4.0.2] ... 15 more Caused by: org.osgi.framework.BundleException: Unsupported 'Bundle-ManifestVersion' value: 1 at org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[6:org.apache.karaf.features.core:4.0.2] at org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[6:org.apache.karaf.features.core:4.0.2] ... 17 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3967) Seemingly simple Karaf application fails with equinox as framework
[
https://issues.apache.org/jira/browse/KARAF-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14946683#comment-14946683
]
Benson Margulies commented on KARAF-3967:
-
:-) I did push you a test case :-). I'll try it out.
> Seemingly simple Karaf application fails with equinox as framework
> --
>
> Key: KARAF-3967
> URL: https://issues.apache.org/jira/browse/KARAF-3967
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.1
> Environment: Java 1.8.
>Reporter: Benson Margulies
>
> If you clone g...@github.com:bimargulies/karaf-loop-tc.git, and checkout the
> 'equinox' branch, and run mvn install with Maven 3.2.5, you will see the
> following exception, followed by the test hanging. jstack shows all karaf
> threads sitting around, none of them are doing anything. Eventually, pax-exam
> gives up and quits.
> {noformat}
> 2015-09-01 11:02:07,533 | WARN | pool-1-thread-1 | Activator
> | 8 - org.apache.karaf.features.core - 4.0.1 | Error starting
> activator
> java.lang.IllegalStateException: BundleContext is no longer valid
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.checkValid(BundleContextImpl.java:983)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:463)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
> at
> org.apache.karaf.util.tracker.BaseActivator.registerMBean(BaseActivator.java:290)[8:org.apache.karaf.features.core:4.0.1]
> at
> org.apache.karaf.features.internal.osgi.Activator.doStart(Activator.java:262)[8:org.apache.karaf.features.core:4.0.1]
> at
> org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:233)[8:org.apache.karaf.features.core:4.0.1]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_05]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_05]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_05]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_05]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_05]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3967) Seemingly simple Karaf application fails with equinox as framework
[
https://issues.apache.org/jira/browse/KARAF-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14946686#comment-14946686
]
Benson Margulies commented on KARAF-3967:
-
I can't get the current snapshot.
ERROR] Failed to execute goal on project tc-itest: Could not resolve
dependencies for project org.apache.karaf:tc-itest:jar:0.0.1-SNAPSHOT: Failed
to collect dependencies at
org.ops4j.pax.exam:pax-exam-junit4:jar:4.7.0-SNAPSHOT: Failed to read artifact
descriptor for org.ops4j.pax.exam:pax-exam-junit4:jar:4.7.0-SNAPSHOT: Could not
find artifact org.ops4j:master:pom:4.3.0-SNAPSHOT in ops4j-snapshots
(https://oss.sonatype.org/content/repositories/ops4j-snapshots) -> [Help 1]
> Seemingly simple Karaf application fails with equinox as framework
> --
>
> Key: KARAF-3967
> URL: https://issues.apache.org/jira/browse/KARAF-3967
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.1
> Environment: Java 1.8.
>Reporter: Benson Margulies
>
> If you clone g...@github.com:bimargulies/karaf-loop-tc.git, and checkout the
> 'equinox' branch, and run mvn install with Maven 3.2.5, you will see the
> following exception, followed by the test hanging. jstack shows all karaf
> threads sitting around, none of them are doing anything. Eventually, pax-exam
> gives up and quits.
> {noformat}
> 2015-09-01 11:02:07,533 | WARN | pool-1-thread-1 | Activator
> | 8 - org.apache.karaf.features.core - 4.0.1 | Error starting
> activator
> java.lang.IllegalStateException: BundleContext is no longer valid
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.checkValid(BundleContextImpl.java:983)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:463)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
> at
> org.apache.karaf.util.tracker.BaseActivator.registerMBean(BaseActivator.java:290)[8:org.apache.karaf.features.core:4.0.1]
> at
> org.apache.karaf.features.internal.osgi.Activator.doStart(Activator.java:262)[8:org.apache.karaf.features.core:4.0.1]
> at
> org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:233)[8:org.apache.karaf.features.core:4.0.1]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_05]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_05]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_05]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_05]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_05]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3982) Be able to change standard files during distribution assembly
[ https://issues.apache.org/jira/browse/KARAF-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14905666#comment-14905666 ] Benson Margulies commented on KARAF-3982: - Gosh, I thought I ran a complete build successfully once. > Be able to change standard files during distribution assembly > - > > Key: KARAF-3982 > URL: https://issues.apache.org/jira/browse/KARAF-3982 > Project: Karaf > Issue Type: Improvement > Components: karaf-tooling >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > > The Karaf Maven plugin generates files (etc/org.apache.karaf.features.cfg, > etc). It would be great to mimic pax-exam to be able to change these > generated files (like put/append instructions). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3995) installAllFeaturesByDefault is not documented
Benson Margulies created KARAF-3995: --- Summary: installAllFeaturesByDefault is not documented Key: KARAF-3995 URL: https://issues.apache.org/jira/browse/KARAF-3995 Project: Karaf Issue Type: Bug Components: karaf-tooling Affects Versions: 4.0.1 Reporter: Benson Margulies @Parameter protected boolean installAllFeaturesByDefault = true; has no javadoc, so no documentation at all. What does it do? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3982) Be able to change standard files during distribution assembly
[ https://issues.apache.org/jira/browse/KARAF-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744589#comment-14744589 ] Benson Margulies commented on KARAF-3982: - I added a flag as an attribute of the operation element. > Be able to change standard files during distribution assembly > - > > Key: KARAF-3982 > URL: https://issues.apache.org/jira/browse/KARAF-3982 > Project: Karaf > Issue Type: Improvement > Components: karaf-tooling >Reporter: Jean-Baptiste Onofré > > The Karaf Maven plugin generates files (etc/org.apache.karaf.features.cfg, > etc). It would be great to mimic pax-exam to be able to change these > generated files (like put/append instructions). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3982) Be able to change standard files during distribution assembly
[ https://issues.apache.org/jira/browse/KARAF-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742442#comment-14742442 ] Benson Margulies commented on KARAF-3982: - [~jbonofre] Did you notice this? for some reason the PR didn't tag itself here. > Be able to change standard files during distribution assembly > - > > Key: KARAF-3982 > URL: https://issues.apache.org/jira/browse/KARAF-3982 > Project: Karaf > Issue Type: Improvement > Components: karaf-tooling >Reporter: Jean-Baptiste Onofré > > The Karaf Maven plugin generates files (etc/org.apache.karaf.features.cfg, > etc). It would be great to mimic pax-exam to be able to change these > generated files (like put/append instructions). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3982) Be able to change standard files during distribution assembly
[
https://issues.apache.org/jira/browse/KARAF-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14737011#comment-14737011
]
Benson Margulies commented on KARAF-3982:
-
https://github.com/apache/karaf/pull/80 seems done except for the issue I asked
for help on.
Here's how this works: You create:
src/main/karaf/assembly-property-edits.xml
to look for something like:
{code}
http://karaf.apache.org/tools/property-edits/1.0.0;>
config.properties
put
karaf.framework
equinox
config.properties
extend
org.osgi.framework.system.capabilities
my-magic-capability
{code}
> Be able to change standard files during distribution assembly
> -
>
> Key: KARAF-3982
> URL: https://issues.apache.org/jira/browse/KARAF-3982
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
>Reporter: Jean-Baptiste Onofré
>
> The Karaf Maven plugin generates files (etc/org.apache.karaf.features.cfg,
> etc). It would be great to mimic pax-exam to be able to change these
> generated files (like put/append instructions).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3982) Be able to change standard files during distribution assembly
[
https://issues.apache.org/jira/browse/KARAF-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14736982#comment-14736982
]
Benson Margulies commented on KARAF-3982:
-
[~jbonofre] How to I add a new bundle to the profiles?
{noformat}
Message: Unable to resolve root: missing requirement [root] osgi.identity;
osgi.identity=profile; type=karaf.feature; version=4.0.2.SNAPSHOT;
filter:="(&(osgi.identity=profile)(type=karaf.feature)(version>=4.0.2.SNAPSHOT))"
[caused by: Unable to resolve profile/4.0.2.SNAPSHOT: missing requirement
[profile/4.0.2.SNAPSHOT] osgi.identity;
osgi.identity=org.apache.karaf.profile.core; type=osgi.bundle;
version="[4.0.2.SNAPSHOT,4.0.2.SNAPSHOT]"; resolution:=mandatory [caused by:
Unable to resolve org.apache.karaf.profile.core/4.0.2.SNAPSHOT: missing
requirement [org.apache.karaf.profile.core/4.0.2.SNAPSHOT] osgi.wiring.package;
filter:="(&(osgi.wiring.package=org.apache.karaf.tools.utils)(version>=4.0.0)(!(version>=5.0.0)))"]]
{noformat}
> Be able to change standard files during distribution assembly
> -
>
> Key: KARAF-3982
> URL: https://issues.apache.org/jira/browse/KARAF-3982
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
>Reporter: Jean-Baptiste Onofré
>
> The Karaf Maven plugin generates files (etc/org.apache.karaf.features.cfg,
> etc). It would be great to mimic pax-exam to be able to change these
> generated files (like put/append instructions).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (KARAF-3982) Be able to change standard files during distribution assembly
[
https://issues.apache.org/jira/browse/KARAF-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14737011#comment-14737011
]
Benson Margulies edited comment on KARAF-3982 at 9/9/15 3:49 PM:
-
https://github.com/apache/karaf/pull/80 seems done.
Here's how this works: You create:
src/main/karaf/assembly-property-edits.xml
to look for something like:
{code}
http://karaf.apache.org/tools/property-edits/1.0.0;>
config.properties
put
karaf.framework
equinox
config.properties
extend
org.osgi.framework.system.capabilities
my-magic-capability
{code}
'put' and 'extend' are the usual verbs from the pax-exam container.
Note that this creates a new JAR file that could be used in pax-exam to avoid a
DRY violation.
was (Author: bmargulies):
https://github.com/apache/karaf/pull/80 seems done except for the issue I asked
for help on.
Here's how this works: You create:
src/main/karaf/assembly-property-edits.xml
to look for something like:
{code}
http://karaf.apache.org/tools/property-edits/1.0.0;>
config.properties
put
karaf.framework
equinox
config.properties
extend
org.osgi.framework.system.capabilities
my-magic-capability
{code}
'put' and 'extend' are the usual verbs from the pax-exam container.
Note that this creates a new JAR file that could be used in pax-exam to avoid a
DRY violation.
> Be able to change standard files during distribution assembly
> -
>
> Key: KARAF-3982
> URL: https://issues.apache.org/jira/browse/KARAF-3982
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
>Reporter: Jean-Baptiste Onofré
>
> The Karaf Maven plugin generates files (etc/org.apache.karaf.features.cfg,
> etc). It would be great to mimic pax-exam to be able to change these
> generated files (like put/append instructions).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (KARAF-3982) Be able to change standard files during distribution assembly
[
https://issues.apache.org/jira/browse/KARAF-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated KARAF-3982:
Comment: was deleted
(was: [~jbonofre] How to I add a new bundle to the profiles?
{noformat}
Message: Unable to resolve root: missing requirement [root] osgi.identity;
osgi.identity=profile; type=karaf.feature; version=4.0.2.SNAPSHOT;
filter:="(&(osgi.identity=profile)(type=karaf.feature)(version>=4.0.2.SNAPSHOT))"
[caused by: Unable to resolve profile/4.0.2.SNAPSHOT: missing requirement
[profile/4.0.2.SNAPSHOT] osgi.identity;
osgi.identity=org.apache.karaf.profile.core; type=osgi.bundle;
version="[4.0.2.SNAPSHOT,4.0.2.SNAPSHOT]"; resolution:=mandatory [caused by:
Unable to resolve org.apache.karaf.profile.core/4.0.2.SNAPSHOT: missing
requirement [org.apache.karaf.profile.core/4.0.2.SNAPSHOT] osgi.wiring.package;
filter:="(&(osgi.wiring.package=org.apache.karaf.tools.utils)(version>=4.0.0)(!(version>=5.0.0)))"]]
{noformat}
)
> Be able to change standard files during distribution assembly
> -
>
> Key: KARAF-3982
> URL: https://issues.apache.org/jira/browse/KARAF-3982
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
>Reporter: Jean-Baptiste Onofré
>
> The Karaf Maven plugin generates files (etc/org.apache.karaf.features.cfg,
> etc). It would be great to mimic pax-exam to be able to change these
> generated files (like put/append instructions).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (KARAF-3982) Be able to change standard files during distribution assembly
[
https://issues.apache.org/jira/browse/KARAF-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14737011#comment-14737011
]
Benson Margulies edited comment on KARAF-3982 at 9/9/15 3:12 PM:
-
https://github.com/apache/karaf/pull/80 seems done except for the issue I asked
for help on.
Here's how this works: You create:
src/main/karaf/assembly-property-edits.xml
to look for something like:
{code}
http://karaf.apache.org/tools/property-edits/1.0.0;>
config.properties
put
karaf.framework
equinox
config.properties
extend
org.osgi.framework.system.capabilities
my-magic-capability
{code}
'put' and 'extend' are the usual verbs from the pax-exam container.
Note that this creates a new JAR file that could be used in pax-exam to avoid a
DRY violation.
was (Author: bmargulies):
https://github.com/apache/karaf/pull/80 seems done except for the issue I asked
for help on.
Here's how this works: You create:
src/main/karaf/assembly-property-edits.xml
to look for something like:
{code}
http://karaf.apache.org/tools/property-edits/1.0.0;>
config.properties
put
karaf.framework
equinox
config.properties
extend
org.osgi.framework.system.capabilities
my-magic-capability
{code}
> Be able to change standard files during distribution assembly
> -
>
> Key: KARAF-3982
> URL: https://issues.apache.org/jira/browse/KARAF-3982
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
>Reporter: Jean-Baptiste Onofré
>
> The Karaf Maven plugin generates files (etc/org.apache.karaf.features.cfg,
> etc). It would be great to mimic pax-exam to be able to change these
> generated files (like put/append instructions).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-3977) Control D should not exit in mid-line-edit
Benson Margulies created KARAF-3977: --- Summary: Control D should not exit in mid-line-edit Key: KARAF-3977 URL: https://issues.apache.org/jira/browse/KARAF-3977 Project: Karaf Issue Type: Bug Reporter: Benson Margulies In all the shells I know, typing control-D only exits if you have no text typed into the input editor. If you are in mid-line, it just deletes forward. So I keep killing karaf. Can we fix this? I took a look at where the fix might live and failed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3969) assembly goal has no way to set javase version
Benson Margulies created KARAF-3969: --- Summary: assembly goal has no way to set javase version Key: KARAF-3969 URL: https://issues.apache.org/jira/browse/KARAF-3969 Project: Karaf Issue Type: Bug Reporter: Benson Margulies I'm calling it a bug because it makes it impossible to build anything that requires 1.8. Patch to follow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3968) The assembly mojo does not respect --offline
Benson Margulies created KARAF-3968: --- Summary: The assembly mojo does not respect --offline Key: KARAF-3968 URL: https://issues.apache.org/jira/browse/KARAF-3968 Project: Karaf Issue Type: Bug Components: karaf-tooling Affects Versions: 4.0.1 Reporter: Benson Margulies Patch coming. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3967) Seemingly simple Karaf application fails with equinox as framework
Benson Margulies created KARAF-3967:
---
Summary: Seemingly simple Karaf application fails with equinox as
framework
Key: KARAF-3967
URL: https://issues.apache.org/jira/browse/KARAF-3967
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.1
Environment: Java 1.8.
Reporter: Benson Margulies
If you clone g...@github.com:bimargulies/karaf-loop-tc.git, and checkout the
'equinox' branch, and run mvn install with Maven 3.2.5, you will see the
following exception, followed by the test hanging. jstack shows all karaf
threads sitting around, none of them are doing anything. Eventually, pax-exam
gives up and quits.
{noformat}
2015-09-01 11:02:07,533 | WARN | pool-1-thread-1 | Activator
| 8 - org.apache.karaf.features.core - 4.0.1 | Error starting activator
java.lang.IllegalStateException: BundleContext is no longer valid
at
org.eclipse.osgi.internal.framework.BundleContextImpl.checkValid(BundleContextImpl.java:983)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
at
org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:463)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
at
org.apache.karaf.util.tracker.BaseActivator.registerMBean(BaseActivator.java:290)[8:org.apache.karaf.features.core:4.0.1]
at
org.apache.karaf.features.internal.osgi.Activator.doStart(Activator.java:262)[8:org.apache.karaf.features.core:4.0.1]
at
org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:233)[8:org.apache.karaf.features.core:4.0.1]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_05]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_05]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_05]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_05]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_05]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3967) Seemingly simple Karaf application fails with equinox as framework
[
https://issues.apache.org/jira/browse/KARAF-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725565#comment-14725565
]
Benson Margulies commented on KARAF-3967:
-
The 'hang' aspect of this is presumably
https://ops4j1.jira.com/browse/PAXEXAM-731.
Having captured a log to 'foo', {{grep -i refresh ~/foo}} yields no results.
So it looks like no refreshes.
> Seemingly simple Karaf application fails with equinox as framework
> --
>
> Key: KARAF-3967
> URL: https://issues.apache.org/jira/browse/KARAF-3967
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.1
> Environment: Java 1.8.
>Reporter: Benson Margulies
>
> If you clone g...@github.com:bimargulies/karaf-loop-tc.git, and checkout the
> 'equinox' branch, and run mvn install with Maven 3.2.5, you will see the
> following exception, followed by the test hanging. jstack shows all karaf
> threads sitting around, none of them are doing anything. Eventually, pax-exam
> gives up and quits.
> {noformat}
> 2015-09-01 11:02:07,533 | WARN | pool-1-thread-1 | Activator
> | 8 - org.apache.karaf.features.core - 4.0.1 | Error starting
> activator
> java.lang.IllegalStateException: BundleContext is no longer valid
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.checkValid(BundleContextImpl.java:983)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:463)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
> at
> org.apache.karaf.util.tracker.BaseActivator.registerMBean(BaseActivator.java:290)[8:org.apache.karaf.features.core:4.0.1]
> at
> org.apache.karaf.features.internal.osgi.Activator.doStart(Activator.java:262)[8:org.apache.karaf.features.core:4.0.1]
> at
> org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:233)[8:org.apache.karaf.features.core:4.0.1]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_05]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_05]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_05]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_05]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_05]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-3963) Some slight improvements to the doc for the feature generation mojo.
Benson Margulies created KARAF-3963: --- Summary: Some slight improvements to the doc for the feature generation mojo. Key: KARAF-3963 URL: https://issues.apache.org/jira/browse/KARAF-3963 Project: Karaf Issue Type: Improvement Reporter: Benson Margulies See about-to-exist pull request. -- 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] [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] [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] [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] [Created] (KARAF-3953) Karaf fails to diagnose un-wire-able bundle in feature
Benson Margulies created KARAF-3953:
---
Summary: 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-3951) No error when problem with class version
[ https://issues.apache.org/jira/browse/KARAF-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved KARAF-3951. - Resolution: Invalid No error when problem with class version Key: KARAF-3951 URL: https://issues.apache.org/jira/browse/KARAF-3951 Project: Karaf Issue Type: Bug Reporter: Benson Margulies Assignee: Jean-Baptiste Onofré Given an assembly that includes a features that includes a bundle that includes a class (!) that requires Java 1.8. Run Karaf with Java 1.7, and then try to install that there feature. No error; no log message; also, no installation of the feature! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3951) No error when problem with class version
[ https://issues.apache.org/jira/browse/KARAF-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708131#comment-14708131 ] Benson Margulies commented on KARAF-3951: - JB, I know what the neighborhood is now; there may be a bug, but this description is useless. I added a non-OSGi dependency to my project. It got wrapped. It, in turn, depends on something else. That also got wrapped. I excluded the later because these is an OSGi bundle that contains it. The result is this bizarre, silent, failure. After I put my own code into reasonable order, I'll see if I can come up with a reasonable test case for this business. No error when problem with class version Key: KARAF-3951 URL: https://issues.apache.org/jira/browse/KARAF-3951 Project: Karaf Issue Type: Bug Reporter: Benson Margulies Assignee: Jean-Baptiste Onofré Given an assembly that includes a features that includes a bundle that includes a class (!) that requires Java 1.8. Run Karaf with Java 1.7, and then try to install that there feature. No error; no log message; also, no installation of the feature! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3951) No error when problem with class version
[ https://issues.apache.org/jira/browse/KARAF-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708098#comment-14708098 ] Benson Margulies commented on KARAF-3951: - Karaf 4.0.1. Absolutely nothing in the log, either via log:display or by looking at the file. This has a nagging resemblance to something that I ran into weeks ago, which was perhaps related to maven configuration problems. No error when problem with class version Key: KARAF-3951 URL: https://issues.apache.org/jira/browse/KARAF-3951 Project: Karaf Issue Type: Bug Reporter: Benson Margulies Assignee: Jean-Baptiste Onofré Given an assembly that includes a features that includes a bundle that includes a class (!) that requires Java 1.8. Run Karaf with Java 1.7, and then try to install that there feature. No error; no log message; also, no installation of the feature! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3951) No error when problem with class version
Benson Margulies created KARAF-3951: --- Summary: No error when problem with class version Key: KARAF-3951 URL: https://issues.apache.org/jira/browse/KARAF-3951 Project: Karaf Issue Type: Bug Reporter: Benson Margulies Given an assembly that includes a features that includes a bundle that includes a class (!) that requires Java 1.8. Run Karaf with Java 1.7, and then try to install that there feature. No error; no log message; also, no installation of the feature! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3882) karaf should permit alternative host key formats
[ https://issues.apache.org/jira/browse/KARAF-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641938#comment-14641938 ] Benson Margulies commented on KARAF-3882: - [~jwcarman] has suggested writing the code to try several formats; I've got a patch in progress that aims to add a hostKeyFormat prop, we'll offer up some variation when we have a test that passes. karaf should permit alternative host key formats Key: KARAF-3882 URL: https://issues.apache.org/jira/browse/KARAF-3882 Project: Karaf Issue Type: Improvement Affects Versions: 4.0.0 Reporter: Benson Margulies It would be helpful to be able to generate a host key in advance; no common tools do so in serialized java objects readable by SimpleGeneratorHostKeyProvider. It would thus be helpful to be able to read PEM. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3882) karaf should permit alternative host key formats
Benson Margulies created KARAF-3882: --- Summary: karaf should permit alternative host key formats Key: KARAF-3882 URL: https://issues.apache.org/jira/browse/KARAF-3882 Project: Karaf Issue Type: Improvement Affects Versions: 4.0.0 Reporter: Benson Margulies It would be helpful to be able to generate a host key in advance; no common tools do so in serialized java objects readable by SimpleGeneratorHostKeyProvider. It would thus be helpful to be able to read PEM. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3874) Apparently valid feature.xml results in silent kar install failure
Benson Margulies created KARAF-3874:
---
Summary: Apparently valid feature.xml results in silent kar
install failure
Key: KARAF-3874
URL: https://issues.apache.org/jira/browse/KARAF-3874
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.0
Reporter: Benson Margulies
Attachments: feature.xml, oops.txt
Using the karaf-maven-plugin 4.0.0 with kar packaging, I created a kar.
The kar contains a feature.xml that aggregates the CXF 3.1.1 feature.xml. It
contains elements like:
{code}
feature name=cxf-specs resolver=(obr) version=3.1.1
...
/feature
{code}
According to the XSD on the web site, this should be OK.
Unfortunately, schema validation throws on kar:install.
Extremely unfortunately, kar:install does not print any error, and the kar is
'installed', but none of its features are installed.
The trouble is only to be seen in the log.
I will attach the feature.xml and the relevant log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3874) Apparently valid feature.xml results in silent kar install failure
[
https://issues.apache.org/jira/browse/KARAF-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated KARAF-3874:
Attachment: oops.txt
oops.txt is the log information.
Apparently valid feature.xml results in silent kar install failure
--
Key: KARAF-3874
URL: https://issues.apache.org/jira/browse/KARAF-3874
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.0
Reporter: Benson Margulies
Attachments: feature.xml, oops.txt
Using the karaf-maven-plugin 4.0.0 with kar packaging, I created a kar.
The kar contains a feature.xml that aggregates the CXF 3.1.1 feature.xml. It
contains elements like:
{code}
feature name=cxf-specs resolver=(obr) version=3.1.1
...
/feature
{code}
According to the XSD on the web site, this should be OK.
Unfortunately, schema validation throws on kar:install.
Extremely unfortunately, kar:install does not print any error, and the kar is
'installed', but none of its features are installed.
The trouble is only to be seen in the log.
I will attach the feature.xml and the relevant log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3874) Apparently valid feature.xml results in silent kar install failure
[
https://issues.apache.org/jira/browse/KARAF-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated KARAF-3874:
Attachment: feature.xml
Apparently valid feature.xml results in silent kar install failure
--
Key: KARAF-3874
URL: https://issues.apache.org/jira/browse/KARAF-3874
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.0
Reporter: Benson Margulies
Attachments: feature.xml, oops.txt
Using the karaf-maven-plugin 4.0.0 with kar packaging, I created a kar.
The kar contains a feature.xml that aggregates the CXF 3.1.1 feature.xml. It
contains elements like:
{code}
feature name=cxf-specs resolver=(obr) version=3.1.1
...
/feature
{code}
According to the XSD on the web site, this should be OK.
Unfortunately, schema validation throws on kar:install.
Extremely unfortunately, kar:install does not print any error, and the kar is
'installed', but none of its features are installed.
The trouble is only to be seen in the log.
I will attach the feature.xml and the relevant log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
