Re: Karaf 4.0.5 prerequisite feature not installed with correct version

2016-09-01 Thread Guillaume Nodet
I see, the documentation clearly needs to be fixed. Though what I said about feature:install holds true, the behavior is different afaik. 2016-09-02 2:14 GMT+02:00 oski_bear : > I'm sorry but that makes no sense. The documentation is in reference to > defining a

Re: Blueprint System Properties not resolved

2016-09-01 Thread Jean-Baptiste Onofré
Hi Alex, I answered to another user couple of days ago with the same question (system property in blueprint) and he said it works fine. Can you check the actual value of user.home ? I will try by my side. Regards JB On 09/01/2016 07:45 PM, Alex Soto wrote: Hello, I have a blueprint

Unable to use http://karaf.apache.org/xmlns/shell/v1.0.0

2016-09-01 Thread kotoole
Within my Blueprint file, if I use the http://karaf.apache.org/xmlns/shell/v1.*0*.0 namespace, I get the following exception (notice it refers to 1.1.0 even though I am using 1.0.0) org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, 'http://schemas.xmlsoap.org/wsdl/', of an

Re: Blueprint System Properties not resolved

2016-09-01 Thread Alex Soto
Still didn’t work. Maybe I am running the wrong version? These are the versions of the jar I see under system/org/apache/aries/blueprint directory of Karaf. org.apache.aries.blueprint.api-1.0.1.jar org.apache.aries.blueprint.cm-1.0.7.jar org.apache.aries.blueprint.core-1.4.5.jar

Re: Blueprint System Properties not resolved

2016-09-01 Thread Christian Lutz
Hello Alex, I did use the same, but in my case I had to update the version of the schemas to. http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.3.0 and http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.5.0

Re: Blueprint System Properties not resolved

2016-09-01 Thread Alex Soto
No, I checked. This is still in integration test mode, with Pax-Exam, so the directory does not yet have any cfg files other than Karaf’s own. Best regards, Alex soto > On Sep 1, 2016, at 2:12 PM, Guillaume Nodet wrote: > > Are you sure you don't have this value coming

Re: Blueprint System Properties not resolved

2016-09-01 Thread Guillaume Nodet
Are you sure you don't have this value coming from the configuration in etc/my.config.id.cfg or something like that ? We had such a pattern in multiple places in Karaf 2.x and it was working fine. 2016-09-01 19:45 GMT+02:00 Alex Soto : > Hello, I have a blueprint bundle

Blueprint System Properties not resolved

2016-09-01 Thread Alex Soto
Hello, I have a blueprint bundle defined as: http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;

Re: Problems with Karaf 4.0.5 vs. Karaf 4.0.4

2016-09-01 Thread kotoole
I think I am actually encountering a different issue than the one originally reported. It is still related to namespaces, but offline access does not appear to be the issue. I apologize for the confusion. I do believe Aries Blueprint Core 1.6.2 fixed the original problem reported. I will create a

Re: Replace framework version in distribution

2016-09-01 Thread Jean-Baptiste Onofré
It will change the etc/config.properties but it won't populate the system folder with the framework artifact. Regards JB On 09/01/2016 04:24 PM, Dmytro Pishchukhin wrote: Do you mean to create a new framework feature? I found that I can change config file properties with

Re: Replace framework version in distribution

2016-09-01 Thread Dmytro Pishchukhin
Do you mean to create a new framework feature? I found that I can change config file properties with assembly-property-edits.xml. Is it not a better way? -- View this message in context: http://karaf.922171.n3.nabble.com/Replace-framework-version-in-distribution-tp4047812p4047816.html Sent

Replace framework version in distribution

2016-09-01 Thread Dmytro Pishchukhin
Hi All, is it possible to replace framework version during distribution build? e.g. I want to use felix 5.2.0 instead default version 5.4.0. Kind regards, Dmytro -- View this message in context: http://karaf.922171.n3.nabble.com/Replace-framework-version-in-distribution-tp4047812.html Sent

Re: Managed Service Factory Configuration file deployment

2016-09-01 Thread manisv
Thanks JB. It works fine now, Config files are now getting deployed automatically into etc folder after feature deployment. I made changes as done in the below artifact. Regards, Mani -- View this message in context:

Re: Problems with Karaf 4.0.5 vs. Karaf 4.0.4

2016-09-01 Thread Jean-Baptiste Onofré
Hi JP Karaf 4.0.6 already uses Aries Blueprint Core 1.6.2: https://github.com/apache/karaf/blob/karaf-4.0.6/pom.xml So, it seems to not be enough. That's why I have to investigate. Regards JB On 09/01/2016 11:27 AM, CLEMENT Jean-Philippe wrote: Hi JB, As far as I understand, using

Managed Service Factory Configuration file deployment

2016-09-01 Thread manisv
Hi, I would like to know how to deploy configuration (.cfg) files for a managedservicefactory into /etc folder of Karaf instance automatically. My understanding is every config file has to be under etc. Below are the steps I've done so far. 1. Have created a managedservicefactory class A having