[jira] [Created] (KARAF-3283) karaf.util missing as private package for bundle watcher
Jean-Baptiste Onofré created KARAF-3283:
---
Summary: karaf.util missing as private package for bundle watcher
Key: KARAF-3283
URL: https://issues.apache.org/jira/browse/KARAF-3283
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 3.0.2
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.3
BundleWatcher doesn't work due to:
{code}
Exception in thread Thread-32 java.lang.NoClassDefFoundError:
org/apache/karaf/util/maven/Parser
at
org.apache.karaf.bundle.core.internal.BundleWatcherImpl.getBundleExternalLocation(BundleWatcherImpl.java:195)
at
org.apache.karaf.bundle.core.internal.BundleWatcherImpl.updateBundleIfNecessary(BundleWatcherImpl.java:144)
at
org.apache.karaf.bundle.core.internal.BundleWatcherImpl.run(BundleWatcherImpl.java:100)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException: org.apache.karaf.util.maven.Parser
not found by org.apache.karaf.bundle.core [31]
at
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1532)
at
org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:75)
at
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1955)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 4 more
{code}
karaf.util (which is not a bundle) has to be as private package of the bundle
bundle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (KARAF-3103) config:edit does not correctly handle configuration visibility for --factory calls.
[ https://issues.apache.org/jira/browse/KARAF-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Kaufhold closed KARAF-3103. --- Thank you. config:edit does not correctly handle configuration visibility for --factory calls. --- Key: KARAF-3103 URL: https://issues.apache.org/jira/browse/KARAF-3103 Project: Karaf Issue Type: Bug Components: karaf-config Affects Versions: 2.4.0, 4.0.0, 3.0.2 Reporter: Richard Kaufhold Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.0, 3.0.2, 2.4.1 Attachments: patch-ConfigRepositoryImpl-visibility.txt Original Estimate: 10m Remaining Estimate: 10m The ConfigRepositoryImpl does not specify the visibility for created factory configurations. I have tested it using my own ManagedServiceFactory: Inside of the karaf shell I executed: karaf@root() config:edit --factory de.ansii.example.hellofactory karaf@root() config:property-append prop1 value1 karaf@root() config:update The response was: 2014-07-07 15:18:45,038 | ERROR | 04-24cc6aa84094) | configadmin | 5 - org.apache.felix.configadmin - 1.6.0 | Cannot use configuration de.ansii.example.hellofactory.5b076892-5207-4913-a704-24cc6aa84094 for [org.osgi.service.cm.ManagedServiceFactory, id=90, bundle=65/mvn:de.ansii.example/hellofactory]: No visibility to configuration bound to mvn:org.apache.karaf.config/org.apache.karaf.config.core/4.0.0-SNAPSHOT In line 91 of /org.apache.karaf.config.core/src/main/java/org/apache/karaf/config/core/impl/ConfigRepositoryImpl.java the visibility is not specified which leads to the problem that the factory configuration created by config:edit --factory is not usable by factory implementations. (null is a sensible default, as in line 44) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3281) Upgrade to Pax Logging 1.8.0 (log4j v2 support)
[ https://issues.apache.org/jira/browse/KARAF-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated KARAF-3281: --- Fix Version/s: 2.4.1 Upgrade to Pax Logging 1.8.0 (log4j v2 support) --- Key: KARAF-3281 URL: https://issues.apache.org/jira/browse/KARAF-3281 Project: Karaf Issue Type: Dependency upgrade Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0, 3.0.3, 2.4.1 Pax Logging 1.8.0 will be released soon, including log4j v2 support and few important bug fixes. I'm testing 1.8.0-SNAPSHOT, ready to upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3284) The shell-log bundle should not import org.apache.log4j.* package
Guillaume Nodet created KARAF-3284: -- Summary: The shell-log bundle should not import org.apache.log4j.* package Key: KARAF-3284 URL: https://issues.apache.org/jira/browse/KARAF-3284 Project: Karaf Issue Type: Bug Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.0.0, 3.0.3, 2.4.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3285) IllegalArgumentException raised when accessing the FeaturesMBean
Jean-Baptiste Onofré created KARAF-3285:
---
Summary: IllegalArgumentException raised when accessing the
FeaturesMBean
Key: KARAF-3285
URL: https://issues.apache.org/jira/browse/KARAF-3285
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.2
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.3
Using jconsole, when accessing the FeaturesMBean (and especially the Features
attribute), an IllegalArgumentException is raised:
{code}
java.lang.IllegalArgumentException: Different lengths: itemNames[2],
itemValues[3]
at
javax.management.openmbean.CompositeDataSupport.makeMap(CompositeDataSupport.java:130)
at
javax.management.openmbean.CompositeDataSupport.init(CompositeDataSupport.java:118)
at
org.apache.karaf.features.management.codec.JmxFeature.getConfigList(JmxFeature.java:136)
at
org.apache.karaf.features.management.codec.JmxFeature.init(JmxFeature.java:82)
at
org.apache.karaf.features.management.internal.FeaturesServiceMBeanImpl.getFeatures(FeaturesServiceMBeanImpl.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:75)
at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:279)
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
at
com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
at
com.sun.jmx.mbeanserver.PerInterface.getAttribute(PerInterface.java:83)
at
com.sun.jmx.mbeanserver.MBeanSupport.getAttribute(MBeanSupport.java:206)
at
com.sun.jmx.mbeanserver.MBeanSupport.getAttributes(MBeanSupport.java:213)
at javax.management.StandardMBean.getAttributes(StandardMBean.java:390)
at Proxyc2523419_ec3a_4576_b9a1_222eadf37003.getAttributes(Unknown
Source)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:709)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:705)
at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:80)
at com.sun.proxy.$Proxy0.getAttributes(Unknown Source)
at
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
at
javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:97)
at
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1328)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1427)
at
javax.management.remote.rmi.RMIConnectionImpl.getAttributes(RMIConnectionImpl.java:693)
at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
at sun.rmi.transport.Transport$1.run(Transport.java:177)
at sun.rmi.transport.Transport$1.run(Transport.java:174)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:556)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:811)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:670)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-3284) The shell-log bundle should not import org.apache.log4j.* package
[ https://issues.apache.org/jira/browse/KARAF-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-3284. Resolution: Fixed 2.x branch: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commit;h=afa3c669225a822deb2f830ff486055682196f1c 3.0.x branch: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commit;h=c5822d9296cc22e2ff1d8b8d079a26fc6a57734f master: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commit;h=f868947d82394136433cd2ea0f17e73adf4fbe83 The shell-log bundle should not import org.apache.log4j.* package - Key: KARAF-3284 URL: https://issues.apache.org/jira/browse/KARAF-3284 Project: Karaf Issue Type: Bug Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.0.0, 3.0.3, 2.4.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3284) The shell-log bundle should not import org.apache.log4j.* package
[ https://issues.apache.org/jira/browse/KARAF-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170917#comment-14170917 ] Guillaume Nodet commented on KARAF-3284: KARAF-3281 needs KARAF-3284 in order to benefit from PAXLOGGING-184 The shell-log bundle should not import org.apache.log4j.* package - Key: KARAF-3284 URL: https://issues.apache.org/jira/browse/KARAF-3284 Project: Karaf Issue Type: Bug Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.0.0, 3.0.3, 2.4.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3286) karaf-maven-plugin does not merge bundle entry with URL parameters
Ralf Steppacher created KARAF-3286:
--
Summary: karaf-maven-plugin does not merge bundle entry with URL
parameters
Key: KARAF-3286
URL: https://issues.apache.org/jira/browse/KARAF-3286
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.1
Reporter: Ralf Steppacher
If a template contains an entry with URL parameters, e.g.
{code:xml}bundlewrap:mvn:jboss/jbossall-client/4.2.3.GA/$Bundle-SymbolicName=jbossall-clientamp;Bundle-Version=4.2.3.GA/bundle{code}
then it is not merged with a maven compile dependency. Instead the resulting
feature.xml contains two entries for that bundle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3286) karaf-maven-plugin does not merge bundle entry with URL parameters
[
https://issues.apache.org/jira/browse/KARAF-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171006#comment-14171006
]
Achim Nierbeck commented on KARAF-3286:
---
did you also test with the just released 3.0.2?
AFAIK it should be fixed already ...
karaf-maven-plugin does not merge bundle entry with URL parameters
--
Key: KARAF-3286
URL: https://issues.apache.org/jira/browse/KARAF-3286
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.1
Reporter: Ralf Steppacher
If a template contains an entry with URL parameters, e.g.
{code:xml}bundlewrap:mvn:jboss/jbossall-client/4.2.3.GA/$Bundle-SymbolicName=jbossall-clientamp;Bundle-Version=4.2.3.GA/bundle{code}
then it is not merged with a maven compile dependency. Instead the resulting
feature.xml contains two entries for that bundle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-3287) Bundle command waiting for BundleWatcher and BundleService services
Jean-Baptiste Onofré created KARAF-3287:
---
Summary: Bundle command waiting for BundleWatcher and
BundleService services
Key: KARAF-3287
URL: https://issues.apache.org/jira/browse/KARAF-3287
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 3.0.2
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Fix For: 3.0.3
In the Karaf log, we can see (directly at startup):
{code}
2014-10-14 19:15:04,498 | INFO | FelixStartLevel | BlueprintContainerImpl
| 15 - org.apache.aries.blueprint.core - 1.4.1 | Bundle
org.apache.karaf.bundle.command is waiting for dependencies
[(objectClass=org.apache.karaf.bundle.core.BundleService),
(objectClass=org.apache.karaf.bundle.core.BundleWatcher)]
2014-10-14 19:15:04,529 | INFO | rint Extender: 2 | BlueprintContainerImpl
| 15 - org.apache.aries.blueprint.core - 1.4.1 | Bundle
org.apache.karaf.bundle.command is waiting for dependencies
[(objectClass=org.apache.karaf.bundle.core.BundleService)]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-3275) Release Apache Karaf 4.0.0.M1
[ https://issues.apache.org/jira/browse/KARAF-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jamie goodyear resolved KARAF-3275. --- Resolution: Fixed Release Apache Karaf 4.0.0.M1 -- Key: KARAF-3275 URL: https://issues.apache.org/jira/browse/KARAF-3275 Project: Karaf Issue Type: Task Reporter: Jamie goodyear Assignee: Jamie goodyear Preview beta of Karaf 4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
