[jira] [Updated] (KARAF-4162) Wrap deployer does not add default versions to exported packages

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
> 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] [Commented] (KARAF-4162) Wrap deployer does not add default versions to exported packages

[JIRA]

[ 
https://issues.apache.org/jira/browse/KARAF-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843935#comment-15843935
 ] 

Jean-Baptiste Onofré commented on KARAF-4162:
-

It's actually more a Pax URL Wrap issue than Karaf directly.

> 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.0.9, 4.1.1
>
> 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] [Assigned] (KARAF-4237) can't install transaction feature and activemq-camel feature: Missing dependency javax.transaction.TransactionManager

[Christian Schneider (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider reassigned KARAF-4237:
--

Assignee: Christian Schneider

> 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
>Assignee: Christian Schneider
> Fix For: 4.1.0, 4.0.9
>
>
> 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-4255) karaf-maven-plugin does include unused feature conditional dependencies in assembly

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-4261) Bundle start-level seems to be ignored at Karaf restart

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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, karaf-kar
>Affects Versions: 4.0.3
>Reporter: Ralf Steppacher
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.9, 4.1.1
>
>
> 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] [Assigned] (KARAF-4261) Bundle start-level seems to be ignored at Karaf restart

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-4261:
---

Assignee: Jean-Baptiste Onofré

> 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, karaf-kar
>Affects Versions: 4.0.3
>Reporter: Ralf Steppacher
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.9, 4.1.1
>
>
> 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-4261) Bundle start-level seems to be ignored at Karaf restart

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4261:

Component/s: karaf-kar

> 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, karaf-kar
>Affects Versions: 4.0.3
>Reporter: Ralf Steppacher
> Fix For: 4.0.9, 4.1.1
>
>
> 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] [Resolved] (KARAF-4283) List command reporting incorrect bundle state after service recovery

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4283.
-
   Resolution: Cannot Reproduce
Fix Version/s: (was: 4.0.9)
   (was: 3.0.9)
   (was: 4.1.0)

I'm not able to reproduce this issue on Karaf 4.x. Can you try on your side 
please (and reopen the Jira) ?

> 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é
>
> 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-4274) feature bundles not found even though they are in required version range

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-4314) karaf-maven-plugin issue when parsing feature xmls with entries that contain a newline and/or whitespaces

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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 
> 

[jira] [Updated] (KARAF-4496) UserPrincipal lookup in the JAAS' BackingEngine

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4496:

Fix Version/s: (was: 4.1.0)
   4.2.0

> UserPrincipal lookup in the JAAS' BackingEngine
> ---
>
> Key: KARAF-4496
> URL: https://issues.apache.org/jira/browse/KARAF-4496
> Project: Karaf
>  Issue Type: Improvement
>Reporter: Yurii Rashkovskii
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>  Labels: jaas
> Fix For: 4.2.0
>
>
> I have a suggestion for improving org.apache.karaf.jaas.modules.BackingEngine
> Currently, the only way to lookup an individual user (as far as I can tell) 
> is to iterate through the result of BackingEngine#listUsers() and find the 
> required user. This is fine if the number of users is reasonably low. 
> However, when JAAS infrastructure is used for public systems (say, a SaaS), 
> it quickly becomes a bottleneck.
> I suggest adding something like `public UserPrincipal lookupUser(String 
> name)` to avoid this problem (also, it should return `null` if no such user 
> found , or throw an exception)
> I am happy to contribute a PR promptly if this change will be approved.
> Thoughts?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4552) Karaf maven plugin creates wrong archived folder name when building custom distribution

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4552.
-
   Resolution: Not A Problem
Fix Version/s: (was: 4.0.9)
   (was: 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
>Assignee: Jean-Baptiste Onofré
>
> 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] [Commented] (KARAF-4552) Karaf maven plugin creates wrong archived folder name when building custom distribution

[JIRA]

[ 
https://issues.apache.org/jira/browse/KARAF-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843921#comment-15843921
 ] 

Jean-Baptiste Onofré commented on KARAF-4552:
-

{{targetFile}} just defines the name of the resulting archive ({{tar.gz}} or 
{{zip}}).

If you want to change the name of the directory inside the archive, you have to 
use {{pathPrefix}} configuration:

{code}

  aaa
  aaa

{code}

Then, you will have a {{aaa.zip}} and {{aaa.tar.gz}} file containing {{aaa}} 
directory with the distribution.

> 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é
>
> 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] [Resolved] (KARAF-4778) Add data delete support in reboot

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4778.
-
   Resolution: Not A Problem
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

It's already available via {{-c}} option on the {{system:shutdown}} command.

> Add data delete support in reboot
> -
>
> Key: KARAF-4778
> URL: https://issues.apache.org/jira/browse/KARAF-4778
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-core, karaf-shell
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>
> When using shutdown, it's possible to support data delete. However, this 
> functionality is not available for the reboot command.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4212) Null Dereference

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4212.
-
   Resolution: Won't Fix
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

The load test command uses here a latch. As it runs in OSGi, the 
bundle/framework can't be null.

> 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
>
> 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] [Resolved] (KARAF-4209) Weak XML Schema: Unbounded Occurrences

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4209.
-
   Resolution: Won't Fix
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

The number of features is unlimited that's why the maxOccurs is unbounded in 
the XSD.

> 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
>
> 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] [Resolved] (KARAF-4206) Session Fixation

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4206.
-
   Resolution: Won't Fix
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

That's the goal of the su command: execute an action with a different user. 

> 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
>
> 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] [Resolved] (KARAF-4204) Weak SecurityManager Check: Overridable Method

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4204.
-
   Resolution: Won't Fix
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

The Exception Karaf wrapper allows us to deal with stack trace. Not a big deal 
to have override-able method as this class is never extended.

> 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
>
> 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] [Resolved] (KARAF-4205) Privacy Violation

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4205.
-
   Resolution: Won't Fix
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

GogoParser is in the shell console. No problem here.

> 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
>
> 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] [Resolved] (KARAF-4200) Privacy Violation: Heap Inspection

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4200.
-
   Resolution: Not A Problem
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

The login module actually stores the password for the backend. We can imagine a 
workaround but it requires some deeper refactoring.

> 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
>
> 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] [Commented] (KARAF-3779) Be able to define the copied location of the kar files

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843858#comment-15843858
 ] 

ASF subversion and git services commented on KARAF-3779:


Commit dc4eb9b39f8a04a8b293e0a551bdea9862346c2a in karaf's branch 
refs/heads/karaf-4.0.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=dc4eb9b ]

[KARAF-3779] Be able to define the location of the kar storage


> 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é
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.9
>
>
> 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] [Resolved] (KARAF-3779) Be able to define the copied location of the kar files

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-3779.
-
Resolution: Fixed

> 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é
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.9
>
>
> 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] [Commented] (KARAF-3779) Be able to define the copied location of the kar files

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843850#comment-15843850
 ] 

ASF subversion and git services commented on KARAF-3779:


Commit 5c3c4ade61205a1fabfcf9d1ed72b768368c2786 in karaf's branch 
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=5c3c4ad ]

[KARAF-3779] Use File.separator in the default kar storage location


> 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é
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.9
>
>
> 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] [Resolved] (KARAF-4901) Make warning for "Unable to create a system terminal" less verbose

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz resolved KARAF-4901.
-
   Resolution: Done
Fix Version/s: 4.1.0

> Make warning for "Unable to create a system terminal" less verbose
> --
>
> Key: KARAF-4901
> URL: https://issues.apache.org/jira/browse/KARAF-4901
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.1.0
> Environment: Mac, Pax Exam
>Reporter: Oliver Lietz
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0
>
>
> {noformat}
> 2016-12-20T11:23:11,705 | WARN  | pool-3-thread-1  |  
> | 165 - org.jline - 3.1.1 | Creating a dumb terminal
> java.lang.IllegalStateException: Unable to create a system terminal
>   at org.jline.terminal.TerminalBuilder.doBuild(TerminalBuilder.java:177) 
> ~[?:?]
>   at org.jline.terminal.TerminalBuilder.build(TerminalBuilder.java:149) 
> ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:63)
>  ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:114) 
> ~[?:?]
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>  ~[?:?]
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226) 
> ~[?:?]
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144) ~[?:?]
>   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) 
> ~[?:?]
>   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1281)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:890) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>  ~[?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   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) [?:?]
>   Suppressed: com.sun.jna.LastErrorException: [25] Inappropriate ioctl 
> for device
>   at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
>   at com.sun.jna.Function.invoke(Function.java:374) ~[?:?]
>   at com.sun.jna.Function.invoke(Function.java:323) ~[?:?]
>   at com.sun.jna.Library$Handler.invoke(Library.java:236) ~[?:?]
>   at com.sun.proxy.$Proxy48.ttyname_r(Unknown Source) ~[?:?]
>   at 
> org.jline.terminal.impl.jna.osx.OsXNativePty.current(OsXNativePty.java:34) 
> ~[?:?]
>   at 
> org.jline.terminal.impl.jna.JnaNativePty.current(JnaNativePty.java:38) ~[?:?]
>   at 
> org.jline.terminal.TerminalBuilder.doBuild(TerminalBuilder.java:210) ~[?:?]
>   at 
> org.jline.terminal.TerminalBuilder.build(TerminalBuilder.java:149) ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:63)
>  ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:114) 
> ~[?:?]
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>  ~[?:?]
>   at 
> org.apache.felix.framework.Felix.activateBundle(Felix.java:2226) ~[?:?]
>   at 
> org.apache.felix.framework.Felix.startBundle(Felix.java:2144) ~[?:?]
>   at 
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?]
>   at 
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1281)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:890) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>  ~[?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [?:?]
>   at 
> 

[jira] [Commented] (KARAF-4901) Make warning for "Unable to create a system terminal" less verbose

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843122#comment-15843122
 ] 

Oliver Lietz commented on KARAF-4901:
-

[~jbonofre], it's less verbose with JLine 3.1.2:

{noformat}
[...]
2017-01-27T17:54:09,479 | WARN  | pool-3-thread-1  |
  | 123 - org.jline - 3.1.2 | Unable to create a system terminal, creating 
a dumb terminal (enable debug logging for more information)
[...]
{noformat}

> Make warning for "Unable to create a system terminal" less verbose
> --
>
> Key: KARAF-4901
> URL: https://issues.apache.org/jira/browse/KARAF-4901
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.1.0
> Environment: Mac, Pax Exam
>Reporter: Oliver Lietz
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> {noformat}
> 2016-12-20T11:23:11,705 | WARN  | pool-3-thread-1  |  
> | 165 - org.jline - 3.1.1 | Creating a dumb terminal
> java.lang.IllegalStateException: Unable to create a system terminal
>   at org.jline.terminal.TerminalBuilder.doBuild(TerminalBuilder.java:177) 
> ~[?:?]
>   at org.jline.terminal.TerminalBuilder.build(TerminalBuilder.java:149) 
> ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:63)
>  ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:114) 
> ~[?:?]
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>  ~[?:?]
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226) 
> ~[?:?]
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144) ~[?:?]
>   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) 
> ~[?:?]
>   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1281)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:890) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>  ~[?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   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) [?:?]
>   Suppressed: com.sun.jna.LastErrorException: [25] Inappropriate ioctl 
> for device
>   at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
>   at com.sun.jna.Function.invoke(Function.java:374) ~[?:?]
>   at com.sun.jna.Function.invoke(Function.java:323) ~[?:?]
>   at com.sun.jna.Library$Handler.invoke(Library.java:236) ~[?:?]
>   at com.sun.proxy.$Proxy48.ttyname_r(Unknown Source) ~[?:?]
>   at 
> org.jline.terminal.impl.jna.osx.OsXNativePty.current(OsXNativePty.java:34) 
> ~[?:?]
>   at 
> org.jline.terminal.impl.jna.JnaNativePty.current(JnaNativePty.java:38) ~[?:?]
>   at 
> org.jline.terminal.TerminalBuilder.doBuild(TerminalBuilder.java:210) ~[?:?]
>   at 
> org.jline.terminal.TerminalBuilder.build(TerminalBuilder.java:149) ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:63)
>  ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:114) 
> ~[?:?]
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>  ~[?:?]
>   at 
> org.apache.felix.framework.Felix.activateBundle(Felix.java:2226) ~[?:?]
>   at 
> org.apache.felix.framework.Felix.startBundle(Felix.java:2144) ~[?:?]
>   at 
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?]
>   at 
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1281)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:890) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>  ~[?:?]
>   at 
> 

[jira] [Reopened] (KARAF-4901) Make warning for "Unable to create a system terminal" less verbose

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz reopened KARAF-4901:
-

> Make warning for "Unable to create a system terminal" less verbose
> --
>
> Key: KARAF-4901
> URL: https://issues.apache.org/jira/browse/KARAF-4901
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.1.0
> Environment: Mac, Pax Exam
>Reporter: Oliver Lietz
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> {noformat}
> 2016-12-20T11:23:11,705 | WARN  | pool-3-thread-1  |  
> | 165 - org.jline - 3.1.1 | Creating a dumb terminal
> java.lang.IllegalStateException: Unable to create a system terminal
>   at org.jline.terminal.TerminalBuilder.doBuild(TerminalBuilder.java:177) 
> ~[?:?]
>   at org.jline.terminal.TerminalBuilder.build(TerminalBuilder.java:149) 
> ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:63)
>  ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:114) 
> ~[?:?]
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>  ~[?:?]
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226) 
> ~[?:?]
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144) ~[?:?]
>   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) 
> ~[?:?]
>   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1281)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:890) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>  ~[?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   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) [?:?]
>   Suppressed: com.sun.jna.LastErrorException: [25] Inappropriate ioctl 
> for device
>   at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
>   at com.sun.jna.Function.invoke(Function.java:374) ~[?:?]
>   at com.sun.jna.Function.invoke(Function.java:323) ~[?:?]
>   at com.sun.jna.Library$Handler.invoke(Library.java:236) ~[?:?]
>   at com.sun.proxy.$Proxy48.ttyname_r(Unknown Source) ~[?:?]
>   at 
> org.jline.terminal.impl.jna.osx.OsXNativePty.current(OsXNativePty.java:34) 
> ~[?:?]
>   at 
> org.jline.terminal.impl.jna.JnaNativePty.current(JnaNativePty.java:38) ~[?:?]
>   at 
> org.jline.terminal.TerminalBuilder.doBuild(TerminalBuilder.java:210) ~[?:?]
>   at 
> org.jline.terminal.TerminalBuilder.build(TerminalBuilder.java:149) ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:63)
>  ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:114) 
> ~[?:?]
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>  ~[?:?]
>   at 
> org.apache.felix.framework.Felix.activateBundle(Felix.java:2226) ~[?:?]
>   at 
> org.apache.felix.framework.Felix.startBundle(Felix.java:2144) ~[?:?]
>   at 
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?]
>   at 
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1281)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:890) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>  ~[?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [?:?]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:?]
>   at 
> 

[jira] [Resolved] (KARAF-3878) Update and fix documentation

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-3878.
-
   Resolution: Duplicate
 Assignee: Jean-Baptiste Onofré
Fix Version/s: (was: 4.1.0)

> Update and fix documentation
> 
>
> Key: KARAF-3878
> URL: https://issues.apache.org/jira/browse/KARAF-3878
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-documentation
>Affects Versions: 4.0.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>
> The dev guide contains not up to date details. For instance:
> * the custom distribution refers to standard feature which doesn't exist 
> anymore
> Regarding the user guide:
> * the jdbc commands have changed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-3779) Be able to define the copied location of the kar files

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843096#comment-15843096
 ] 

ASF subversion and git services commented on KARAF-3779:


Commit 58da8340b0707bdba8d358a1e4a445727385d97d in karaf's branch 
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=58da834 ]

[KARAF-3779] Be able to define the location of the kar storage


> 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é
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.9
>
>
> 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] [Resolved] (KARAF-4290) karaf-maven-plugin uses inactive proxies from settings.xml

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4290.
-
   Resolution: Won't Fix
Fix Version/s: (was: 4.1.1)
   (was: 4.0.9)

Anyway, it's probably a Pax URL problem (mvn). I will take a look and create 
the Jira at Pax URL.

> 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
> 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-4260) Setting karaf.clean.all = true breaks service wrapper service script

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-4290) karaf-maven-plugin uses inactive proxies from settings.xml

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
> 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-4199) Privacy Violation: Heap Inspection

[JIRA]

 [ 
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: 4.1.1
   4.0.9

> 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.0.9, 4.1.1
>
>
> 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-4188) Add support for Systemd's watchdog

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4188:

Fix Version/s: (was: 4.1.0)
   4.1.1

> Add support for Systemd's watchdog
> --
>
> Key: KARAF-4188
> URL: https://issues.apache.org/jira/browse/KARAF-4188
> Project: Karaf
>  Issue Type: New Feature
>  Components: karaf-core
>Reporter: Luca Burgazzoli
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.0.6, 4.0.9, 4.1.1
>
>
> Systemd has a watchdog feature that could help detecting freeze jvm, 
> integrating it in karaf would be possible via jna/jnr



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-3995) installAllFeaturesByDefault is not documented

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-3995.
-
   Resolution: Not A Problem
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

> 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é
>
>  @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

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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: 3.0.9, 4.0.9, 4.1.1
>
>
> 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-4109) For backward compatibility, support the resolver attribute in features XML

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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] [Resolved] (KARAF-3989) Manual broken because images can't be loaded.

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-3989.
-
   Resolution: Not A Problem
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

It's now ok with the new asciidoc documentation backend.

> 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
> 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-3976) Broken compatibility with 3.x jdbc DataSources

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-3921) Installing an already installed feature again sometimes switches used bundles

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3921:

Fix Version/s: (was: 4.1.0)
   4.1.1
   4.0.9

> Installing an already installed feature again sometimes switches used bundles
> -
>
> Key: KARAF-3921
> URL: https://issues.apache.org/jira/browse/KARAF-3921
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.0
>Reporter: Christian Schneider
> Fix For: 4.0.9, 4.1.1
>
>
> First install my example from:
> https://github.com/cschneider/Karaf-Tutorial/tree/jpa-2.1.0/tasklist-blueprint-cdi
> according to the README.
> Then install the already install jaxrs service bundle again several times. As 
> you see from the console log below the resolved tends to use a different 
> transaction manager every time.
> -
> karaf@root()> feature:install -v example-tasklist-cdi-service
> Adding features: example-tasklist-cdi-service/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
> Changes to perform:
>   Region: root
> Bundles to uninstall:
>   org.apache.aries.transaction.manager/1.0.1
> Bundles to install:
>   
> mvn:org.apache.aries.transaction/org.apache.aries.transaction.blueprint/1.1.1
> Stopping bundles:
>   org.apache.aries.transaction.manager/1.0.1
> Uninstalling bundles:
>   org.apache.aries.transaction.manager/1.0.1
> Installing bundles:
>   
> mvn:org.apache.aries.transaction/org.apache.aries.transaction.blueprint/1.1.1
> Stopping bundles:
>   org.apache.aries.transaction.blueprint/1.1.1
> Refreshing bundles:
> org.apache.aries.transaction.blueprint/1.1.1 (Should be wired to: 
> org.apache.aries.transaction.blueprint/1.1.1 (through 
> [org.apache.aries.transaction.blueprint/1.1.1] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.apache.aries.transaction.exception)(version>=1.0.0)(!(version>=2.0.0)))"))
> org.apache.aries.transaction.manager/1.0.1 (Bundle will be uninstalled)
> Starting bundles:
>   org.apache.aries.transaction.blueprint/1.1.1
> Done.
> karaf@root()> feature:install -v example-tasklist-cdi-service
> Adding features: example-tasklist-cdi-service/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
> Changes to perform:
>   Region: root
> Bundles to update:
>   org.apache.aries.transaction.manager/1.0.0 with 
> mvn:org.apache.aries.transaction/org.apache.aries.transaction.manager/1.0.1
> Stopping bundles:
>   org.apache.aries.transaction.manager/1.0.0
> Updating bundles:
>   mvn:org.apache.aries.transaction/org.apache.aries.transaction.manager/1.0.1
> Stopping bundles:
>   org.apache.aries.transaction.manager/1.0.1
> Refreshing bundles:
> org.apache.aries.transaction.manager/1.0.1 (Bundle will be updated)
> Starting bundles:
>   org.apache.aries.transaction.manager/1.0.1
> Done.
> karaf@root()> feature:install -v example-tasklist-cdi-service
> Adding features: example-tasklist-cdi-service/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
> Changes to perform:
>   Region: root
> Bundles to update:
>   org.apache.aries.transaction.manager/1.0.1 with 
> mvn:org.apache.aries.transaction/org.apache.aries.transaction.manager/1.0.0
> Bundles to install:
>   
> mvn:org.apache.aries.transaction/org.apache.aries.transaction.blueprint/1.1.1
> Stopping bundles:
>   org.apache.aries.transaction.manager/1.0.1
> Updating bundles:
>   mvn:org.apache.aries.transaction/org.apache.aries.transaction.manager/1.0.0
> Installing bundles:
>   
> mvn:org.apache.aries.transaction/org.apache.aries.transaction.blueprint/1.1.1
> Stopping bundles:
>   org.apache.aries.transaction.manager/1.0.0
> Refreshing bundles:
> org.apache.aries.transaction.manager/1.0.0 (Bundle will be updated)
> Starting bundles:
>   org.apache.aries.transaction.manager/1.0.0
> Done.
> karaf@root()> feature:install -v example-tasklist-cdi-service
> Adding features: example-tasklist-cdi-service/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
> Changes to perform:
>   Region: root
> Bundles to install:
>   
> mvn:org.apache.aries.transaction/org.apache.aries.transaction.blueprint/1.1.1
>   
> mvn:org.apache.aries.transaction/org.apache.aries.transaction.manager/1.0.1
> Installing bundles:
>   
> mvn:org.apache.aries.transaction/org.apache.aries.transaction.blueprint/1.1.1
>   mvn:org.apache.aries.transaction/org.apache.aries.transaction.manager/1.0.1
> Starting bundles:
>   org.apache.aries.transaction.manager/1.0.1
> Done.



--
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

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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: 3.0.9, 4.0.9, 4.1.1
>
>
> 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] [Resolved] (KARAF-3810) Feature verify goal fail on Windows (for standard features)

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-3810.
-
   Resolution: Cannot Reproduce
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

It's OK now (I don't know since when).

> 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é
>
> On Windows, the verify goal fails on some standard features.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4210) Unreleased Resource: Streams

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-3770) Add support for installing libraries from the features service

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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] [Resolved] (KARAF-4211) Portability Flaw: Locale Dependent Comparison

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4211.
-
   Resolution: Won't Fix
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

Not a problem as the feature name doesn't depend to the locale.

> 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
>
> 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] [Resolved] (KARAF-4213) Public cloneable() Method Without Final ('Object Hijack')

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4213.
-
   Resolution: Won't Fix
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

Not really a problem as we catch the {{CloneNotSupportedException}}.

> 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
>
> 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-4214) Deserialization of Untrusted Data

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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] [Resolved] (KARAF-4217) XML External Entity Injection

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4217.
-
   Resolution: Won't Fix
Fix Version/s: (was: 4.1.1)
   (was: 4.0.9)

Not really a problem as the XML parser is only for the Maven {{settings.xml}}.

> 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
>
> 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] [Resolved] (KARAF-4216) Poor Error Handling: Return Inside Finally

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4216.
-
   Resolution: Won't Fix
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

Not a problem as the {{IOException}} is catched only for logging and the 
backend engine can be null.

> 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
>
> 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-4216) Poor Error Handling: Return Inside Finally

[JIRA]

 [ 
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.1.1)
   4.1.0

> 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.9
>
>
> 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] [Resolved] (KARAF-4215) Use of Dynamic Class Loading, Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4215.
-
   Resolution: Won't Fix
Fix Version/s: (was: 4.0.9)
   (was: 4.1.0)

It's not really a problem there and it's the only way for the JDBC lock to load 
the JDBC driver.

> 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
>
> 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-4216) Poor Error Handling: Return Inside Finally

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-4235) Windows start script requires data dir

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-4217) XML External Entity Injection

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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] [Resolved] (KARAF-4959) Log messages duplicated in log:tail

[Christian Schneider (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider resolved KARAF-4959.

Resolution: Fixed

> Log messages duplicated in log:tail
> ---
>
> Key: KARAF-4959
> URL: https://issues.apache.org/jira/browse/KARAF-4959
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.1.0
>
>
> When starting a fresh karaf 4.1.0-SNAPSHOT log:tail shows multiple identical 
> log messages:
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | 

[jira] [Resolved] (KARAF-4960) Karaf exits when typing "la |"

[Christian Schneider (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider resolved KARAF-4960.

Resolution: Fixed

> Karaf exits when typing "la |"
> --
>
> Key: KARAF-4960
> URL: https://issues.apache.org/jira/browse/KARAF-4960
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.1.0
>
>
> When typing any command and just "|" at the end karaf completely exits.
> There is the stacktrace below in the log.
> I found that this is because of a unprotected access to the first token of 
> the parsed command.
> 2017-01-27T14:52:22,844 | ERROR | Karaf local console user karaf | ShellUtil  
>   | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | 
> Exception caught while executing command
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
>   at java.util.ArrayList.rangeCheck(ArrayList.java:653) [?:?]
>   at java.util.ArrayList.get(ArrayList.java:429) [?:?]
>   at 
> org.apache.karaf.shell.impl.console.parsing.KarafParser.doParse(KarafParser.java:78)
>  [43:org.apache.karaf.shell.core:4.1.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.parsing.KarafParser.parse(KarafParser.java:49)
>  [43:org.apache.karaf.shell.core:4.1.0.SNAPSHOT]
>   at 
> org.jline.reader.impl.LineReaderImpl.insertSecondaryPrompts(LineReaderImpl.java:3430)
>  [50:org.jline:3.1.2]
>   at 
> org.jline.reader.impl.LineReaderImpl.insertSecondaryPrompts(LineReaderImpl.java:3387)
>  [50:org.jline:3.1.2]
>   at 
> org.jline.reader.impl.LineReaderImpl.getDisplayedBufferWithPrompts(LineReaderImpl.java:3268)
>  [50:org.jline:3.1.2]
>   at 
> org.jline.reader.impl.LineReaderImpl.redisplay(LineReaderImpl.java:3203) 
> [50:org.jline:3.1.2]
>   at 
> org.jline.reader.impl.LineReaderImpl.cleanup(LineReaderImpl.java:2180) 
> [50:org.jline:3.1.2]
>   at 
> org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:570) 
> [50:org.jline:3.1.2]
>   at 
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
>  [43:org.apache.karaf.shell.core:4.1.0.SNAPSHOT]
>   at java.lang.Thread.run(Thread.java:745) [?:?]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4960) Karaf exits when typing "la |"

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842897#comment-15842897
 ] 

ASF subversion and git services commented on KARAF-4960:


Commit 90ef2e8196fa36bc4ddb93e342624a3845eb0bca in karaf's branch 
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=90ef2e8 ]

[KARAF-4960] Checking number of tokens to avoid karaf crash


> Karaf exits when typing "la |"
> --
>
> Key: KARAF-4960
> URL: https://issues.apache.org/jira/browse/KARAF-4960
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.1.0
>
>
> When typing any command and just "|" at the end karaf completely exits.
> There is the stacktrace below in the log.
> I found that this is because of a unprotected access to the first token of 
> the parsed command.
> 2017-01-27T14:52:22,844 | ERROR | Karaf local console user karaf | ShellUtil  
>   | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | 
> Exception caught while executing command
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
>   at java.util.ArrayList.rangeCheck(ArrayList.java:653) [?:?]
>   at java.util.ArrayList.get(ArrayList.java:429) [?:?]
>   at 
> org.apache.karaf.shell.impl.console.parsing.KarafParser.doParse(KarafParser.java:78)
>  [43:org.apache.karaf.shell.core:4.1.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.parsing.KarafParser.parse(KarafParser.java:49)
>  [43:org.apache.karaf.shell.core:4.1.0.SNAPSHOT]
>   at 
> org.jline.reader.impl.LineReaderImpl.insertSecondaryPrompts(LineReaderImpl.java:3430)
>  [50:org.jline:3.1.2]
>   at 
> org.jline.reader.impl.LineReaderImpl.insertSecondaryPrompts(LineReaderImpl.java:3387)
>  [50:org.jline:3.1.2]
>   at 
> org.jline.reader.impl.LineReaderImpl.getDisplayedBufferWithPrompts(LineReaderImpl.java:3268)
>  [50:org.jline:3.1.2]
>   at 
> org.jline.reader.impl.LineReaderImpl.redisplay(LineReaderImpl.java:3203) 
> [50:org.jline:3.1.2]
>   at 
> org.jline.reader.impl.LineReaderImpl.cleanup(LineReaderImpl.java:2180) 
> [50:org.jline:3.1.2]
>   at 
> org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:570) 
> [50:org.jline:3.1.2]
>   at 
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
>  [43:org.apache.karaf.shell.core:4.1.0.SNAPSHOT]
>   at java.lang.Thread.run(Thread.java:745) [?:?]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4960) Karaf exits when typing "la |"

[Christian Schneider (JIRA)]

Christian Schneider created KARAF-4960:
--

 Summary: Karaf exits when typing "la |"
 Key: KARAF-4960
 URL: https://issues.apache.org/jira/browse/KARAF-4960
 Project: Karaf
  Issue Type: Bug
  Components: karaf-shell
Affects Versions: 4.1.0
Reporter: Christian Schneider
Assignee: Christian Schneider
 Fix For: 4.1.0


When typing any command and just "|" at the end karaf completely exits.
There is the stacktrace below in the log.

I found that this is because of a unprotected access to the first token of the 
parsed command.

2017-01-27T14:52:22,844 | ERROR | Karaf local console user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | 
Exception caught while executing command
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:653) [?:?]
at java.util.ArrayList.get(ArrayList.java:429) [?:?]
at 
org.apache.karaf.shell.impl.console.parsing.KarafParser.doParse(KarafParser.java:78)
 [43:org.apache.karaf.shell.core:4.1.0.SNAPSHOT]
at 
org.apache.karaf.shell.impl.console.parsing.KarafParser.parse(KarafParser.java:49)
 [43:org.apache.karaf.shell.core:4.1.0.SNAPSHOT]
at 
org.jline.reader.impl.LineReaderImpl.insertSecondaryPrompts(LineReaderImpl.java:3430)
 [50:org.jline:3.1.2]
at 
org.jline.reader.impl.LineReaderImpl.insertSecondaryPrompts(LineReaderImpl.java:3387)
 [50:org.jline:3.1.2]
at 
org.jline.reader.impl.LineReaderImpl.getDisplayedBufferWithPrompts(LineReaderImpl.java:3268)
 [50:org.jline:3.1.2]
at 
org.jline.reader.impl.LineReaderImpl.redisplay(LineReaderImpl.java:3203) 
[50:org.jline:3.1.2]
at 
org.jline.reader.impl.LineReaderImpl.cleanup(LineReaderImpl.java:2180) 
[50:org.jline:3.1.2]
at 
org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:570) 
[50:org.jline:3.1.2]
at 
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
 [43:org.apache.karaf.shell.core:4.1.0.SNAPSHOT]
at java.lang.Thread.run(Thread.java:745) [?:?]




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4959) Log messages duplicated in log:tail

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842628#comment-15842628
 ] 

ASF subversion and git services commented on KARAF-4959:


Commit 33c94fd154a1ae094e406d2658a8517a496b6923 in karaf's branch 
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=33c94fd ]

[KARAF-4959] Small refactorings


> Log messages duplicated in log:tail
> ---
>
> Key: KARAF-4959
> URL: https://issues.apache.org/jira/browse/KARAF-4959
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.1.0
>
>
> When starting a fresh karaf 4.1.0-SNAPSHOT log:tail shows multiple identical 
> log messages:
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle 

[jira] [Commented] (KARAF-4959) Log messages duplicated in log:tail

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842627#comment-15842627
 ] 

ASF subversion and git services commented on KARAF-4959:


Commit 1f1973c60ed9c13677b7057b2a1bc82c45045916 in karaf's branch 
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=1f1973c ]

[KARAF-4959] Avoid logging message duplicates


> Log messages duplicated in log:tail
> ---
>
> Key: KARAF-4959
> URL: https://issues.apache.org/jira/browse/KARAF-4959
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.1.0
>
>
> When starting a fresh karaf 4.1.0-SNAPSHOT log:tail shows multiple identical 
> log messages:
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle 

[jira] [Updated] (KARAF-4901) Make warning for "Unable to create a system terminal" less verbose

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4901:

Fix Version/s: (was: 4.1.0)

> Make warning for "Unable to create a system terminal" less verbose
> --
>
> Key: KARAF-4901
> URL: https://issues.apache.org/jira/browse/KARAF-4901
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.1.0
> Environment: Mac, Pax Exam
>Reporter: Oliver Lietz
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> {noformat}
> 2016-12-20T11:23:11,705 | WARN  | pool-3-thread-1  |  
> | 165 - org.jline - 3.1.1 | Creating a dumb terminal
> java.lang.IllegalStateException: Unable to create a system terminal
>   at org.jline.terminal.TerminalBuilder.doBuild(TerminalBuilder.java:177) 
> ~[?:?]
>   at org.jline.terminal.TerminalBuilder.build(TerminalBuilder.java:149) 
> ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:63)
>  ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:114) 
> ~[?:?]
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>  ~[?:?]
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226) 
> ~[?:?]
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144) ~[?:?]
>   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) 
> ~[?:?]
>   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1281)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:890) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>  ~[?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   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) [?:?]
>   Suppressed: com.sun.jna.LastErrorException: [25] Inappropriate ioctl 
> for device
>   at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
>   at com.sun.jna.Function.invoke(Function.java:374) ~[?:?]
>   at com.sun.jna.Function.invoke(Function.java:323) ~[?:?]
>   at com.sun.jna.Library$Handler.invoke(Library.java:236) ~[?:?]
>   at com.sun.proxy.$Proxy48.ttyname_r(Unknown Source) ~[?:?]
>   at 
> org.jline.terminal.impl.jna.osx.OsXNativePty.current(OsXNativePty.java:34) 
> ~[?:?]
>   at 
> org.jline.terminal.impl.jna.JnaNativePty.current(JnaNativePty.java:38) ~[?:?]
>   at 
> org.jline.terminal.TerminalBuilder.doBuild(TerminalBuilder.java:210) ~[?:?]
>   at 
> org.jline.terminal.TerminalBuilder.build(TerminalBuilder.java:149) ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:63)
>  ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:114) 
> ~[?:?]
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>  ~[?:?]
>   at 
> org.apache.felix.framework.Felix.activateBundle(Felix.java:2226) ~[?:?]
>   at 
> org.apache.felix.framework.Felix.startBundle(Felix.java:2144) ~[?:?]
>   at 
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?]
>   at 
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1281)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:890) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>  ~[?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [?:?]
>   at 
> 

[jira] [Resolved] (KARAF-4901) Make warning for "Unable to create a system terminal" less verbose

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4901.
-
Resolution: Not A Problem

Any way to reproduce the exception ?

> Make warning for "Unable to create a system terminal" less verbose
> --
>
> Key: KARAF-4901
> URL: https://issues.apache.org/jira/browse/KARAF-4901
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.1.0
> Environment: Mac, Pax Exam
>Reporter: Oliver Lietz
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> {noformat}
> 2016-12-20T11:23:11,705 | WARN  | pool-3-thread-1  |  
> | 165 - org.jline - 3.1.1 | Creating a dumb terminal
> java.lang.IllegalStateException: Unable to create a system terminal
>   at org.jline.terminal.TerminalBuilder.doBuild(TerminalBuilder.java:177) 
> ~[?:?]
>   at org.jline.terminal.TerminalBuilder.build(TerminalBuilder.java:149) 
> ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:63)
>  ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:114) 
> ~[?:?]
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>  ~[?:?]
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226) 
> ~[?:?]
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144) ~[?:?]
>   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) 
> ~[?:?]
>   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1281)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:890) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>  ~[?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   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) [?:?]
>   Suppressed: com.sun.jna.LastErrorException: [25] Inappropriate ioctl 
> for device
>   at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
>   at com.sun.jna.Function.invoke(Function.java:374) ~[?:?]
>   at com.sun.jna.Function.invoke(Function.java:323) ~[?:?]
>   at com.sun.jna.Library$Handler.invoke(Library.java:236) ~[?:?]
>   at com.sun.proxy.$Proxy48.ttyname_r(Unknown Source) ~[?:?]
>   at 
> org.jline.terminal.impl.jna.osx.OsXNativePty.current(OsXNativePty.java:34) 
> ~[?:?]
>   at 
> org.jline.terminal.impl.jna.JnaNativePty.current(JnaNativePty.java:38) ~[?:?]
>   at 
> org.jline.terminal.TerminalBuilder.doBuild(TerminalBuilder.java:210) ~[?:?]
>   at 
> org.jline.terminal.TerminalBuilder.build(TerminalBuilder.java:149) ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:63)
>  ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:114) 
> ~[?:?]
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>  ~[?:?]
>   at 
> org.apache.felix.framework.Felix.activateBundle(Felix.java:2226) ~[?:?]
>   at 
> org.apache.felix.framework.Felix.startBundle(Felix.java:2144) ~[?:?]
>   at 
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?]
>   at 
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1281)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:890) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>  ~[?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [?:?]
>   at 
> 

[jira] [Commented] (KARAF-4901) Make warning for "Unable to create a system terminal" less verbose

[JIRA]

[ 
https://issues.apache.org/jira/browse/KARAF-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842507#comment-15842507
 ] 

Jean-Baptiste Onofré commented on KARAF-4901:
-

I think it's more a jline issue than a Karaf issue.

> Make warning for "Unable to create a system terminal" less verbose
> --
>
> Key: KARAF-4901
> URL: https://issues.apache.org/jira/browse/KARAF-4901
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.1.0
> Environment: Mac, Pax Exam
>Reporter: Oliver Lietz
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> {noformat}
> 2016-12-20T11:23:11,705 | WARN  | pool-3-thread-1  |  
> | 165 - org.jline - 3.1.1 | Creating a dumb terminal
> java.lang.IllegalStateException: Unable to create a system terminal
>   at org.jline.terminal.TerminalBuilder.doBuild(TerminalBuilder.java:177) 
> ~[?:?]
>   at org.jline.terminal.TerminalBuilder.build(TerminalBuilder.java:149) 
> ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:63)
>  ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:114) 
> ~[?:?]
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>  ~[?:?]
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226) 
> ~[?:?]
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144) ~[?:?]
>   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) 
> ~[?:?]
>   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1281)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:890) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>  ~[?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   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) [?:?]
>   Suppressed: com.sun.jna.LastErrorException: [25] Inappropriate ioctl 
> for device
>   at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
>   at com.sun.jna.Function.invoke(Function.java:374) ~[?:?]
>   at com.sun.jna.Function.invoke(Function.java:323) ~[?:?]
>   at com.sun.jna.Library$Handler.invoke(Library.java:236) ~[?:?]
>   at com.sun.proxy.$Proxy48.ttyname_r(Unknown Source) ~[?:?]
>   at 
> org.jline.terminal.impl.jna.osx.OsXNativePty.current(OsXNativePty.java:34) 
> ~[?:?]
>   at 
> org.jline.terminal.impl.jna.JnaNativePty.current(JnaNativePty.java:38) ~[?:?]
>   at 
> org.jline.terminal.TerminalBuilder.doBuild(TerminalBuilder.java:210) ~[?:?]
>   at 
> org.jline.terminal.TerminalBuilder.build(TerminalBuilder.java:149) ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:63)
>  ~[?:?]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:114) 
> ~[?:?]
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>  ~[?:?]
>   at 
> org.apache.felix.framework.Felix.activateBundle(Felix.java:2226) ~[?:?]
>   at 
> org.apache.felix.framework.Felix.startBundle(Felix.java:2144) ~[?:?]
>   at 
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?]
>   at 
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1281)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:890) 
> ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>  ~[?:?]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>  ~[?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [?:?]
>   at 
> 

[jira] [Updated] (KARAF-4361) Allow dynamic config customization when embedding Karaf using the Main class

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
> 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-4360) FrameworkEvent ERROR in the karaf.log when install cxf-core feature

[JIRA]

 [ 
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.9)
   (was: 4.1.0)

> 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
>
> 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: 
> 

[jira] [Resolved] (KARAF-4360) FrameworkEvent ERROR in the karaf.log when install cxf-core feature

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4360.
-
Resolution: Not A Problem

AFAIK, it has been fixed in CXF.

> 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
>
> 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: 
> 

[jira] [Updated] (KARAF-4324) Shell commands and optional @Reference

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-4336) Add support for ordering of CLI scripts and commands in karaf-maven-plugin

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> {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-4174) NullPointerException when running obr:info on a bundle served by cave

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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: cave-4.0.1, 4.0.9, 4.1.1
>
>
> 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-4181) blacklist.properties is not a properties file

[JIRA]

 [ 
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.1.0)
   4.2.0

> 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.2.0
>
>
> 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-4124) feature config installer adds property to config

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-4419) Multiple inharitance levels with generics cause ClassCastException when JPA is enabled

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4419:

Assignee: Christian Schneider

> 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
> Environment: Win 7 x64, JDK 1.8.0_73, Karaf 4.0.4
>Reporter: Felix Wassmer
>Assignee: Christian Schneider
>
> 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-4380) Remove blueprint feature in standard distribution

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4380:

Fix Version/s: (was: 4.1.0)
   4.2.0

> Remove blueprint feature in standard distribution
> -
>
> Key: KARAF-4380
> URL: https://issues.apache.org/jira/browse/KARAF-4380
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0
>
>
> Applications should define the dependency to the blueprint feature if needed 
> (as for scr), and so, it makes sense to remove blueprint from standard and 
> minimal distributions. It's even better to let users have a choice between 
> aries-blueprint and gemini.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4124) feature config installer adds property to config

[Christian Schneider (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842466#comment-15842466
 ] 

Christian Schneider commented on KARAF-4124:


We can fix this is pax jdbc but indeed it is not a good idea to add attributes 
to configs. I know felix fileinstall does it too but it causes lots of problems.

In pax-jdbc the problem is that all configs are fed into 
DataSourceFactory.create calls. Most factories directly throw an exception if 
any unknown key is encountered. I think this is even defined in the spec. As 
these factories are out of our control we can not easily fix this.

> 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.9
>
>
> 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-4417) Display a summary for the verify goal

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4417:

Fix Version/s: (was: 4.1.0)
   4.1.1

> Display a summary for the verify goal
> -
>
> Key: KARAF-4417
> URL: https://issues.apache.org/jira/browse/KARAF-4417
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-tooling
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.1
>
>
> davsclaus: would be cool if the karaf plugin could write a summary at the end
> davsclaus: how may pass and failed
> davsclaus: and maybe list the names of the ones that failed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4418) Ability to exclude a set of features from the verify goal

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4418:

Fix Version/s: (was: 4.1.0)
   4.1.1

> Ability to exclude a set of features from the verify goal
> -
>
> Key: KARAF-4418
> URL: https://issues.apache.org/jira/browse/KARAF-4418
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-tooling
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.1
>
>
> Currently, the verify goal has a set of features to include which are parsed 
> as regex (using a glob syntax), however, this is a bit tricky to exclude some 
> features.
> We need an additional configuration field with a set of excludes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4158) Unexpected behavior on first startup

[Christian Schneider (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider updated KARAF-4158:
---
Fix Version/s: (was: 4.1.0)
   4.2.0

> Unexpected behavior on first startup
> 
>
> Key: KARAF-4158
> URL: https://issues.apache.org/jira/browse/KARAF-4158
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 4.0.3
> Environment: RHEL 6.2 x32, Java 1.8.0_72-ea-b05
>Reporter: Jean-Philippe CLEMENT
>Assignee: Christian Schneider
> Fix For: 4.2.0
>
>
> This problem only occurs on the very first startup of a custom assembly. This 
> means unpacking the assembly .tar.gz then run karaf. This issue is not 100% 
> reproducible. Several untar/run might be necessary to reproduce the issue.
> The problem comes with Blueprint property-placeholders. User bundles might be 
> started and not get .cfg replaced properties but the "$(PARAM_NAME)" itself 
> (String property).
> I suspect user bundles to be started before the .cfg files are populated in 
> the /etc directory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4927) NamespaceHandlers should return null for unknown namespaces

[Christian Schneider (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider resolved KARAF-4927.

Resolution: Fixed

> NamespaceHandlers should return null for unknown namespaces
> ---
>
> Key: KARAF-4927
> URL: https://issues.apache.org/jira/browse/KARAF-4927
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.0.8
>Reporter: Daniel Kulp
>Assignee: Christian Schneider
> Fix For: 4.1.0, 4.0.9
>
>
> The namespacehandler for shell does a:
> return getClass().getResource("karaf-shell-1.1.0.xsd");
> for unknown namespaces.   It should return null.  Right now, users will get 
> an error at startup of:
> "NamespaceHandler org.apache.karaf.shell.console.commands.NamespaceHandler is 
> behaving badly and should be fixed"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4927) NamespaceHandlers should return null for unknown namespaces

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842461#comment-15842461
 ] 

ASF subversion and git services commented on KARAF-4927:


Commit 86108d09178dad371202ffe0a2084a014605f588 in karaf's branch 
refs/heads/karaf-4.0.x from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=86108d0 ]

[KARAF-4927] return null for unknown namespaces


> NamespaceHandlers should return null for unknown namespaces
> ---
>
> Key: KARAF-4927
> URL: https://issues.apache.org/jira/browse/KARAF-4927
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.0.8
>Reporter: Daniel Kulp
>Assignee: Christian Schneider
> Fix For: 4.1.0, 4.0.9
>
>
> The namespacehandler for shell does a:
> return getClass().getResource("karaf-shell-1.1.0.xsd");
> for unknown namespaces.   It should return null.  Right now, users will get 
> an error at startup of:
> "NamespaceHandler org.apache.karaf.shell.console.commands.NamespaceHandler is 
> behaving badly and should be fixed"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4927) NamespaceHandlers should return null for unknown namespaces

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842460#comment-15842460
 ] 

ASF subversion and git services commented on KARAF-4927:


Commit e39183715a156910b03b725a56b3fbb287c0e2e7 in karaf's branch 
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=e391837 ]

[KARAF-4927] return null for unknown namespaces


> NamespaceHandlers should return null for unknown namespaces
> ---
>
> Key: KARAF-4927
> URL: https://issues.apache.org/jira/browse/KARAF-4927
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.0.8
>Reporter: Daniel Kulp
>Assignee: Christian Schneider
> Fix For: 4.1.0, 4.0.9
>
>
> The namespacehandler for shell does a:
> return getClass().getResource("karaf-shell-1.1.0.xsd");
> for unknown namespaces.   It should return null.  Right now, users will get 
> an error at startup of:
> "NamespaceHandler org.apache.karaf.shell.console.commands.NamespaceHandler is 
> behaving badly and should be fixed"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4419) Multiple inharitance levels with generics cause ClassCastException when JPA is enabled

[JIRA]

[ 
https://issues.apache.org/jira/browse/KARAF-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842455#comment-15842455
 ] 

Jean-Baptiste Onofré commented on KARAF-4419:
-

I think this Jira is more related to Aries JPA. [~ch...@die-schneider.net] what 
do you think ?

> 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.0.9, 4.1.1
>
>
> 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-4419) Multiple inharitance levels with generics cause ClassCastException when JPA is enabled

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-4424) referenced features/bundles not installed when dropped in deploy folder

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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] [Commented] (KARAF-4927) NamespaceHandlers should return null for unknown namespaces

[JIRA]

[ 
https://issues.apache.org/jira/browse/KARAF-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842453#comment-15842453
 ] 

Jean-Baptiste Onofré commented on KARAF-4927:
-

[~ch...@die-schneider.net] can you take a look on this one please ?

Thanks !

> NamespaceHandlers should return null for unknown namespaces
> ---
>
> Key: KARAF-4927
> URL: https://issues.apache.org/jira/browse/KARAF-4927
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.0.8
>Reporter: Daniel Kulp
>Assignee: Christian Schneider
> Fix For: 4.1.0, 4.0.9
>
>
> The namespacehandler for shell does a:
> return getClass().getResource("karaf-shell-1.1.0.xsd");
> for unknown namespaces.   It should return null.  Right now, users will get 
> an error at startup of:
> "NamespaceHandler org.apache.karaf.shell.console.commands.NamespaceHandler is 
> behaving badly and should be fixed"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4707) Add pax-url-classpath feature

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-4927) NamespaceHandlers should return null for unknown namespaces

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4927:

Assignee: Christian Schneider  (was: Jean-Baptiste Onofré)

> NamespaceHandlers should return null for unknown namespaces
> ---
>
> Key: KARAF-4927
> URL: https://issues.apache.org/jira/browse/KARAF-4927
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.0.8
>Reporter: Daniel Kulp
>Assignee: Christian Schneider
> Fix For: 4.1.0, 4.0.9
>
>
> The namespacehandler for shell does a:
> return getClass().getResource("karaf-shell-1.1.0.xsd");
> for unknown namespaces.   It should return null.  Right now, users will get 
> an error at startup of:
> "NamespaceHandler org.apache.karaf.shell.console.commands.NamespaceHandler is 
> behaving badly and should be fixed"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4959) Log messages duplicated in log:tail

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4959:

Assignee: Christian Schneider  (was: Jean-Baptiste Onofré)

> Log messages duplicated in log:tail
> ---
>
> Key: KARAF-4959
> URL: https://issues.apache.org/jira/browse/KARAF-4959
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.1.0
>
>
> When starting a fresh karaf 4.1.0-SNAPSHOT log:tail shows multiple identical 
> log messages:
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle 

[jira] [Updated] (KARAF-4953) Completion trim last character in the delegate buffer

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4953:

Fix Version/s: (was: 4.1.0)
   4.1.1

> Completion trim last character in the delegate buffer
> -
>
> Key: KARAF-4953
> URL: https://issues.apache.org/jira/browse/KARAF-4953
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Guillaume Nodet
> Fix For: 4.1.1
>
>
> When using tab key for the completion, even if the proposed completion are 
> good, the last character in the command is trimmed.
> For instance:
> {code}
> karaf@root()> feature:install transaction
> {code}
> the cursor is on 'n' and when completing:
> {code}
> karaf@root()> feature:install transactio-api
> {code}
> instead of {{transaction-api}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4959) Log messages duplicated in log:tail

[JIRA]

[ 
https://issues.apache.org/jira/browse/KARAF-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842450#comment-15842450
 ] 

Jean-Baptiste Onofré commented on KARAF-4959:
-

[~ch...@die-schneider.net] can you take a look on this one please ?

Thanks !

> Log messages duplicated in log:tail
> ---
>
> Key: KARAF-4959
> URL: https://issues.apache.org/jira/browse/KARAF-4959
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.1.0
>
>
> When starting a fresh karaf 4.1.0-SNAPSHOT log:tail shows multiple identical 
> log messages:
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:11,950 | INFO  | pool-16-thread-1 | core 
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering 
> org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=158c5ff9-fda4-472b-82d4-3bf16edde37c
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | Registering 
> commands for bundle org.apache.karaf.event/4.1.0.SNAPSHOT
> 2017-01-27 09:02:12,237 | INFO  | FelixStartLevel  | CommandExtension 
> | 43 - org.apache.karaf.shell.core - 4.1.0.SNAPSHOT | 

[jira] [Updated] (KARAF-4829) Make sure configFile in features makes config available early

[Christian Schneider (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider updated KARAF-4829:
---
Fix Version/s: 4.2.0

> Make sure configFile in features makes config available early
> -
>
> Key: KARAF-4829
> URL: https://issues.apache.org/jira/browse/KARAF-4829
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-config
>Affects Versions: 4.0.7
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.0.9
>
>
> We currently have the config and configFile elements in feature files.
> Config writes the given entries to ConfigAdmin while configFile writes a file.
> So configFile is needed if the user should get a nice file to edit. The 
> problem with configFile is that ConfigurationAdmin reads the files 
> asyncronously. So bundles of the feature might already be started at the time 
> the config is written.
> So bundles might need to restart or if they only process the config once are 
> in a kind of invalid state that does not relfect the config from the feature.
> So I propose to also write the config to ConfigAdmin if configFile is used. 
> This should allow the bundles to come up in the correct state from the start.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4092) feature.xml to support SystemProperties

[Christian Schneider (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842436#comment-15842436
 ] 

Christian Schneider commented on KARAF-4092:


I think we should not allow this. I think features should always do the same 
independent of the environment. For example it is completely useless to 
validate a feature if it can behave differently next time.
So I am -1 on this change.

> 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.9
>
>
> 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-4064) Support version ranges for feature refs in the assembly goal

[Christian Schneider (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider updated KARAF-4064:
---
Fix Version/s: (was: 4.1.0)
   4.2.0

> Support version ranges for feature refs in the assembly goal
> 
>
> Key: KARAF-4064
> URL: https://issues.apache.org/jira/browse/KARAF-4064
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-tooling
>Affects Versions: 4.0.2
>Reporter: Christian Schneider
> Fix For: 4.2.0
>
>
> Currently we copy all features with the given name if a feature version is 
> given as a range like [1,2). 
> We should only copy the features that match the specified range.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4000) Karaf maven plugin and feature service should also validate conditional bundles

[Christian Schneider (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider updated KARAF-4000:
---
Fix Version/s: (was: 4.1.0)
   4.2.0

> Karaf maven plugin and feature service should also validate conditional 
> bundles
> ---
>
> Key: KARAF-4000
> URL: https://issues.apache.org/jira/browse/KARAF-4000
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature, karaf-tooling
>Affects Versions: 4.0.1
>Reporter: Christian Schneider
> Fix For: 4.2.0
>
>
> There is an error in the transaction feature. 
> Start karaf 4.0.1
> > feature:install transaction 
> As karaf by default installs aries blueprint we would expect the conditional 
> bundles in the transaction feature to also be installed. After the command 
> above the transaction.blueprint bundle is missing though.
> The reason is that the bundle does not resolve as a requirement is missing. 
> The expected behaviour would be that the transaction feature is not installed 
> as it does not fully resolve.



--
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

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-4515) Add kar:extract command (and MBean operation)

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-4434) Version range not correctly resolved for distribution build

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
>
> 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-4534) Assembly builder does not support file urls in features

[JIRA]

 [ 
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.9)
   (was: 4.1.0)

> Assembly builder does not support file urls in features
> ---
>
> 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
>
> [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=*;-noimport:=true;version="1.8"
>   at 
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:71)
>   at 
> 

[jira] [Resolved] (KARAF-4534) Assembly builder does not support file urls in features

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4534.
-
Resolution: Not A Problem

Not sure what we can do: we already added wrap, blueprint, ... protocols 
support in the Maven plugin.

> Assembly builder does not support file urls in features
> ---
>
> 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
>
> [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=*;-noimport:=true;version="1.8"
>   at 
> 

[jira] [Updated] (KARAF-4537) Karaf Maven Plugin should respect scope when building a feature

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4537:

Fix Version/s: (was: 4.1.0)
   4.1.1

> Karaf Maven Plugin should respect scope when building a feature
> ---
>
> Key: KARAF-4537
> URL: https://issues.apache.org/jira/browse/KARAF-4537
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-tooling
>Affects Versions: 4.0.5
>Reporter: Viktor Kozlov
> Fix For: 4.1.1
>
>
> I am building a feature without a feature template file. I list my feature 
> content via pom dependencies.
> For example:
> 
> 
> org.apache.geronimo.specs
> geronimo-validation_1.1_spec
> compile
> 
> 
> org.apache.geronimo.specs
> geronimo-el_2.2_spec
> compile
> 
> 
> commons-collections
> commons-collections
> compile
> 
> 
> commons-beanutils
> commons-beanutils
> compile
> 
> 
> org.apache.bval
> org.apache.bval.bundle
> compile
> 
> 
> The target file is OK except I need to mark somehow whether bundle is 
> dependency or not.
> dependency="true">mvn:org.apache.geronimo.specs/geronimo-validation_1.1_spec
> I think maven runtime scope would be nice.



--
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

[JIRA]

 [ 
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.1.0)
   4.1.1

> 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.0.9, 4.1.1
>
> 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)