[jira] [Commented] (KARAF-4688) jre.properties should export all JavaFX packages for JRE 1.8+
[ https://issues.apache.org/jira/browse/KARAF-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15500432#comment-15500432 ] Jean-Baptiste Onofré commented on KARAF-4688: - I just checked on https://docs.oracle.com/javafx/2/api/: {{javafx.collections.transformation}} and {{javafx.print}} are not in the JavaFX 2 API. It's maybe in additional API ? Anyway, I'm syncing {{jre.properties}} with JavaFX 2 API, especially adding {{netscape.javascript}} package. > jre.properties should export all JavaFX packages for JRE 1.8+ > - > > Key: KARAF-4688 > URL: https://issues.apache.org/jira/browse/KARAF-4688 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.6, 3.0.8 >Reporter: Tim Hull >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.9, 4.0.7 > > > javafx.collections.transformation, javafx.print, andnetscape.javascript is > part of the JavaFX API in Java 8, but is not exported by the system package > in Karaf instances running on Java 8. Since other JavaFX packages are > exported, could these be added to jre.properties? This was requested by a > user of our distribution who was using JavaFX - we're planning on adding it > to our configuration, though it would be good to have this in Karaf upstream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4688) jre.properties should export all JavaFX packages for JRE 1.8+
[ https://issues.apache.org/jira/browse/KARAF-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15500432#comment-15500432 ] Jean-Baptiste Onofré edited comment on KARAF-4688 at 9/18/16 7:02 AM: -- I just checked on https://docs.oracle.com/javafx/2/api/: {{javafx.collections.transformation}} and {{javafx.print}} are not in the JavaFX 2 API. It's maybe in additional API ? Anyway, I'm syncing {{jre.properties}} with JavaFX 2 API, especially adding {{netscape.javascript}} package. I'm also preparing additional JavaFX package (not a big deal if there are not actually present). was (Author: jbonofre): I just checked on https://docs.oracle.com/javafx/2/api/: {{javafx.collections.transformation}} and {{javafx.print}} are not in the JavaFX 2 API. It's maybe in additional API ? Anyway, I'm syncing {{jre.properties}} with JavaFX 2 API, especially adding {{netscape.javascript}} package. > jre.properties should export all JavaFX packages for JRE 1.8+ > - > > Key: KARAF-4688 > URL: https://issues.apache.org/jira/browse/KARAF-4688 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.6, 3.0.8 >Reporter: Tim Hull >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.9, 4.0.7 > > > javafx.collections.transformation, javafx.print, andnetscape.javascript is > part of the JavaFX API in Java 8, but is not exported by the system package > in Karaf instances running on Java 8. Since other JavaFX packages are > exported, could these be added to jre.properties? This was requested by a > user of our distribution who was using JavaFX - we're planning on adding it > to our configuration, though it would be good to have this in Karaf upstream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4688) jre.properties should export all JavaFX packages for JRE 1.8+
[ https://issues.apache.org/jira/browse/KARAF-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15500466#comment-15500466 ] ASF subversion and git services commented on KARAF-4688: Commit a8049e01fb74ed38a095c949c45e839d4a0b7243 in karaf's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=a8049e0 ] [KARAF-4688] Add additional javafx packages in jre.properties > jre.properties should export all JavaFX packages for JRE 1.8+ > - > > Key: KARAF-4688 > URL: https://issues.apache.org/jira/browse/KARAF-4688 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.6, 3.0.8 >Reporter: Tim Hull >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.9, 4.0.7 > > > javafx.collections.transformation, javafx.print, andnetscape.javascript is > part of the JavaFX API in Java 8, but is not exported by the system package > in Karaf instances running on Java 8. Since other JavaFX packages are > exported, could these be added to jre.properties? This was requested by a > user of our distribution who was using JavaFX - we're planning on adding it > to our configuration, though it would be good to have this in Karaf upstream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4688) jre.properties should export all JavaFX packages for JRE 1.8+
[ https://issues.apache.org/jira/browse/KARAF-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15500470#comment-15500470 ] ASF subversion and git services commented on KARAF-4688: Commit 002065714ce2dd9564e70cddba37fdc032829f3a in karaf's branch refs/heads/karaf-4.0.x from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=0020657 ] [KARAF-4688] Add additional javafx packages in jre.properties > jre.properties should export all JavaFX packages for JRE 1.8+ > - > > Key: KARAF-4688 > URL: https://issues.apache.org/jira/browse/KARAF-4688 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.6, 3.0.8 >Reporter: Tim Hull >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.9, 4.0.7 > > > javafx.collections.transformation, javafx.print, andnetscape.javascript is > part of the JavaFX API in Java 8, but is not exported by the system package > in Karaf instances running on Java 8. Since other JavaFX packages are > exported, could these be added to jre.properties? This was requested by a > user of our distribution who was using JavaFX - we're planning on adding it > to our configuration, though it would be good to have this in Karaf upstream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4688) jre.properties should export all JavaFX packages for JRE 1.8+
[ https://issues.apache.org/jira/browse/KARAF-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4688. - Resolution: Fixed > jre.properties should export all JavaFX packages for JRE 1.8+ > - > > Key: KARAF-4688 > URL: https://issues.apache.org/jira/browse/KARAF-4688 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.6, 3.0.8 >Reporter: Tim Hull >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.9, 4.0.7 > > > javafx.collections.transformation, javafx.print, andnetscape.javascript is > part of the JavaFX API in Java 8, but is not exported by the system package > in Karaf instances running on Java 8. Since other JavaFX packages are > exported, could these be added to jre.properties? This was requested by a > user of our distribution who was using JavaFX - we're planning on adding it > to our configuration, though it would be good to have this in Karaf upstream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4688) jre.properties should export all JavaFX packages for JRE 1.8+
[ https://issues.apache.org/jira/browse/KARAF-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15500474#comment-15500474 ] ASF subversion and git services commented on KARAF-4688: Commit 1f1fc5619669fcb5fc4d5c1f0371f6b80d83d017 in karaf's branch refs/heads/karaf-3.0.x from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=1f1fc56 ] [KARAF-4688] Add additional javafx packages in jre.properties > jre.properties should export all JavaFX packages for JRE 1.8+ > - > > Key: KARAF-4688 > URL: https://issues.apache.org/jira/browse/KARAF-4688 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.6, 3.0.8 >Reporter: Tim Hull >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.9, 4.0.7 > > > javafx.collections.transformation, javafx.print, andnetscape.javascript is > part of the JavaFX API in Java 8, but is not exported by the system package > in Karaf instances running on Java 8. Since other JavaFX packages are > exported, could these be added to jre.properties? This was requested by a > user of our distribution who was using JavaFX - we're planning on adding it > to our configuration, though it would be good to have this in Karaf upstream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4716) Upgrade to Aries Blueprint Core 1.7.0 and Aries Blueprint CM 1.0.9
[ https://issues.apache.org/jira/browse/KARAF-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4716: Fix Version/s: (was: 4.0.7) 4.0.8 > Upgrade to Aries Blueprint Core 1.7.0 and Aries Blueprint CM 1.0.9 > -- > > Key: KARAF-4716 > URL: https://issues.apache.org/jira/browse/KARAF-4716 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4572) NullPointer Exception when deploying EclipseLink model bundle
[ https://issues.apache.org/jira/browse/KARAF-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4572: Fix Version/s: (was: 4.0.7) 4.0.8 4.1.0 > NullPointer Exception when deploying EclipseLink model bundle > - > > Key: KARAF-4572 > URL: https://issues.apache.org/jira/browse/KARAF-4572 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.5 >Reporter: Viktor Kozlov >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > > When I deploy my model bundle which contains only persistence unit I get this > Exception: > karaf@root()> bundle:install -s mvn:biz.lorien.niichi/model; > [EL Warning]: 2016-01-18 17:14:57.797--java.lang.NullPointerException > Bundle ID: 167 > and every time I start Karaf with this model bundle: > Hit '' for a list of available commands. > Type '[cmd] --help' for help on a specific command. > karaf@root()> [EL Warning]: 2016-01-18 > 17:18:08.176--java.lang.NullPointerException > If I uninstall and install my model bundle there is no Exception. > Exception popups when first installed and after Karaf restart. > It looks like exception is thrown during eclipselink engine init. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4655) karaf-maven-plugin add-features-to-repo goal can't add Camel feature
[ https://issues.apache.org/jira/browse/KARAF-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4655: Fix Version/s: (was: 4.0.7) 4.0.8 > karaf-maven-plugin add-features-to-repo goal can't add Camel feature > > > Key: KARAF-4655 > URL: https://issues.apache.org/jira/browse/KARAF-4655 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.0.5, 4.0.6 >Reporter: Igor Lazebny >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > Attachments: pom.xml > > > camel-restlet 2.17.3 feature contains bundle reference like this: > {{ dependency="true">mvn:http://maven.restlet.org@id=restlet!org.restlet.osgi/org.restlet/2.3.6}} > add-features-to-repo can't interpret it correctly trying to connect to > "id=restlet" host: > [ERROR] Failed to execute goal > org.apache.karaf.tooling:karaf-maven-plugin:4.0.6-SNAPSHOT:features-add-to-repository > (add-features-to-repo) on project karaf-maven-plugin-test: Error populating > repository: Error resolving feature camel-restlet/2.17.3: Error resolving > artifact > mvn:http://maven.restlet.org@id=restlet!org.restlet.osgi/org.restlet/2.3.6: > Can't resolve artifact org.restlet.osgi:org.restlet:jar:2.3.6: Could not > transfer artifact org.restlet.osgi:org.restlet:jar:2.3.6 from/to > http://maven.restlet.org@id=restlet (http://id=restlet): id=restlet: unknown > error > [ERROR] org.restlet.osgi:org.restlet:jar:2.3.6 > [ERROR] > [ERROR] from the specified remote repositories: > [ERROR] http://maven.restlet.org@id=restlet (http://id=restlet, > releases=true, snapshots=true): Unknown host id=restlet: unknown error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4552) Karaf maven plugin creates wrong archived folder name when building custom distribution
[ https://issues.apache.org/jira/browse/KARAF-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4552: Fix Version/s: (was: 4.0.7) 4.0.8 4.1.0 > Karaf maven plugin creates wrong archived folder name when building custom > distribution > --- > > Key: KARAF-4552 > URL: https://issues.apache.org/jira/browse/KARAF-4552 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.0.5 >Reporter: Viktor Kozlov > Fix For: 4.1.0, 4.0.8 > > > I am building my custom distribution. I set target file name to aaa: > > org.apache.karaf.tooling > karaf-maven-plugin > > aa > Plugin creates aaa.zip archive file. But inside of acrhive there is wrong > folder name: assembly-0.4.0-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4552) Karaf maven plugin creates wrong archived folder name when building custom distribution
[ https://issues.apache.org/jira/browse/KARAF-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-4552: --- Assignee: Jean-Baptiste Onofré > Karaf maven plugin creates wrong archived folder name when building custom > distribution > --- > > Key: KARAF-4552 > URL: https://issues.apache.org/jira/browse/KARAF-4552 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.0.5 >Reporter: Viktor Kozlov >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > I am building my custom distribution. I set target file name to aaa: > > org.apache.karaf.tooling > karaf-maven-plugin > > aa > Plugin creates aaa.zip archive file. But inside of acrhive there is wrong > folder name: assembly-0.4.0-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4535) OpenJPA 2.4.1 Missing dependencies: objectClass=javax.persistence.EntityManager
[ https://issues.apache.org/jira/browse/KARAF-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4535: Fix Version/s: (was: 4.0.7) 4.0.8 > OpenJPA 2.4.1 Missing dependencies: > objectClass=javax.persistence.EntityManager > --- > > Key: KARAF-4535 > URL: https://issues.apache.org/jira/browse/KARAF-4535 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.5 > Environment: Karaf 4.0.5 > OpenJPA 2.4.1 >Reporter: Jirka >Assignee: Christian Schneider > Fix For: 4.1.0, 4.0.8 > > > OpenJPA 2.4.1 does not start when installed with the jpa feature. > Problem is that the jpa feature installs persistence api 2.1.0 > {code} > dependency="false">persistence-api > > {code} > It collides with persistence api 2.0.0 installed by the openjpa feature > {code} > dependency="false">persistence-api > {code} > Workaround is to use this custom jpa feature instead of the jpa feature. > {code} >version="2.3.0"> > JPA implementation provided by Apache Aries JPA 2.x. > NB: this feature doesn't provide the JPA engine, you have to install one by > yourself (OpenJPA for instance) >dependency="false">transaction-api >dependency="true">mvn:org.apache.felix/org.apache.felix.coordinator/1.0.2 >dependency="true">mvn:org.osgi/org.osgi.service.jdbc/1.0.0 > mvn:org.osgi/org.osgi.service.jpa/1.0.0 > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.api/2.3.0 > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.container/2.3.0 > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.support/2.3.0 > > aries-blueprint > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.blueprint/2.3.0 > > > {code} > Changes compared to the karaf jpa feature:: > Removed: > {code} > dependency="false">persistence-api > {code} > Added > {code} > mvn:org.osgi/org.osgi.service.jpa/1.0.0 added > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4665) Skip Maven itest when using -DskipTests
[ https://issues.apache.org/jira/browse/KARAF-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4665: Fix Version/s: (was: 4.0.7) 4.0.8 > Skip Maven itest when using -DskipTests > --- > > Key: KARAF-4665 > URL: https://issues.apache.org/jira/browse/KARAF-4665 > Project: Karaf > Issue Type: Improvement > Components: karaf-tooling >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > When using {{-DskipTests}} to skip unit tests, the Maven integration test in > tooling (using Maven invoker) are executed anyway (slowing down the build). I > think it make sense to "link" Maven itest with {{-DskipTests}} usage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4534) Invalid definition in feature file causes maven build of custom distro to fail
[ https://issues.apache.org/jira/browse/KARAF-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4534: Fix Version/s: (was: 4.0.7) 4.0.8 4.1.0 > Invalid definition in feature file causes maven build of custom distro to fail > -- > > Key: KARAF-4534 > URL: https://issues.apache.org/jira/browse/KARAF-4534 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.0.5 >Reporter: Christian Schneider >Priority: Critical > Fix For: 4.1.0, 4.0.8 > > > [ERROR] Failed to execute goal > org.apache.karaf.tooling:karaf-maven-plugin:4.0.5:assembly > (process-resources) on project decanter-server: Unable to build assembly: > Error -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.karaf.tooling:karaf-maven-plugin:4.0.5:assembly > (process-resources) on project decanter-server: Unable to build assembly > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:160) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to build > assembly > at org.apache.karaf.tooling.AssemblyMojo.execute(AssemblyMojo.java:234) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > Caused by: org.apache.karaf.features.internal.util.MultiException: Error > at > org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.(MavenDownloadManager.java:84) > at > org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72) > at > org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:363) > at > org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:360) > at > org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:187) > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:263) > at org.apache.karaf.profile.assembly.Builder.resolve(Builder.java:1214) > at > org.apache.karaf.profile.assembly.Builder.startupStage(Builder.java:1002) > at > org.apache.karaf.profile.assembly.Builder.doGenerateAssembly(Builder.java:606) > at > org.apache.karaf.profile.assembly.Builder.generateAssembly(Builder.java:389) > at > org.apache.karaf.tooling.AssemblyMojo.doExecute(AssemblyMojo.java:392) > at org.apache.karaf.tooling.AssemblyMojo.execute(AssemblyMojo.java:228) > ... 21 more > Suppressed: java.io.IOException: Error downloading > wrap:file:/home/cschneider/.m2/repository/org/fusesource/leveldbjni/leveldbjni-all/1.8/leveldbjni-all-1.8.jar$Bundle-Version=1.8&Export-Package=*;-noimport:=true;version="1.8" > at > org.apache.karaf.features.internal.download.impl.A
[jira] [Resolved] (KARAF-4520) Add DigestPasswordLoginModule so PasswordDigest can work with Karaf JAAS realm
[ https://issues.apache.org/jira/browse/KARAF-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4520. - Resolution: Fixed > Add DigestPasswordLoginModule so PasswordDigest can work with Karaf JAAS > realm > --- > > Key: KARAF-4520 > URL: https://issues.apache.org/jira/browse/KARAF-4520 > Project: Karaf > Issue Type: Improvement > Components: karaf-security >Reporter: Freeman Fang >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.7, 4.0.6 > > > So far the assumption with JAAS login modules is that the password is to be > compared "as is". However per the ws-security spec, the PasswordDigest for > UsernameToken is "the concatenation of the nonce plus the creation time plus > the password. The nonce is 16 bytes long and is passed along as a base64 > encoded value. The way this works is that the client creates the password > hash using all of this information plus the password". So the PasswordDigest > would change per each invocation, so we can't simply store the passwords in a > digest form in the properties file. > The way to make it work, I think we need a DigestPasswordLoginModule which > use a customized checkPassword method where can compare the stored password > and the digest password from PasswordCallback (we may need take a close look > how this part implemented in WSS4J for digest password comparing) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4515) Add kar:extract command (and MBean operation)
[ https://issues.apache.org/jira/browse/KARAF-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4515: Fix Version/s: (was: 4.0.7) 4.0.8 > Add kar:extract command (and MBean operation) > - > > Key: KARAF-4515 > URL: https://issues.apache.org/jira/browse/KARAF-4515 > Project: Karaf > Issue Type: New Feature > Components: karaf-kar, karaf-management, karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > The {{kar:extract}} command will be able to resolve a KAR file (from a Maven > URL for instance), and extract kar content into the system folder (or other > location). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4514) Add config:install command and MBean
[ https://issues.apache.org/jira/browse/KARAF-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4514: Fix Version/s: (was: 4.0.7) 4.0.8 > Add config:install command and MBean > > > Key: KARAF-4514 > URL: https://issues.apache.org/jira/browse/KARAF-4514 > Project: Karaf > Issue Type: New Feature > Components: karaf-config, karaf-management, karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > It's possible to directly deploy a cfg file using the {{}} > element of a feature. > However, it's not possible to do the same directly in Karaf (providing the > cfg URL). The only way is to actually create the config (config:property-set, > etc). > We will provide a {{config:install}} command with the cfg URL as argument to > deploy directly in the {{karaf.etc}} folder. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4439) Prevent user authentication (shell & JMX) if he doesn't have role
[ https://issues.apache.org/jira/browse/KARAF-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4439: Fix Version/s: (was: 4.0.7) 4.0.8 > Prevent user authentication (shell & JMX) if he doesn't have role > - > > Key: KARAF-4439 > URL: https://issues.apache.org/jira/browse/KARAF-4439 > Project: Karaf > Issue Type: Bug > Components: karaf-management, karaf-security, karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 4.1.0, 4.0.8 > > > Right now, if an user doesn't have any role defined, he can logon and perform > "non" critical operations (the "critical" operation). > We should define a minimum role required for login and prevent users access > if they don't have the minimum role (before the ACL). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4424) referenced features/bundles not installed when dropped in deploy folder
[ https://issues.apache.org/jira/browse/KARAF-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4424: Fix Version/s: (was: 4.0.7) 4.0.8 > referenced features/bundles not installed when dropped in deploy folder > --- > > Key: KARAF-4424 > URL: https://issues.apache.org/jira/browse/KARAF-4424 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Robert von Burg >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > > I have the following features: > {code:xml} > > http://karaf.apache.org/xmlns/features/v1.3.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://karaf.apache.org/xmlns/features/v1.3.0 > karaf-features-1.3.0.xsd " name="All-features"> > > mvn:my.group/MyBundle1/0.3.0-SNAPSHOT/xml/features > > mvn:my.group/MyBundle2/0.3.0-SNAPSHOT/xml/features > > mvn:my.group/MyBundle3/0.3.0-SNAPSHOT/xml/features > >version="0.3.0-SNAPSHOT">MyBundle1 > > >version="0.3.0-SNAPSHOT">MyBundle2 > > >version="0.3.0-SNAPSHOT">MyBundle3 > > > > http://karaf.apache.org/xmlns/features/v1.3.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://karaf.apache.org/xmlns/features/v1.3.0 > karaf-features-1.3.0.xsd " name="MyBundle1-features"> > >start="true">mvn:my.group/MyBundle1/0.3.0-SNAPSHOT > > > > http://karaf.apache.org/xmlns/features/v1.3.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://karaf.apache.org/xmlns/features/v1.3.0 > karaf-features-1.3.0.xsd " name="MyBundle2-features"> > >start="true">mvn:my.group/MyBundle2/0.3.0-SNAPSHOT > > > > http://karaf.apache.org/xmlns/features/v1.3.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://karaf.apache.org/xmlns/features/v1.3.0 > karaf-features-1.3.0.xsd " name="MyBundle3-features"> > >start="true">mvn:my.group/MyBundle3/0.3.0-SNAPSHOT > > > {code} > On my local machine when i drop the "all-features", then it installs al the > referenced bundles. On my local machine, the bundles were installed using mvn > clean install. > On another machine, where the features are pulled in through a remote archiva > repository, it doesn't auto install. It says: > {noformat} > Adding features: MyBundle1/[0.3.0.SNAPSHOT,0.3.0.SNAPSHOT] > No deployment change. > {noformat} > When i then do everything by hand: > {noformat} > feature:repo-add mvn:my.group/MyBundle1/0.3.0-SNAPSHOT/xml/features > feature:repo-add mvn:my.group/MyBundle2/0.3.0-SNAPSHOT/xml/features > feature:repo-add mvn:my.group/MyBundle3/0.3.0-SNAPSHOT/xml/features > feature:install MyBundle1/0.3.0-SNAPSHOT > feature:install MyBundle2/0.3.0-SNAPSHOT > feature:install MyBundle3/0.3.0-SNAPSHOT > {noformat} > the features are installed and everything. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4434) Version range not correctly resolved for distribution build
[ https://issues.apache.org/jira/browse/KARAF-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4434: Fix Version/s: (was: 4.0.7) 4.0.8 > Version range not correctly resolved for distribution build > --- > > Key: KARAF-4434 > URL: https://issues.apache.org/jira/browse/KARAF-4434 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.0.4 >Reporter: Markus Tippmann > Fix For: 4.1.0, 4.0.8 > > > using karaf-mave-plugin 4.0.4 without any obscure configuration, just > bootFeatures, to build a distribution. > One feature contains a bundle location with a version range like: > mvn:groupid/artifactid/[1.0,2) > The assembly succeeds to build, but the distribution afterwards contains: > system/groupid/artifactid/[1.0,2)/artifactid-[1.0,2).jar > So it looks like the karaf assemble goal does not use the resolved version > but copies the version string from the feature XML. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4419) Multiple inharitance levels with generics cause ClassCastException when JPA is enabled
[ https://issues.apache.org/jira/browse/KARAF-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4419: Fix Version/s: (was: 4.0.7) 4.0.8 > Multiple inharitance levels with generics cause ClassCastException when JPA > is enabled > -- > > Key: KARAF-4419 > URL: https://issues.apache.org/jira/browse/KARAF-4419 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.4 > Environment: Win 7 x64, JDK 1.8.0_73, Karaf 4.0.4 >Reporter: Felix Wassmer > Fix For: 4.1.0, 4.0.8 > > > I'm using inheritance with generics over multiple levels. > Injecting properties to those beans works fine, but on access of a property > of the lowest class, there is a ClassCastException thrown. > I could narrow it down to enabling JPA in the blueprint causing the issue: > When disabling JPA, the proper bean class is resolved, > enabled the type resolving stopped at the parent abstract class of the > expected class, thus throwing a ClassCastException. > Example project to reproduce this issue: > https://github.com/fwassmer/inheritance -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4360) FrameworkEvent ERROR in the karaf.log when install cxf-core feature
[ https://issues.apache.org/jira/browse/KARAF-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4360: Fix Version/s: (was: 4.0.7) 4.0.8 > FrameworkEvent ERROR in the karaf.log when install cxf-core feature > --- > > Key: KARAF-4360 > URL: https://issues.apache.org/jira/browse/KARAF-4360 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.4 > Environment: Java 8 >Reporter: Xilai Dai >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > > When trying to install cxf-core feature into Karaf 4.0.4, there is > FrameworkEvent ERROR in the karaf.log, but the bundles can be started and in > the Active status. > {code} > 2016-02-25 12:09:57,529 | ERROR | 8d8-961af9b70a25 | cxf-core > | 53 - org.apache.cxf.cxf-core - 3.1.5 | FrameworkEvent ERROR - > org.apache.cxf.cxf-core > org.osgi.framework.BundleException: Could not resolve module: > org.apache.cxf.cxf-core [53] > Unresolved requirement: Import-Package: com.ctc.wstx.msv; > version="[4.4.0,5.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: com.ctc.wstx.stax; > version="[4.4.0,5.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: org.codehaus.stax2; > version="[3.1.0,4.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: org.codehaus.stax2.validation; > version="[3.1.0,4.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: com.sun.msv.grammar; > version="[2013.6.0,2014.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: com.sun.msv.grammar.xmlschema; > version="[2013.6.0,2014.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: com.sun.msv.reader; > version="[2013.6.0,2014.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: com.sun.msv.reader.xmlschema; > version="[2013.6.0,2014.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: com.sun.xml.bind.marshaller; > version="[2.2.0,3.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: com.sun.xml.fastinfoset.stax; > version="[1.2.0,2.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: net.sf.cglib.proxy; > version="[2.1.3,3.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: org.springframework.osgi.io; > version="[1.2.0,2.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: org.springframework.osgi.util; > version="[1.2.0,2.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: org.springframework.aop; > version="[3.1.0,5.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: org.springframework.aop.framework; > version="[3.1.0,5.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: org.springframework.aop.support; > version="[3.1.0,5.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: org.springframework.beans; > version="[3.1.0,5.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: org.springframework.beans.factory; > version="[3.1.0,5.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: > org.springframework.beans.factory.config; version="[3.1.0,5.0.0)"; > resolution:="optional" > Unresolved requirement: Import-Package: > org.springframework.beans.factory.support; version="[3.1.0,5.0.0)"; > resolution:="optional" > Unresolved requirement: Import-Package: > org.springframework.beans.factory.wiring; version="[3.1.0,5.0.0)"; > resolution:="optional" > Unresolved requirement: Import-Package: > org.springframework.beans.factory.xml; version="[3.1.0,5.0.0)"; > resolution:="optional" > Unresolved requirement: Import-Package: org.springframework.context; > version="[3.1.0,5.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: org.springframework.context.event; > version="[3.1.0,5.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: > org.springframework.context.support; version="[3.1.0,5.0.0)"; > resolution:="optional" > Unresolved requirement: Import-Package: org.springframework.core; > version="[3.1.0,5.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: org.springframework.core.io; > version="[3.1.0,5.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: > org.springframework.core.io.support; version="[3.1.0,5.0.0)"; > resolution:="optional" > Unresolved requirement: Import-Package: org.springframework.core.type; > version="[3.1.0,5.0.0)"; resolution:="optional" > Unresolved requirement: Import-Package: > org.s
[jira] [Resolved] (KARAF-4411) FeatureResolver: spring-dm-web feature installs Spring ver 3.1.4 and 3.2.14 at the same time
[ https://issues.apache.org/jira/browse/KARAF-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4411. - Resolution: Fixed > FeatureResolver: spring-dm-web feature installs Spring ver 3.1.4 and 3.2.14 > at the same time > > > Key: KARAF-4411 > URL: https://issues.apache.org/jira/browse/KARAF-4411 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.4 > Environment: Oracle JDK 1.8 >Reporter: Vladimir Konkov >Assignee: Guillaume Nodet > Fix For: 4.1.0, 4.0.7 > > > Similar to KARAF-4159. > To reproduce: > $ feature:install spring-dm-web > $ la > ... > 56 | Active | 30 | 3.2.14.RELEASE_1 | Apache ServiceMix :: Bundles :: > spring-aop > 57 | Active | 30 | 3.2.14.RELEASE_1 | Apache ServiceMix :: Bundles :: > spring-beans > 58 | Active | 30 | 3.2.14.RELEASE_1 | Apache ServiceMix :: Bundles :: > spring-context > 59 | Active | 30 | 3.2.14.RELEASE_1 | Apache ServiceMix :: Bundles :: > spring-context-support > 60 | Active | 30 | 3.2.14.RELEASE_1 | Apache ServiceMix :: Bundles :: > spring-core > 61 | Active | 30 | 3.2.14.RELEASE_1 | Apache ServiceMix :: Bundles :: > spring-expression > ... > 106 | Active | 30 | 3.1.4.RELEASE| Spring AOP > 107 | Active | 30 | 3.1.4.RELEASE| Spring ASM > 108 | Active | 30 | 3.1.4.RELEASE| Spring Beans > 109 | Active | 30 | 3.1.4.RELEASE| Spring Context > 110 | Active | 30 | 3.1.4.RELEASE| Spring Context Support > 111 | Active | 30 | 3.1.4.RELEASE| Spring Core > 112 | Active | 30 | 3.1.4.RELEASE| Spring Expression Language > 113 | Active | 30 | 1.2.1| spring-osgi-web -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4361) Allow dynamic config customization when embedding Karaf using the Main class
[ https://issues.apache.org/jira/browse/KARAF-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4361: Fix Version/s: (was: 4.0.7) 4.0.8 > Allow dynamic config customization when embedding Karaf using the Main class > > > Key: KARAF-4361 > URL: https://issues.apache.org/jira/browse/KARAF-4361 > Project: Karaf > Issue Type: Improvement > Components: karaf-core >Affects Versions: 4.1.0, 4.0.4 >Reporter: Serge Huber >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > Attachments: > KARAF_4361_Allow_dynamic_config_customization_when_embedding_Karaf_using_the_Main_class.patch > > > We are using Karaf by embedding it and basically starting it like this : > {code} > // code to setup System properties > main = new Main(new String[0]); > main.launch(); > {code} > The problem is that the ConfigProperties that are used to startup Karaf are > directly created in the main.launch() method, like this: > {code} > public void launch() throws Exception { > config = new ConfigProperties(); > {code} > Ideally it would be great if we could either have a setter to provide the > config value, so that we could manipulate it before launching. In an embedded > environment this quickly becomes a necessity. For example we would like to > make it possible to have retrieve properties coming from another framework > such as Spring and use those to override config.properties settings in a > dynamic way, without needing to dump them to a file at Karaf startup. I'm > aware of the ${includes} and ${optionals} but those require files to be read > from the disk where here I'm talking about being able to dynamically > manipulate the properties once loaded. > Basically something like this would be fantastic > {code} > // code to setup System properties > main = new Main(new String[0]); > ConfigProperties config = main.getConfig(); > if (config == null) { >config = new ConfigProperties(); > } > // manipulate config in any way desired > main.setConfig(config) > main.launch(); > {code} > The main.launch could then simply be modified to something like this : > {code} > public void launch() throws Exception { > if (config == null) { > config = new ConfigProperties(); > } > {code} > Btw we are using Karaf 4.0.x so having this in both Karaf 4.1.0 and Karaf 4.0 > would be fantastic. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4350) Error while entering percent-symbol (%) between quotation marks in karaf-shell.
[ https://issues.apache.org/jira/browse/KARAF-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4350: Fix Version/s: (was: 4.0.7) 4.0.8 > Error while entering percent-symbol (%) between quotation marks in > karaf-shell. > --- > > Key: KARAF-4350 > URL: https://issues.apache.org/jira/browse/KARAF-4350 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.0.4 > Environment: Linux >Reporter: Lijun Liao > Fix For: 4.1.0, 4.0.8 > > > karaf@root()> echo "a\%b" > Error executing command: bad expression: a\%b -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4336) Add support for ordering of CLI scripts and commands in karaf-maven-plugin
[ https://issues.apache.org/jira/browse/KARAF-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4336: Fix Version/s: (was: 4.0.7) 4.0.8 > Add support for ordering of CLI scripts and commands in karaf-maven-plugin > -- > > Key: KARAF-4336 > URL: https://issues.apache.org/jira/browse/KARAF-4336 > Project: Karaf > Issue Type: Improvement > Components: karaf-tooling >Affects Versions: 4.0.4 >Reporter: Martin Basovník >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > {code:xml} > > > setup1.cli > setup2.cli > > > feature:repo-add camel ${version.camel} > > > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4324) Shell commands and optional @Reference
[ https://issues.apache.org/jira/browse/KARAF-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4324: Fix Version/s: (was: 4.0.7) 4.0.8 > Shell commands and optional @Reference > -- > > Key: KARAF-4324 > URL: https://issues.apache.org/jira/browse/KARAF-4324 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.0.4 >Reporter: J. Brébec >Assignee: Guillaume Nodet >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > > The annotation @Reference have a optional property, but this property is not > used to resolve the dependencies of a command. > Moreover, if I define in a bundle two commands, and one of this command can't > be deployed because of an optional dependencies, then none of the command of > the bundle is not deployed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4314) karaf-maven-plugin issue when parsing feature xmls with entries that contain a newline and/or whitespaces
[ https://issues.apache.org/jira/browse/KARAF-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4314: Fix Version/s: (was: 4.0.7) 4.0.8 > karaf-maven-plugin issue when parsing feature xmls with entries > that contain a newline and/or whitespaces > -- > > Key: KARAF-4314 > URL: https://issues.apache.org/jira/browse/KARAF-4314 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.0.4 >Reporter: Andy Schmidt >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > > The karaf-maven-plugin (tested with 4.0.3 and 4.0.4) has an issue when > parsing feature xmls with entries that contain a newline and/or > whitespaces. > Having an (eclipse auto-formatted) entry like > mvn:org.apache.karaf.features/enterprise/${karaf.version}/xml/features > > causes the plugin to try and create a lock file with the name maven-repository>\apache\karaf\features\enterprise\4.0.4\enterprise-4.0.4-features.xml.part.lock > which in turn causes the following exception to be thrown: > shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not > transfer artifact org.apache.karaf.features:enterprise:xml:features > :4.0.4 from/to maven-srv > (http://maven-srv:8080/nexus/content/groups/kisters-central/): > C:\Users\jfrank\.m2\repository\org\apache\karaf\features\enterprise\4.0.4\enterprise-4.0.4-features > .xml.part.lock (Die Syntax f▒r den Dateinamen, Verzeichnisnamen oder > die Datentr▒gerbezeichnung ist falsch) > at > shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444) > at > shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) > at > shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223) > at > shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294) > at > org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:615) > at > org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:570) > at > org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:548) > at > org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:523) > at > org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download(MavenDownloadTask.java:34) > at > org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:58) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: shaded.org.eclipse.aether.transfer.ArtifactTransferException: > Could not transfer artifact org.apache.karaf.features:enterprise:xml:features > :4.0.4 from/to maven-srv > (http://maven-srv:8080/nexus/content/groups/kisters-central/): > C:\Users\jfrank\.m2\repository\org\apache\karaf\features\enterprise\4.0.4\enterprise-4.0.4-features > .xml.part.lock (Die Syntax f▒r den Dateinamen, Verzeichnisnamen oder > die Datentr▒gerbezeichnung ist falsch) > at > shaded.org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:43) > at > shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355) > at > shaded.org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67) > at > shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:581) > at > shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:249) > at > shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:520) > at > s
[jira] [Updated] (KARAF-4327) Features for spring-security 3.2.x and 4.0.x
[ https://issues.apache.org/jira/browse/KARAF-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4327: Fix Version/s: (was: 4.0.7) 4.0.8 > Features for spring-security 3.2.x and 4.0.x > > > Key: KARAF-4327 > URL: https://issues.apache.org/jira/browse/KARAF-4327 > Project: Karaf > Issue Type: New Feature > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Roland Hauser >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > We'd like to use Spring Security in our application. Currently, the available > feature covers spring-security 3.1.x. We would appriciate, if there would be > a feature for the 3.2.x and 4.0.x release line of spring-security. > Necessary bundles: > spring-security-acl > spring-security-taglibs > spring-security-web > spring-security-config > spring-security-core -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4274) feature bundles not found even though they are in required version range
[ https://issues.apache.org/jira/browse/KARAF-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4274: Fix Version/s: (was: 4.0.7) 4.0.8 > feature bundles not found even though they are in required version range > > > Key: KARAF-4274 > URL: https://issues.apache.org/jira/browse/KARAF-4274 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Amichai Rothman >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > When attempting to install the cxf-http-jetty/3.1.1 feature on Karaf 4.0.4 > (offline), it fails. This feature is comprised of the features cxf-http [3,4) > and jetty [7,10), and bundle > mvn:org.apache.cxf/cxf-rt-transports-http-jetty/3.1.1. > All three of these can be installed and started separately with no probelm, > yet if I try to install the cxf-http-jetty feature itself, there are errors > about missing bundles, which appear to belong to the older jetty 8.1.14 > feature. > So if I understand correctly, it should be using the installed jetty > 9.2.10.v20150310 which is in the required range, but instead it's still > trying to look for the 8.1.14.v20131031 bundles which are not there. > Perhaps related, when configuring karaf-maven-plugin's > features-add-to-repository goal to include the activemq-broker-noweb feature, > and then trying to run karaf with the created offline repo, it gives errors > about missing spring/3.1.4.RELEASE bundles. > activemq-broker-noweb feature (5.13.0) depends on activemq feature depends on > activemq-client feature depends on spring [3.2,4) feature, but at runtime it > fails claiming it's missing spring 3.1.4.RELEASE (even though > 3.2.14.RELEASE_1 is available, installed and started). > So in both cases, it seems to be looking for the wrong (older) unavailable > version at runtime even though the newer version is within the required range > and available. Note that in the jetty case both version are within the > required range, whereas in the activemq case the older version that it claims > is missing is not even in the required range (and the new version that is > within the range and installed is being ignored). > It may be a coincidence, but both problematic dependency features have > arbitrary strings added as part of the version number. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4306) karaf-maven-plugin is not assembling the correct version of dependencies
[ https://issues.apache.org/jira/browse/KARAF-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4306: Fix Version/s: (was: 4.0.7) 4.0.8 > karaf-maven-plugin is not assembling the correct version of dependencies > > > Key: KARAF-4306 > URL: https://issues.apache.org/jira/browse/KARAF-4306 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.0.4 >Reporter: Raman Gupta >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > This is similar to KARAF-3994. > I see that the commit for that issue added the following TODO: > * TODO Need to also check for version ranges. Currently ranges are ignored > and all features matching the name > I have a similar problem -- the generated system repo contains all versions > of a feature that is matched by a range, not just the highest one that > fulfills all of the requirements of the boot features. This is an issue > because the generated repo may contain older (or newer) versions of libraries > that have CVEs against them, which is then flagged by ops. > For example: > My feature depends on spring-dm which depends on spring range [2.5.6,4). At > runtime, Karaf only needs and uses Spring 3.2.14, but my system repo contains > Spring 3.1.4 (as well as three versions of Spring 4), all of which are > defined in the Karaf Spring repo. And of course, Spring 3.1.4 has CVEs > against it, so the system is flagged by ops as using jars with security > problems (even though those jars are not actually used by the app). > Shouldn't the Builder apply the same resolution logic as is used by Karaf > itself, and assemble only those jars? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4290) karaf-maven-plugin uses inactive proxies from settings.xml
[ https://issues.apache.org/jira/browse/KARAF-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4290: Fix Version/s: (was: 4.0.7) 4.0.8 > karaf-maven-plugin uses inactive proxies from settings.xml > -- > > Key: KARAF-4290 > URL: https://issues.apache.org/jira/browse/KARAF-4290 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.0.4 >Reporter: Michael Prescott >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > Attachments: karaf-4290-stack-trace.txt > > > My maven settings.xml has a server defined, but it's inactive: > > charles-proxy > false > http > localhost > > www.google.com|*.example.com > > Nevertheless, when runs, I get IOExceptions related to attempting to contact > the proxy server (which isn't running): > Connect to localhost: [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] > failed: Connection refused: connect -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4275) StaticConfigurationAdmin and NPE with spring dm
[ https://issues.apache.org/jira/browse/KARAF-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4275: Fix Version/s: (was: 4.0.7) 4.0.8 > StaticConfigurationAdmin and NPE with spring dm > --- > > Key: KARAF-4275 > URL: https://issues.apache.org/jira/browse/KARAF-4275 > Project: Karaf > Issue Type: Bug > Components: karaf-profile >Affects Versions: 4.0.4 > Environment: Karaf 4.0.4 with a static distribution >Reporter: J. Brébec >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > Spring DM throw a NPE with a Karaf static distribution, when a configuration > is not bound. The Static ConfigurationAdmin implementation is not compliant > with the specification : getConfiguration should never return null. > A workaround : create an for every configuration a file .cfg in > etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4261) Bundle start-level seems to be ignored at Karaf restart
[ https://issues.apache.org/jira/browse/KARAF-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4261: Fix Version/s: (was: 4.0.7) 4.0.8 > Bundle start-level seems to be ignored at Karaf restart > --- > > Key: KARAF-4261 > URL: https://issues.apache.org/jira/browse/KARAF-4261 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.3 >Reporter: Ralf Steppacher > Fix For: 4.1.0, 4.0.8 > > > AS a workaround for CAMEL-9483 I have set a start-level for my bundles > deployed as part of my features. This works as expected during initial > deployment (order of deployment is according to the start levels I set), but > not during sub-sequent starts of Karaf. It appears the start-level of the > bundles is ignored, meaning the order of deployment of my bundles is more or > less random and I observe the issues described in CAMEL-9483 again. > {{bundle:list}} shows my bundles with the start-levels they have been > originally deployed with, though. > As a workaround I set {{karaf.clean.all = true}} in system.properties. -- 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 ] Jean-Baptiste Onofré updated KARAF-4272: Fix Version/s: (was: 4.0.7) 4.0.8 > 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 > Fix For: 4.1.0, 4.0.8 > > > 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 ] Jean-Baptiste Onofré updated KARAF-4271: Fix Version/s: (was: 4.0.7) 4.0.8 > 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 > Fix For: 4.1.0, 4.0.8 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4260) Setting karaf.clean.all = true breaks service wrapper service script
[ https://issues.apache.org/jira/browse/KARAF-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4260: Fix Version/s: (was: 4.0.7) 4.0.8 > Setting karaf.clean.all = true breaks service wrapper service script > > > Key: KARAF-4260 > URL: https://issues.apache.org/jira/browse/KARAF-4260 > Project: Karaf > Issue Type: Bug > Components: karaf-config >Affects Versions: 4.0.3 >Reporter: Ralf Steppacher >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > > The Karaf service wrapper script is generated such that the PID file is > created in {{$KARAF_HOME/data}}. When setting {{karaf.clean.all = true}} then > the PID file created by the service script gets deleted together with the > data directory. As a result of this the service script reports Karaf as not > running and it is not possible to stop the process via the script. > The PID file location probably should be outside the data directory by > default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4255) karaf-maven-plugin does include unused feature conditional dependencies in assembly
[ https://issues.apache.org/jira/browse/KARAF-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4255: Fix Version/s: (was: 4.0.7) 4.0.8 > karaf-maven-plugin does include unused feature conditional dependencies in > assembly > --- > > Key: KARAF-4255 > URL: https://issues.apache.org/jira/browse/KARAF-4255 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > I am using karaf-maven-plugin to make a custom assembly. > I do include SCR, but I do not include webconsole. > When I look into the system folder of my generated assembly, I can see: > {code} > target/assembly/system/org/apache/felix/org.apache.felix.webconsole.plugins.ds/2.0.2/org.apache.felix.webconsole.plugins.ds-2.0.2.jar > {code} > this correlates to the maven output: > {code} > [INFO] Feature scr is defined as a boot feature > [INFO] == Installing artifact > mvn:org.apache.karaf.scr/org.apache.karaf.scr.command/4.0.3 > [INFO] == Installing artifact mvn:org.apache.felix/org.apache.felix.scr/2.0.2 > [INFO] == Installing artifact > mvn:org.apache.felix/org.apache.felix.scr.compat/1.0.2 > [INFO] == Installing artifact > mvn:org.apache.felix/org.apache.felix.webconsole.plugins.ds/2.0.2 > [INFO] == Installing artifact > mvn:org.apache.felix/org.apache.felix.metatype/1.1.2 > [INFO] == Installing artifact > mvn:org.apache.karaf.scr/org.apache.karaf.scr.management/4.0.3 > {code} > however looking at: > https://github.com/apache/karaf/blob/master/assemblies/features/standard/src/main/feature/feature.xml#L524 > you can see that this is an conditional dependency only. > This is caused by the fact that assembly does not check if the conditional > had been met: > https://github.com/apache/karaf/blob/master/profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java#L822 > I believe we need a check for the conditionals wether the condition is > actually met. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4237) can't install transaction feature and activemq-camel feature: Missing dependency javax.transaction.TransactionManager
[ https://issues.apache.org/jira/browse/KARAF-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4237: Fix Version/s: (was: 4.0.7) 4.0.8 > can't install transaction feature and activemq-camel feature: Missing > dependency javax.transaction.TransactionManager > - > > Key: KARAF-4237 > URL: https://issues.apache.org/jira/browse/KARAF-4237 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 > Environment: ubuntu 14.04, java 7 update 79 (also tried with java 8 > update 45), karaf 3.0.3 camel 2.16.1, activemq 5.13.0 >Reporter: Edward Welch > Fix For: 4.1.0, 4.0.8 > > > I found a little bit of a strange behavior, which I think points to a > possible bug in the features dependency resolver? > Easiest way to reproduce, start with a vanilla 4.0.3 > feature:repo-add activemq 5.13.0 > feature:repo-add camel 2.16.1 > feature:install transaction activemq-camel > bundle:diag > You will see both Apache Aries Transaction Blueprint bundles in Grace Period > waiting for javax.transaction.TransactionManager > Pretty sure this is caused by some bad wiring on a bundle which > activemq-camel brings in, here is that feature descriptor: > {code} > start-level='50'> > spring > dependency='true'>mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/${geronimo-jta-spec-version} > dependency='true'>mvn:commons-pool/commons-pool/${commons-pool-version} > dependency='true'>mvn:org.apache.geronimo.specs/geronimo-jms_1.1_spec/${geronimo-jms-spec-version} > spring-jms > camel-core > mvn:org.apache.camel/camel-jms/${project.version} > > {code} > I see the aries transaction bundles being wired to this bundle coming from > the activemq-camel feature: > mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/${geronimo-jta-spec-version} > What's strange about this, that bundle is marked dependency="true" so I would > think it wouldn't need to be installed at all. > Also peculiar, if you follow this install order: > feature:repo-add activemq 5.13.0 > feature:repo-add camel 2.16.1 > feature:install transaction > feature:install activemq-camel > bundle:diag > There is no issue, so the re-wiring/refresh of the transaction bundles never > happens > Also when I originally posted this on the mailing list: > http://karaf.922171.n3.nabble.com/Missing-dependency-javax-transaction-TransactionManager-with-transaction-feature-and-activemq-camel-td4044354.html > Christian Schneider was unable to reproduce the issue, even though it occurs > 100% of the time for me, so maybe there is something else in play here that I > can't think of. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4217) XML External Entity Injection
[ https://issues.apache.org/jira/browse/KARAF-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4217: Fix Version/s: (was: 4.0.7) 4.0.8 > XML External Entity Injection > - > > Key: KARAF-4217 > URL: https://issues.apache.org/jira/browse/KARAF-4217 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand were used to perform an application > security analysis on the karaf source code. > XML parser configured in MavenConfigService.java:74 does not prevent nor > limit external entities resolution. This can expose the parser to an XML > External Entities attack. See external issue URL. > File: > bundle/core/src/main/java/org/apache/karaf/bundle/core/internal/MavenConfigService.java > Line: 74 > MavenConfigService.java, lines 66-76: > {code} > 66 static String getLocalRepoFromConfig(Dictionary dict) > throws XMLStreamException, FileNotFoundException { > 67 String path = null; > 68 if (dict != null) { > 69 path = (String) dict.get("org.ops4j.pax.url.mvn.localRepository"); > 70 if (path == null) { > 71 String settings = (String) > dict.get("org.ops4j.pax.url.mvn.settings"); > 72 if (settings != null) { > 73 File file = new File(settings); > 74 XMLStreamReader reader = > XMLInputFactory.newFactory().createXMLStreamReader(new FileInputStream(file)); > 75 try { > 76 int event; > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4235) Windows start script requires data dir
[ https://issues.apache.org/jira/browse/KARAF-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4235: Fix Version/s: (was: 4.0.7) 4.0.8 > Windows start script requires data dir > -- > > Key: KARAF-4235 > URL: https://issues.apache.org/jira/browse/KARAF-4235 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > I am observing the following problem > On linux, if I delete the data dir, it is recreated. > On Windows, if I run the start.bat, the output is: > karaf.bat: Ignoring predefined value for KARAF_HOME > karaf.bat: KARAF_DATA is not valid: > "C:\Users\Fabian\Downloads\apache-karaf-4.0.3\bin\..\data" > C:\Users\Fabian\Downloads\apache-karaf-4.0.3\bin> > I checked the difference, and right now I am actually wondering more why it > works on linux, rather than why it doesn't on windows, but I think also n > windows the data dir should be recreated. > STR: > Download Karaf 4.0.3 on windows. > unpack and delete data dir. > try to run start.bat > running karaf.bat will work however -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4211) Portability Flaw: Locale Dependent Comparison
[ https://issues.apache.org/jira/browse/KARAF-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4211: Fix Version/s: (was: 4.0.7) 4.0.8 > Portability Flaw: Locale Dependent Comparison > - > > Key: KARAF-4211 > URL: https://issues.apache.org/jira/browse/KARAF-4211 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand were used to perform an application > security analysis on the karaf source code. > The call to compareTo() on line 109 causes portability problems because it > has different locales which may lead to unexpected output. This may also > circumvent custom validation routines. > File: > features/command/src/main/java/org/apache/karaf/features/command/ListFeaturesCommand.java > Line: 109 > ListFeaturesCommand.java, lines 107-111: > 107 class FeatureComparator implements Comparator { > 108 public int compare(Feature o1, Feature o2) { > 109 return o1.getName().toLowerCase().compareTo( > o2.getName().toLowerCase() ); > 110 } > 111 } -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4213) Public cloneable() Method Without Final ('Object Hijack')
[ https://issues.apache.org/jira/browse/KARAF-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4213: Fix Version/s: (was: 4.0.7) 4.0.8 > Public cloneable() Method Without Final ('Object Hijack') > - > > Key: KARAF-4213 > URL: https://issues.apache.org/jira/browse/KARAF-4213 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand were used to perform an application > security analysis on the karaf source code. > A class has a cloneable() method that is not declared final, which allows an > object to be created without calling the constructor. This can cause the > object to be in an unexpected state. > File: > util\src\main\java\org\apache\karaf\util\collections\CopyOnWriteArrayIdentityList.java > Line: 247 > CopyOnWriteArrayIdentityList.java, lines 246-255: > {code} > 246 @Override > 247 public Object clone() { > 248 try { > 249 CopyOnWriteArrayIdentityList thisClone = > (CopyOnWriteArrayIdentityList) super.clone(); > 250 thisClone.setData(this.getData()); > 251 return thisClone; > 252 } catch (CloneNotSupportedException e) { > 253 throw new RuntimeException("CloneNotSupportedException is not > expected here"); > 254 } > 255 } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4216) Poor Error Handling: Return Inside Finally
[ https://issues.apache.org/jira/browse/KARAF-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4216: Fix Version/s: (was: 4.0.7) 4.0.8 > Poor Error Handling: Return Inside Finally > -- > > Key: KARAF-4216 > URL: https://issues.apache.org/jira/browse/KARAF-4216 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand were used to perform an application > security analysis on the karaf source code. > The method build() in PublickeyBackingEngineFactory.java returns from inside > a finally block on line 52, which will cause exceptions to be lost. > File: > jaas/modules/src/main/java/org/apache/karaf/jaas/modules/publickey/PublickeyBackingEngineFactory.java > Line: 52 > PublickeyBackingEngineFactory.java, lines 40-54: > {code} > 40 public BackingEngine build(Map options) { > 41 PublickeyBackingEngine engine = null; > 42 String usersFile = (String) options.get(USER_FILE); > 43 > 44 File f = new File(usersFile); > 45 Properties users; > 46 try { > 47 users = new Properties(f); > 48 engine = new PublickeyBackingEngine(users); > 49 } catch (IOException ioe) { > 50 logger.warn("Cannot open keys file:" + usersFile); > 51 } finally { > 52 return engine; > 53 } > 54 } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4212) Null Dereference
[ https://issues.apache.org/jira/browse/KARAF-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4212: Fix Version/s: (was: 4.0.7) 4.0.8 > Null Dereference > > > Key: KARAF-4212 > URL: https://issues.apache.org/jira/browse/KARAF-4212 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand were used to perform an application > security analysis on the karaf source code. > The method execute() in LoadTest.java can crash the program by dereferencing > a null pointer on line 71. > File: bundle/core/src/main/java/org/apache/karaf/bundle/command/LoadTest.java > Line: 71 > LoadTest.java, lines 65-74: > {code} > 65 @Override > 66 public Object execute() throws Exception { > 67 if (!confirm(session)) { > 68 return null; > 69 } > 70 final BundleContext bundleContext = > this.bundleContext.getBundle(0).getBundleContext(); > 71 final FrameworkWiring wiring = > bundleContext.getBundle().adapt(FrameworkWiring.class); > 72 final CountDownLatch latch = new CountDownLatch(threads); > 73 final Bundle[] bundles = bundleContext.getBundles(); > 74 final AtomicBoolean[] locks = new AtomicBoolean[bundles.length]; > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4215) Use of Dynamic Class Loading, Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
[ https://issues.apache.org/jira/browse/KARAF-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4215: Fix Version/s: (was: 4.0.7) 4.0.8 > Use of Dynamic Class Loading, Use of Externally-Controlled Input to Select > Classes or Code ('Unsafe Reflection') > > > Key: KARAF-4215 > URL: https://issues.apache.org/jira/browse/KARAF-4215 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand were used to perform an application > security analysis on the karaf source code. > Dynamically loaded code has the potential to be malicious. The application > uses external input with reflection to select which classes or code to use, > but it does not sufficiently prevent the input from selecting improper > classes or code. The constructor for DefaultJDBCLock includes one parameter > for a Properties object from which the parameters for the dynamic class are > taken. None of the properties are checked for content. > File: main\src\main\java\org\apache\karaf\main\lock\DefaultJDBCLock.java > Line: 365 > DefaultJDBCLock.java, lines 364-369: > {code} > 364 Connection doCreateConnection(String driver, String url, String username, > String password) throws ClassNotFoundException, SQLException { > 365 Class.forName(driver); > 366 // results in a closed connection in Derby if the update lock table > request timed out > 367 // DriverManager.setLoginTimeout(timeout); > 368 return DriverManager.getConnection(url, username, password); > 369 } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4214) Deserialization of Untrusted Data
[ https://issues.apache.org/jira/browse/KARAF-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4214: Fix Version/s: (was: 4.0.7) 4.0.8 > Deserialization of Untrusted Data > - > > Key: KARAF-4214 > URL: https://issues.apache.org/jira/browse/KARAF-4214 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand were used to perform an application > security analysis on the karaf source code. > The application deserializes untrusted data without sufficiently verifying > that the resulting data will be valid. An adversary could attack the > application by tampering with the resource "karaf.key". > File: client\src\main\java\org\apache\karaf\client\Main.java > Line: 297 > Main.java, lines 291-313: > {code} > 291 private static SshAgent startAgent(String user, URL privateKeyUrl, String > keyFile) { > 292 InputStream is = null; > 293 try { > 294 SshAgent agent = new AgentImpl(); > 295 is = privateKeyUrl.openStream(); > 296 ObjectInputStream r = new ObjectInputStream(is); > 297 KeyPair keyPair = (KeyPair) r.readObject(); > 298 is.close(); > 299 agent.addIdentity(keyPair, user); > 300 if (keyFile != null) { > 301 String[] keyFiles = new String[]{keyFile}; > 302 FileKeyPairProvider fileKeyPairProvider = new > FileKeyPairProvider(keyFiles); > 303 for (KeyPair key : fileKeyPairProvider.loadKeys()) { > 304 agent.addIdentity(key, user); > 305 } > 306 } > 307 return agent; > 308 } catch (Throwable e) { > 309 close(is); > 310 System.err.println("Error starting ssh agent for: " + > e.getMessage()); > 311 return null; > 312 } > 313 } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4208) Poor Error Handling: Empty Catch Block
[ https://issues.apache.org/jira/browse/KARAF-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4208: Fix Version/s: (was: 4.0.7) 4.0.8 > Poor Error Handling: Empty Catch Block > -- > > Key: KARAF-4208 > URL: https://issues.apache.org/jira/browse/KARAF-4208 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand were used to perform an application > security analysis of the karaf source code. > The method authenticate() in JaasSecurityProvider.java ignores an exception > on line 215, which could cause the program to overlook unexpected states and > conditions. In this case an authentication has failed and the attempt to > respond to the client and let them know has also failed. The comment > indicates that nothing can be done about the problem but the issue should be > logged for further investigation or forensics purposes. > File: > webconsole/console/src/main/java/org/apache/felix/webconsole/internal/servlet/JaasSecurityProvider.java > Line: 215 > JaasSecurityProvider.java, lines 207-218: > {code} > 207 // request authentication > 208 try > 209 { > 210 response.setHeader( HEADER_WWW_AUTHENTICATE, > AUTHENTICATION_SCHEME_BASIC + " realm=\"" + this.realm + "\"" ); > 211 response.setStatus( HttpServletResponse.SC_UNAUTHORIZED ); > 212 response.setContentLength( 0 ); > 213 response.flushBuffer(); > 214 } > 215 catch ( IOException ioe ) > 216 { > 217 // failed sending the response ... cannot do anything about it > 218 } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4205) Privacy Violation
[ https://issues.apache.org/jira/browse/KARAF-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4205: Fix Version/s: (was: 4.0.7) 4.0.8 > Privacy Violation > - > > Key: KARAF-4205 > URL: https://issues.apache.org/jira/browse/KARAF-4205 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand were used to perform an application > security analysis of the karaf source code. > The method find() in GogoParser.java mishandles confidential information, > which can compromise user privacy and is often illegal. > File: > shell/core/src/main/java/org/apache/karaf/shell/support/parsing/GogoParser.java > Line: 332 > GogoParser.java, lines 329-333: > 329 while (level != 0) { > 330 if (eof()) { > 331 throw new RuntimeException("Eof found in the middle of a compound > for '" > 332 + target + deeper + "', begins at " + context(start)); > 333 } -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4210) Unreleased Resource: Streams
[ https://issues.apache.org/jira/browse/KARAF-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4210: Fix Version/s: (was: 4.0.7) 4.0.8 > Unreleased Resource: Streams > > > Key: KARAF-4210 > URL: https://issues.apache.org/jira/browse/KARAF-4210 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand were used to perform an application > security analysis on the karaf source code. > The function getLocalRepoFromConfig() in MavenConfigService.java sometimes > fails to release a system resource allocated by FileInputStream() on line 74. > File: > bundle/core/src/main/java/org/apache/karaf/bundle/core/internal/MavenConfigService.java > Line: 74 > MavenConfigService.java, lines 66-76: > 66 static String getLocalRepoFromConfig(Dictionary dict) > throws XMLStreamException, FileNotFoundException { > 67 String path = null; > 68 if (dict != null) { > 69 path = (String) dict.get("org.ops4j.pax.url.mvn.localRepository"); > 70 if (path == null) { > 71 String settings = (String) > dict.get("org.ops4j.pax.url.mvn.settings"); > 72 if (settings != null) { > 73 File file = new File(settings); > 74 XMLStreamReader reader = > XMLInputFactory.newFactory().createXMLStreamReader(new FileInputStream(file)); > 75 try { > 76 int event; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4209) Weak XML Schema: Unbounded Occurrences
[ https://issues.apache.org/jira/browse/KARAF-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4209: Fix Version/s: (was: 4.0.7) 4.0.8 > Weak XML Schema: Unbounded Occurrences > -- > > Key: KARAF-4209 > URL: https://issues.apache.org/jira/browse/KARAF-4209 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand were used to perform an application > security analysis on the karaf source code. > Setting a maxOccurs value to unbounded can lead to resources exhaustion and > ultimately a denial of service. > File: > features/core/src/main/resources/org/apache/karaf/features/karaf-features-1.0.0.xsd > Line: 64 > karaf-features-1.0.0.xsd, lines 64-77: > 64 > 65 > 66 > 67 > 70 > 71 > 72 > 73 > 74 > 75 > 76 > 77 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4206) Session Fixation
[ https://issues.apache.org/jira/browse/KARAF-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4206: Fix Version/s: (was: 4.0.7) 4.0.8 > Session Fixation > > > Key: KARAF-4206 > URL: https://issues.apache.org/jira/browse/KARAF-4206 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand was used to perform an application > security analysis on the karaf source code. > On line 69 of SuCommand.java the method execute() authenticates users without > invalidating the existing session identifier, giving an attacker the > opportunity to steal authenticated sessions. An existing session should be > invalidated by calling HttpSession.invalidate() prior to calling > loginContext.login(). > File: jaas/command/src/main/java/org/apache/karaf/jaas/command/SuCommand.java > Line: 69 > SuCommand.java, lines 52-69: > {code} > 52 @Override > 53 public Object execute() throws Exception { > 54 Subject subject = new Subject(); > 55 LoginContext loginContext = new LoginContext(realm, subject, new > CallbackHandler() { > 56 public void handle(Callback[] callbacks) throws IOException, > UnsupportedCallbackException { > 57 for (Callback callback : callbacks) { > 58 if (callback instanceof NameCallback) { > 59 ((NameCallback) callback).setName(user); > 60 } else if (callback instanceof PasswordCallback) { > 61 String password = > SuCommand.this.session.readLine("Password: ", '*'); > 62 ((PasswordCallback) > callback).setPassword(password.toCharArray()); > 63 } else { > 64 throw new UnsupportedCallbackException(callback); > 65 } > 66 } > 67 } > 68 }); > 69 loginContext.login(); > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4203) Access Specifier Manipulation
[ https://issues.apache.org/jira/browse/KARAF-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4203: Fix Version/s: (was: 4.0.7) 4.0.8 > Access Specifier Manipulation > - > > Key: KARAF-4203 > URL: https://issues.apache.org/jira/browse/KARAF-4203 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand were used to perform an application > security of the karaf source code. > The call to method setAccessible() on line 355 changes an access specifier. > See the external issue link for more information on the subject. > File: client/src/main/java/org/apache/karaf/client/Main.java > Line: 355 > Main.java, lines 353-362: > {code} > 353 try { > 354 Field field = > terminal.getClass().getSuperclass().getDeclaredField("settings"); > 355 field.setAccessible(true); > 356 Object settings = field.get(terminal); > 357 field = settings.getClass().getDeclaredField("configLastFetched"); > 358 field.setAccessible(true); > 359 field.setLong(settings, 0L); > 360 } catch (Throwable t) { > 361 // Ignore > 362 } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4204) Weak SecurityManager Check: Overridable Method
[ https://issues.apache.org/jira/browse/KARAF-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4204: Fix Version/s: (was: 4.0.7) 4.0.8 > Weak SecurityManager Check: Overridable Method > -- > > Key: KARAF-4204 > URL: https://issues.apache.org/jira/browse/KARAF-4204 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify SCA and SciTools Understand were used to perform an application > security analysis of the karaf source code. > Non-final methods that perform security checks can be overridden in ways that > bypass security checks. See external issue for more information. > File: exception/src/main/java/java/lang/Exception.java > Line: 137 > Exception.java, lines 137-153: > {code} > 137 public Class[] getThrowableContext(Throwable t) { > 138 try { > 139 Class[] context = getClassContext(); > 140 int nb = 0; > 141 for (;;) { > 142 if (context[context.length - 1 - nb] == t.getClass()) { > 143 break; > 144 } > 145 nb++; > 146 } > 147 Class[] nc = new Class[nb]; > 148 System.arraycopy(context, context.length - nb, nc, 0, nb); > 149 return nc; > 150 } catch (Exception e) { > 151 return null; > 152 } > 153 } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4201) Often Misused: Authentication
[ https://issues.apache.org/jira/browse/KARAF-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4201: Fix Version/s: (was: 4.0.7) 4.0.8 > Often Misused: Authentication > - > > Key: KARAF-4201 > URL: https://issues.apache.org/jira/browse/KARAF-4201 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify and SciTools Understand were used to perform an application > security scan on the karaf source code. > The information returned by the call to getByName() on line 150 is not > trustworthy. Attackers can spoof DNS entries. > File: main/src/main/java/org/apache/karaf/main/InstanceHelper.java > Line: 150 > InstanceHelper.java, lines 142-166: > {code} > 142 static void setupShutdown(ConfigProperties config, Framework framework) { > 143 writePid(config.pidFile); > 144 try { > 145 int port = config.shutdownPort; > 146 String host = config.shutdownHost; > 147 String portFile = config.portFile; > 148 final String shutdown = config.shutdownCommand; > 149 if (port >= 0) { > 150 ServerSocket shutdownSocket = new ServerSocket(port, 1, > InetAddress.getByName(host)); > 151 if (port == 0) { > 152 port = shutdownSocket.getLocalPort(); > 153 } > 154 if (portFile != null) { > 155 Writer w = new OutputStreamWriter(new > FileOutputStream(portFile)); > 156 w.write(Integer.toString(port)); > 157 w.close(); > 158 } > 159 Thread thread = new ShutdownSocketThread(shutdown, > shutdownSocket, framework); > 160 thread.setDaemon(true); > 161 thread.start(); > 162 } > 163 } catch (Exception e) { > 164 e.printStackTrace(); > 165 } > 166 } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4200) Privacy Violation: Heap Inspection
[ https://issues.apache.org/jira/browse/KARAF-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4200: Fix Version/s: (was: 4.0.7) 4.0.8 > Privacy Violation: Heap Inspection > -- > > Key: KARAF-4200 > URL: https://issues.apache.org/jira/browse/KARAF-4200 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify and SciTools Understand were used to perform an application > security scan on the karaf source code. > The method login() in JDBCLoginModule.java stores sensitive data in a String > object on line 95, making it impossible to reliably purge the data from > memory. > JDBCLoginModule.java, lines 88-96: > {code} > 88 user = ((NameCallback) callbacks[0]).getName(); > 89 > 90 char[] tmpPassword = ((PasswordCallback) callbacks[1]).getPassword(); > 91 if (tmpPassword == null) { > 92 tmpPassword = new char[0]; > 93 } > 94 > 95 String password = new String(tmpPassword); > 96 principals = new HashSet<>(); > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4192) java.lang.ClassCastException in org.apache.karaf.features.internal.region.CandidateComparator
[ https://issues.apache.org/jira/browse/KARAF-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4192: Fix Version/s: (was: 4.0.7) 4.0.8 > java.lang.ClassCastException in > org.apache.karaf.features.internal.region.CandidateComparator > - > > Key: KARAF-4192 > URL: https://issues.apache.org/jira/browse/KARAF-4192 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.3 >Reporter: Per Kristian Söreide >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > The system bundle will return a String[] {"org.apache.felix.framework", > "system.bundle"} on line 57 in CandidateComparator: > {noformat} > c = ((Comparable) > cap1.getAttributes().get(BundleNamespace.BUNDLE_NAMESPACE)) > > .compareTo(cap2.getAttributes().get(BundleNamespace.BUNDLE_NAMESPACE));{noformat} > This is causing a ClassCastException being thrown. > Equinox will return an ArrayList (seen in the stacktrace) > Stacktrace: > {noformat} > java.lang.ClassCastException: java.util.ArrayList cannot be cast to > java.lang.Comparable > at > org.apache.karaf.features.internal.region.CandidateComparator.compare(CandidateComparator.java:57) > at > org.apache.karaf.features.internal.region.CandidateComparator.compare(CandidateComparator.java:31) > at java.util.TimSort.binarySort(TimSort.java:265) > at java.util.TimSort.sort(TimSort.java:208) > at java.util.TimSort.sort(TimSort.java:173) > at java.util.Arrays.sort(Arrays.java:659) > at java.util.Collections.sort(Collections.java:217) > at > org.apache.karaf.features.internal.region.SubsystemResolveContext.findProviders(SubsystemResolveContext.java:260) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:272) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637) > at > org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273) > at > org.apache.feli
[jira] [Updated] (KARAF-4181) blacklist.properties is not a properties file
[ https://issues.apache.org/jira/browse/KARAF-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4181: Fix Version/s: (was: 4.0.7) 4.0.8 > blacklist.properties is not a properties file > - > > Key: KARAF-4181 > URL: https://issues.apache.org/jira/browse/KARAF-4181 > Project: Karaf > Issue Type: Bug > Components: karaf-profile >Affects Versions: 4.0.3 >Reporter: Benson Margulies >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > 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] [Updated] (KARAF-4199) Privacy Violation: Heap Inspection
[ https://issues.apache.org/jira/browse/KARAF-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4199: Fix Version/s: (was: 4.0.7) 4.0.8 > Privacy Violation: Heap Inspection > -- > > Key: KARAF-4199 > URL: https://issues.apache.org/jira/browse/KARAF-4199 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Eduardo Aguinaga > Fix For: 4.1.0, 4.0.8 > > > HP Fortify and SciTools Understand were used to perform an application > security scan on the karaf source code. > The method interactive() in Main.java stores sensitive data in a String > object on line 127, making it impossible to reliably purge the data from > memory. > Main.java, lines 120-137: > {code} > 120 public String[] interactive(String destination, String name, String > instruction, String[] prompt, boolean[] echo) { > 121 String[] answers = new String[prompt.length]; > 122 try { > 123 for (int i = 0; i < prompt.length; i++) { > 124 if (echo[i]) { > 125 answers[i] = console.readLine(prompt[i] + " "); > 126 } else { > 127 answers[i] = new String(console.readPassword(prompt[i] + > " ")); > 128 } > 129 if (answers[i] == null) { > 130 return null; > 131 } > 132 } > 133 return answers; > 134 } catch (IOError e) { > 135 return null; > 136 } > 137 } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4162) Wrap deployer does not add default versions to exported packages
[ https://issues.apache.org/jira/browse/KARAF-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4162: Fix Version/s: (was: 4.0.7) 4.0.8 > Wrap deployer does not add default versions to exported packages > > > Key: KARAF-4162 > URL: https://issues.apache.org/jira/browse/KARAF-4162 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.3 >Reporter: Aleksei Lissitsin > Fix For: 4.1.0, 4.0.8 > > Attachments: export-package-actual.txt, export-package-expected.txt, > spring-beans-4.1.7.RELEASE.jar > > > Wrap deployer does not add default versions to exported packages but should. > Try, e.g., with the provided spring-beans jar. > My attempts to override this behaviour by using bundle:install with wrap url > containing '-nodefaultversion=false' failed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4124) feature config installer adds property to config
[ https://issues.apache.org/jira/browse/KARAF-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4124: Fix Version/s: (was: 4.0.7) 4.0.8 > feature config installer adds property to config > > > Key: KARAF-4124 > URL: https://issues.apache.org/jira/browse/KARAF-4124 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.3 >Reporter: Markus Rathgeb >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > The element in a feature XML allows a feature to create and/or > populate a configuration (identified by a configuration PID). > The "FeatureConfigInstaller" adds a custom property to the configuration. > key = "org.apache.karaf.features.configKey" > value = result of function call "createConfigurationKey(pid[0], pid[1])" > There are bundles that cannot handle additional properties in the > configuration. > For example: > * using Aries JPA + Hiberante + h2 > * the configuration is installed by a feature and a realted config entry > * this will result in a non working setup > {noformat} > Caused by: org.h2.jdbc.JdbcSQLException: Unsupported connection setting > "ORG.APACHE.KARAF.FEATURES.CONFIGKEY" [90113-172] > at > org.h2.message.DbException.getJdbcSQLException(DbException.java:329) > at org.h2.message.DbException.get(DbException.java:169) > at org.h2.message.DbException.get(DbException.java:146) > at > org.h2.engine.ConnectionInfo.readSettingsFromURL(ConnectionInfo.java:266) > at org.h2.engine.ConnectionInfo.(ConnectionInfo.java:77) > at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:90) > at org.h2.Driver.connect(Driver.java:73) > at > org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:187) > at > org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:323) > at > org.apache.commons.dbcp2.managed.DataSourceXAConnectionFactory.createConnection(DataSourceXAConnectionFactory.java:112) > at > org.apache.commons.dbcp2.managed.PoolableManagedConnectionFactory.makeObject(PoolableManagedConnectionFactory.java:66) > at > org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:868) > at > org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:435) > at > org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363) > at > org.apache.commons.dbcp2.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:127) > ... 132 more > {noformat} > There is a conditional branch in the "findExistingConfiguration" function to > filter (find) the configuration using that property instead of the > service.pid (this is another conditional branch). > Is there any reason for using that property? > I changed the "FeatureConfigInstaller" to not append that property and the > above example is working now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4174) NullPointerException when running obr:info on a bundle served by cave
[ https://issues.apache.org/jira/browse/KARAF-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4174: Fix Version/s: (was: 4.0.7) 4.0.8 > NullPointerException when running obr:info on a bundle served by cave > - > > Key: KARAF-4174 > URL: https://issues.apache.org/jira/browse/KARAF-4174 > Project: Karaf > Issue Type: Bug > Components: cave-server, karaf-repository >Affects Versions: 4.0.4 >Reporter: Marton Papp >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, cave-4.0.1, 4.0.8 > > > Hello, > I am using Cave 4.0.0 with Karaf 4.0.4-SNAPSHOT (after having the same > problem with 4.0.3) and I get a NullPointerException when running the > obr:info command on a bundle. > To reproduce: > __ __ >/ //_/ __ _/ __/ > / ,< / __ `/ ___/ __ `/ /_ > / /| |/ /_/ / / / /_/ / __/ > /_/ |_|\__,_/_/ \__,_/_/ > Apache Karaf (4.0.4-SNAPSHOT) > Hit '' for a list of available commands > and '[cmd] --help' for help on a specific command. > Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf. > karaf@root()> feature:repo-add cave 4.0.0 > Adding feature url > mvn:org.apache.karaf.cave/apache-karaf-cave/4.0.0/xml/features > karaf@root()> feature:install cave-server > karaf@root()> cave:repository-create my-repository > karaf@root()> cave:repository-upload my-repository > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.ant/1.7.0_5 > karaf@root()> feature:install obr > karaf@root()> obr:url-add > http://localhost:8181/cave/http/my-repository-repository.xml > karaf@root()> obr:list > Name | Symbolic Name | Version > -- > | org.apache.servicemix.bundles.ant | 1.7.0.5 > karaf@root()> obr:info org.apache.servicemix.bundles.ant > Error executing command: java.lang.NullPointerException > karaf@root()> display -n 3 > 2015-12-05 18:40:26,319 | INFO | pool-50-thread-1 | bundle > | 56 - org.apache.aries.spifly.dynamic.bundle - 1.0.1 | No > 'SPI-Provider' Manifest header. Skipping bundle: org.apache.karaf.obr.core > 2015-12-05 18:40:26,319 | INFO | pool-50-thread-1 | FeaturesServiceImpl > | 9 - org.apache.karaf.features.core - 4.0.4.SNAPSHOT | Done. > 2015-12-05 18:40:40,518 | ERROR | nsole user karaf | ShellUtil > | 44 - org.apache.karaf.shell.core - 4.0.4.SNAPSHOT | Exception > caught while executing command > java.lang.NullPointerException > at > org.apache.karaf.obr.command.InfoCommand.printResource(InfoCommand.java:65)[118:org.apache.karaf.obr.core:4.0.4.SNAPSHOT] > at > org.apache.karaf.obr.command.InfoCommand.doExecute(InfoCommand.java:57)[118:org.apache.karaf.obr.core:4.0.4.SNAPSHOT] > at > org.apache.karaf.obr.command.ObrCommandSupport.execute(ObrCommandSupport.java:58)[118:org.apache.karaf.obr.core:4.0.4.SNAPSHOT] > at > org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.felix.gogo.runtime.Closure.execute(Closure.java:182)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.felix.gogo.runtime.Closure.execute(Closure.java:119)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:94)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:270)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at java.lang.Thread.run(Thread.java:745)[:1.8.0_60] > karaf@root()> > Regards -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4060) Display a warning when we remove a repo containing installed features
[ https://issues.apache.org/jira/browse/KARAF-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4060: Fix Version/s: (was: 4.0.7) 4.0.8 > Display a warning when we remove a repo containing installed features > - > > Key: KARAF-4060 > URL: https://issues.apache.org/jira/browse/KARAF-4060 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 4.1.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > When we add a feature repo, and we install features from this repo, if after > that, we remove the repo, the features are not displayed anymore (but the > bundles are still installed). It's not obvious for the user in which state > the features are. > We should display a warning when doing feature:repo-remove while we have some > features from this repo installed (or even don't allow to remove the repo). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4109) For backward compatibility, support the resolver attribute in features XML
[ https://issues.apache.org/jira/browse/KARAF-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4109: Fix Version/s: (was: 4.0.7) 4.0.8 > For backward compatibility, support the resolver attribute in features XML > -- > > Key: KARAF-4109 > URL: https://issues.apache.org/jira/browse/KARAF-4109 > Project: Karaf > Issue Type: Bug > Components: karaf-archetypes, karaf-feature >Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.0.3 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > The resolver attribute in features XML is not supported anymore throwing > errors at installation time. > We have to: > 1. fix the feature archetype to remove the reference to the resolver attribute > 2. for backward compatibility, it makes sense to support the resolver > attribute even if we don't really use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4104) NPE in Felix FileInstall
[ https://issues.apache.org/jira/browse/KARAF-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4104: Fix Version/s: (was: 4.0.7) 4.0.8 > NPE in Felix FileInstall > > > Key: KARAF-4104 > URL: https://issues.apache.org/jira/browse/KARAF-4104 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > > Got this from a custom karaf assembly (using the karaf maven plugin) > {code} > 2015-11-12 09:54:15,019 | INFO | nd.bundle.watch) | fileinstall > | 6 - org.apache.felix.fileinstall - 3.5.0 | Unable to save > configuration > java.lang.NullPointerException > at > org.apache.felix.fileinstall.internal.ConfigInstaller.configurationEvent(ConfigInstaller.java:106)[6:org.apache.felix.fileinstall:3.5.0] > at > org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.sendEvent(ConfigurationManager.java:2036)[5:org.apache.felix.configadmin:1.8.4] > at > org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.run(ConfigurationManager.java:2005)[5:org.apache.felix.configadmin:1.8.4] > at > org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)[5:org.apache.felix.configadmin:1.8.4] > at java.lang.Thread.run(Thread.java:744)[:1.7.0_45] > {code} > That is all there is in the log and its repeated endless. > I guess its the felix file watcher that fails somehow. But nevertheless would > be good to get the felix guys to fix a potential NPE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4105) karaf-assembly fails when used Maven versions do not match derived OSGi versions
[ https://issues.apache.org/jira/browse/KARAF-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4105: Fix Version/s: (was: 4.0.7) 4.0.8 > karaf-assembly fails when used Maven versions do not match derived OSGi > versions > > > Key: KARAF-4105 > URL: https://issues.apache.org/jira/browse/KARAF-4105 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.0.3 >Reporter: Oliver Lietz >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > e.g. {{$\{project.version\}}} {{0.1.1-SNAPSHOT}} and {{0.1.1.SNAPSHOT}} do > not match in {{org.apache.karaf.profile.assembly.Builder}} > See mail thread [\[K4.0.3\] custom distribution and > kar|http://mail-archives.apache.org/mod_mbox/karaf-user/201511.mbox/%3c7781910.EKNrsAyV2X@madness%3e] > for more. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3995) installAllFeaturesByDefault is not documented
[ https://issues.apache.org/jira/browse/KARAF-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3995: Fix Version/s: (was: 4.0.7) 4.0.8 > 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 >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > @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] [Updated] (KARAF-4092) feature.xml to support SystemProperties
[ https://issues.apache.org/jira/browse/KARAF-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4092: Fix Version/s: (was: 4.0.7) 4.0.8 > feature.xml to support SystemProperties > --- > > Key: KARAF-4092 > URL: https://issues.apache.org/jira/browse/KARAF-4092 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Amit Patel >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.9, 4.0.8 > > > We need feature.xml file to have access to systemProperty. For example we are > using feature in below format and it has and > define in SystemProperty file. so we can externalized the jar file location > and it can be specified at runtime though SystemProperties > > start="true">file:/ajsc-jars/osgiservice1//-.jar > - > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3952) Be able to provide full ObjectName to registerMBean()
[ https://issues.apache.org/jira/browse/KARAF-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3952: Fix Version/s: (was: 4.0.7) 4.0.8 > Be able to provide full ObjectName to registerMBean() > - > > Key: KARAF-3952 > URL: https://issues.apache.org/jira/browse/KARAF-3952 > Project: Karaf > Issue Type: Improvement > Components: karaf-util >Affects Versions: 4.0.1 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > Karaf util provides the convenient registerMBean() method. However, when you > want to provide a full ObjectName, the workaround is to use: > {code} > Hashtable props = new Hashtable(); > props.put("jmx.objectname", "org.apache.karaf.cellar:type=core,name=" > + System.getProperty("karaf.name")); > coreMBeanRegistration = > bundleContext.registerService(getInterfaceNames(cellarMBean), cellarMBean, > props); > {code} > To simplify the writing, it would be great that the registerMBean() method > accept the complete ObjectName (instead of only type as currently). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3810) Feature verify goal fail on Windows (for standard features)
[ https://issues.apache.org/jira/browse/KARAF-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3810: Fix Version/s: (was: 4.0.7) 4.0.8 > Feature verify goal fail on Windows (for standard features) > --- > > Key: KARAF-3810 > URL: https://issues.apache.org/jira/browse/KARAF-3810 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.0 >Reporter: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > On Windows, the verify goal fails on some standard features. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3976) Broken compatibility with 3.x jdbc DataSources
[ https://issues.apache.org/jira/browse/KARAF-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3976: Fix Version/s: (was: 4.0.7) 4.0.8 > Broken compatibility with 3.x jdbc DataSources > -- > > Key: KARAF-3976 > URL: https://issues.apache.org/jira/browse/KARAF-3976 > Project: Karaf > Issue Type: Bug > Components: karaf-jdbc >Affects Versions: 4.0.1 >Reporter: Sergey >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > 1st of all, current documentaion is wrong, because command names was changed > to jdbc:ds-info, for example, but > http://karaf.apache.org/manual/latest/users-guide/jdbc.html still contains > jdbc:info command names. > Most important compatibility breaking change was another one: in karaf 3.x I > was able to deploy DataSource using spring-dm xml or blueprint, and it was > registered as a service and in jndi, and was listed using jdbc:datasources > command. Right now no datasources are listed. > {code} > karaf@root()> jndi:names > JNDI Name | Class Name > -- > osgi:service/jdbc/zeusDataSource | > net.sourceforge.jtds.jdbcx.JtdsDataSource > osgi:service/jdbc/arenaDS | > net.sourceforge.jtds.jdbcx.JtdsDataSource > osgi:service/jdbc/tomsDS | > net.sourceforge.jtds.jdbcx.JtdsDataSource > osgi:service/jdbc/cofDS | > com.sybase.jdbc3.jdbc.SybDataSource > osgi:service/jdbc/fidbDataSource | > net.sourceforge.jtds.jdbcx.JtdsDataSource > osgi:service/jdbc/murexDS | > com.sybase.jdbc3.jdbc.SybDataSource > osgi:service/jdbc/gpDataSource| > org.postgresql.ds.PGPoolingDataSource > karaf@root()> jdbc:ds-info jdbc/fidbDataSource > Property | Value > - > driver.version | 1.2.2 > db.version | 10.50.4000 > db.product | Microsoft SQL Server > url| jdbc:jtds:sqlserver: > driver.name| jTDS Type 4 JDBC Driver for MS SQL Server and Sybase > username | ... > karaf@root()> jdbc:ds-list > Name | Product | Version | URL | Status > --- > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3989) Manual broken because images can't be loaded.
[ https://issues.apache.org/jira/browse/KARAF-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3989: Fix Version/s: (was: 4.0.7) 4.0.8 > Manual broken because images can't be loaded. > - > > Key: KARAF-3989 > URL: https://issues.apache.org/jira/browse/KARAF-3989 > Project: Karaf > Issue Type: Bug > Components: karaf-documentation >Affects Versions: 4.0.1 >Reporter: Tobias Hochgürtel >Priority: Minor > Labels: documentation > Fix For: 4.1.0, 4.0.8 > > Attachments: 2015-09-13 12_31_20-Greenshot.png > > > Webpage: http://karaf.apache.org/index/community/download.html > - HTML Version of the Manuel can't load the images. > - PDF Version has also no images. > I think that the PDF Version is generated from the HTML Version and so this > affects also to pdf. > I reported this as first to Karaf User Mailing List [Karaf 4.0.1 Manual > HTML/PDF can not be accessed. (404 > Error)|http://karaf.922171.n3.nabble.com/Karaf-4-0-1-Manual-HTML-PDF-can-not-be-accessed-404-Error-td4042543.html]. > !2015-09-13 12_31_20-Greenshot.png|title=Screenshot shows the Issue side by > side for PDF and HTML Version, width=800! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3973) Bundles refresh doesn't work (bundles not resolved)
[ https://issues.apache.org/jira/browse/KARAF-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3973: Fix Version/s: (was: 4.0.7) 4.0.8 > Bundles refresh doesn't work (bundles not resolved) > --- > > Key: KARAF-3973 > URL: https://issues.apache.org/jira/browse/KARAF-3973 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.1 >Reporter: Amichai Rothman >Priority: Critical > Fix For: 4.1.0, 4.0.8 > > > I have a bunch of bundles copied into the deploy folder of a fresh karaf > 4.0.1 installation. The first time karaf runs, the bundles are not properly > resolved, and apparently this has to do with the order in which they are > loaded, i.e. if A depends on B and A is loaded first, then when B is loaded > it is properly resolved but A never gets resolved. running the refresh > command from console does not help either. However, if karaf itself is > restarted, then everything is resolved and activated with no problem. > In Karaf up to 3.0.3 this was not an issue - the moment B was loaded, even on > the first time Karaf is run, A would automatically get resolved/activated as > well. on 3.0.4 I get a deadlock on startup, so can't really tell if it works > (see KARAF-3941). on 4.0.0 I haven't tried. 4.0.1 is the current reported > issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3825) Add ability to shutdown Karaf with a disabled shutdown port
[ https://issues.apache.org/jira/browse/KARAF-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3825: Fix Version/s: (was: 4.0.7) 4.0.8 > Add ability to shutdown Karaf with a disabled shutdown port > --- > > Key: KARAF-3825 > URL: https://issues.apache.org/jira/browse/KARAF-3825 > Project: Karaf > Issue Type: Improvement > Components: karaf-core >Affects Versions: 3.0.3, 4.0.0 >Reporter: Dmitry Konstantinov >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.9, 4.0.8 > > > Sometimes by security reasons listen ports are asked to disable. It would be > nice to provide an alternative way to trigger Karaf shutdown by touching a > special file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3779) Be able to define the copied location of the kar files
[ https://issues.apache.org/jira/browse/KARAF-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3779: Fix Version/s: (was: 4.0.7) 4.0.8 > Be able to define the copied location of the kar files > -- > > Key: KARAF-3779 > URL: https://issues.apache.org/jira/browse/KARAF-3779 > Project: Karaf > Issue Type: Improvement > Components: karaf-kar >Affects Versions: 2.3.8, 3.0.4, 4.0.0, 2.4.3 >Reporter: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > On Karaf 2.3.x, the kar files are copied into the system folder. It would be > great to configure where Karaf copies the kar files (in the kar service > blueprint xml) using a property in etc/org.apache.karaf.kar.cfg. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3588) Support runtime installation of libraries defined in features
[ https://issues.apache.org/jira/browse/KARAF-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3588: Fix Version/s: (was: 4.0.7) 4.0.8 > Support runtime installation of libraries defined in features > - > > Key: KARAF-3588 > URL: https://issues.apache.org/jira/browse/KARAF-3588 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.0.0.M3 >Reporter: Guillaume Nodet > Fix For: 4.1.0, 4.0.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3572) Override resources for instance:create in custom distributions
[ https://issues.apache.org/jira/browse/KARAF-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3572: Fix Version/s: (was: 4.0.7) 4.0.8 > Override resources for instance:create in custom distributions > -- > > Key: KARAF-3572 > URL: https://issues.apache.org/jira/browse/KARAF-3572 > Project: Karaf > Issue Type: New Feature > Components: karaf-instance >Affects Versions: 3.0.3, 2.4.1, 4.0.0.M2 >Reporter: Krzysztof Sobkowiak >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > > Currently the command {{instance:create}} creates a new instance using the > resources included in {{org.apache.karaf.instance.core}} bundle. It would be > resonable to allow people to override the resources in custom distributions, > e.g. in the same way like branding bundles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3748) Installing activemq-blueprint feature sometimes fails with uses constraint violation
[ https://issues.apache.org/jira/browse/KARAF-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3748: Fix Version/s: (was: 4.0.7) 4.0.8 > Installing activemq-blueprint feature sometimes fails with uses constraint > violation > > > Key: KARAF-3748 > URL: https://issues.apache.org/jira/browse/KARAF-3748 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.0.M3 >Reporter: Achim Finke > Fix For: 4.1.0, 4.0.8 > > > From time to time you get the following exception when installing > activemq-blueprint feature. > {code} > org.osgi.service.resolver.ResolutionException: Uses constraint violation. > Unable to resolve resource org.apache.activemq.activemq-blueprint > [org.apache.activemq.activemq-blueprint/5.11.1] because it is exposed to > package 'org.apache.aries.blueprint' from resources > org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] and > org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] via > two dependency chains. > Chain 1: > org.apache.activemq.activemq-blueprint > [org.apache.activemq.activemq-blueprint/5.11.1] > import: > (&(osgi.wiring.package=org.apache.aries.blueprint)(version>=1.0.0)(!(version>=2.0.0))) > | > export: osgi.wiring.package: org.apache.aries.blueprint > org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] > Chain 2: > org.apache.activemq.activemq-blueprint > [org.apache.activemq.activemq-blueprint/5.11.1] > import: > (&(osgi.wiring.package=org.apache.xbean.blueprint.context.impl)(version>=3.13.0)(!(version>=4.0.0))) > | > export: osgi.wiring.package=org.apache.xbean.blueprint.context.impl; > uses:=org.apache.aries.blueprint > org.apache.xbean.blueprint [org.apache.xbean.blueprint/3.18.0] > import: > (&(osgi.wiring.package=org.apache.aries.blueprint)(version>=1.0.0)(!(version>=2.0.0))) > | > export: osgi.wiring.package: org.apache.aries.blueprint > org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] > at > org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1410)[org.apache.felix.framework-5.0.0.jar:] > at > org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:] > at > org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1502)[org.apache.felix.framework-5.0.0.jar:] > at > org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:] > at > org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1502)[org.apache.felix.framework-5.0.0.jar:] > at > org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:] > at > org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:289)[org.apache.felix.framework-5.0.0.jar:] > at > org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:185)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT] > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:261)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1061)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:960)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT] > at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_31] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_31] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_31] > at java.lang.Thread.run(Thread.java:745)[:1.8.0_31] > {code} > The behaviour is not predictable. Installation worked x times, afterwards > installation failed y times so you may need some trys to reproduce. > To reproduce execute: > {code} > feature:repo-add activemq 5.11.1 > feature:install activemq-blueprint > {code} > if you don't get the exception stop the container, delete data folder and try > again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3770) Add support for installing libraries from the features service
[ https://issues.apache.org/jira/browse/KARAF-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3770: Fix Version/s: (was: 4.0.7) 4.0.8 > Add support for installing libraries from the features service > -- > > Key: KARAF-3770 > URL: https://issues.apache.org/jira/browse/KARAF-3770 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.0.0.M3 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0, 4.0.8 > > > Libraries are currently only supported by the assembly builder. > CXF in particular requires quite a few libraries to work properly (those are > added in the apache-karaf distribution, but not in the minimal one). > Those libraries should be referenced in the CXF features instead, and the > features service should support installing the libraries and restarting the > framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3400) Enabling Java System Security and OSGi security leaves Karaf in unusable state
[ https://issues.apache.org/jira/browse/KARAF-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3400: Fix Version/s: (was: 4.0.7) 4.0.8 > Enabling Java System Security and OSGi security leaves Karaf in unusable state > -- > > Key: KARAF-3400 > URL: https://issues.apache.org/jira/browse/KARAF-3400 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.2, 4.0.0.M1 >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > It seems to boil down to the new functionalities of OSGi, like Bundle Adapt > fails with the default security configuration > {code} > java.security.AccessControlException: access denied > ("org.osgi.framework.AdaptPermission" > "org.osgi.framework.wiring.BundleRevision" "adapt") > at > java.security.AccessControlContext.checkPermission(AccessControlContext.java:372) > at > org.eclipse.osgi.internal.permadmin.EquinoxSecurityManager.internalCheckPermission(EquinoxSecurityManager.java:117) > at > org.eclipse.osgi.internal.permadmin.EquinoxSecurityManager$CheckPermissionAction.run(EquinoxSecurityManager.java:60) > at java.security.AccessController.doPrivileged(Native Method) > {code} > Just switch framework to equinox and enable the security params in > etc/system.properties > {code} > # > # By default, only Karaf shell commands are secured, but additional services > can be > # > # To enable OSGi security, uncomment the properties below, > # install the framework-security feature and restart. > # > java.security.policy=${karaf.etc}/all.policy > org.osgi.framework.security=osgi > org.osgi.framework.trust.repositories=${karaf.etc}/trustStore.ks > {code} > This also happens with Felix but needs the additional Felix.Security bundle > to be installed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4707) Add pax-url-classpath feature
[ https://issues.apache.org/jira/browse/KARAF-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4707: Fix Version/s: (was: 4.0.7) 4.0.8 > Add pax-url-classpath feature > - > > Key: KARAF-4707 > URL: https://issues.apache.org/jira/browse/KARAF-4707 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Alex Soto >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > To make it easier to use class path URLs. Something like. > {code:xml} > > mvn:org.ops4j.base/ops4j-base-util-property/1.5.0 > mvn:org.ops4j.base/ops4j-base-lang/1.5.0 > mvn:org.ops4j.pax.swissbox/pax-swissbox-property/1.8.2 > mvn:org.ops4j.pax.url/pax-url-commons/2.4.7 > mvn:org.ops4j.pax.url/pax-url-classpath/2.4.7 > > {code} > Also, it would be nice to have documentation about how to use it for > deploying config files in features.xml: > {code:xml} > > classpath:my.config.cfg > > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4283) List command reporting incorrect bundle state after service recovery
[ https://issues.apache.org/jira/browse/KARAF-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4283: Fix Version/s: (was: 4.0.7) 4.0.8 > List command reporting incorrect bundle state after service recovery > > > Key: KARAF-4283 > URL: https://issues.apache.org/jira/browse/KARAF-4283 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 2.4.3, 3.0.5, 4.0.4 > Environment: Oracle Java 1.7.0_79 > Camel 2.16.1 >Reporter: Quinn Stevenson >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.9, 4.0.8 > > > When an OSGi service used by a Camel route disappears, the list command > report bundle containing the Camel route is in the "Waiting" state, which is > expected. > However, when the required OSGi service is restored, the list command > continues to report the bundle containing the Camel route is in the "Waiting" > state, even though the Camel route recovers and is processing exchanges. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2511) Review and update documentation
[ https://issues.apache.org/jira/browse/KARAF-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2511: Fix Version/s: (was: 4.0.7) 4.0.8 > Review and update documentation > --- > > Key: KARAF-2511 > URL: https://issues.apache.org/jira/browse/KARAF-2511 > Project: Karaf > Issue Type: Task > Components: karaf-documentation >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.9, 4.0.8 > > > The documentation (manual) should be reviewed: > - The subshell part should be described (usage and configuration). > - The "code samples"/screenshots have to be updated with Karaf 3.0.0 use cases > - a global polishing, double read -- This message was sent by Atlassian JIRA (v6.3.4#6332)