Hello,
the following thread implies, that there should be a separation between
directories a write access is needed and the read only data that is packaged
by distribution packages.
http://karaf.922171.n3.nabble.com/using-KARAF-HOME-BASE-vars-tp4031255p4031257.html
ATM I realized that there are m
Hello,
I want to create a feature, that contains a jar (third party one).
The manifest of that bundle contains:
Require-Bundle: system.bundle
If I want to install the kar / feature that contains that bundle I get the
following message:
Error executing command: Unable to resolve root: missing requ
If I am using "karaf.framework=felix" all seems to be working.
If I am using "karaf.framework=equinox" I got the reported error.
Here you could find a kar that demonstrate the problem:
https://drive.google.com/file/d/0Bx99QXY8p6gvY3BoMXlZeXRIOWs/view?usp=sharing
kar:install should write the above
So, what the next step(s) to do?
* Were you able to throw it a look?
* Should I create an issue on Jira and link it here?
* Will you create an issue after investigation and post the link here?
--
View this message in context:
http://karaf.922171.n3.nabble.com/4-0-0-M2-feature-install-system-bu
I am using karaf in a read only installation.
- data
- instances
- lock
This directories / file are created.
It would be nice, if ALL runtime data could be written elsewhere (not only
data, also instances and lock).
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-insta
Any news?
Have you been able to solve this for the 4.0.0 release?
--
View this message in context:
http://karaf.922171.n3.nabble.com/4-0-0-M2-feature-install-system-bundle-tp4040561p4041117.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Using the kar posted above will succeed using 4.0.0 with Equinox and Felix.
I try to use the bigger kar file next week and report again.
--
View this message in context:
http://karaf.922171.n3.nabble.com/4-0-0-M2-feature-install-system-bundle-tp4040561p4041119.html
Sent from the Karaf - User ma
I would like to use the recently released version 4.0.0 to create a custom
distribution.
I started with the official documentation:
https://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html
There is this dependency:
org.apache.karaf.features
I added the pom.xml to a repository.
You can test it if
* git clone g...@github.com:maggu2810/karaf-custom-distribution.git
* cd karaf-custom-distribution
* mvn clean verify
* cd target
* tar xzf my.distribution-1.0.tar.gz
* cd my.distribution-1.0
* grep -A 4 featuresRepositories etc/org.apache.ka
Last but not least, I think the example miss the version of the dependencies.
See
https://github.com/maggu2810/karaf-custom-distribution/commit/68113da531e4776a670fe5f0a1c307b8ceeddb3b
--
View this message in context:
http://karaf.922171.n3.nabble.com/custom-distribution-features
I have tested different versions.
Will have a further look at, but perhaps someone who is familiar with
karaf-assembly (I started yesterday my first steps) could have a look at.
4.0.0.M1
featuresRepositories =
mvn:org.apache.karaf.features/standard/4.0.0.M1/xml/features,mvn:org.apache.karaf.featur
Hello,
reading
"https://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html";
the scope of maven dependencies is used to decide the integration of a
feature (startup.properties, boot feature, ...).
I am missing some information what is the exact difference between
startup.prope
Hello,
there is the file etc/system.properties that could be used ti add system
properties that are available at the very beginning of the Karaf's boot
process.
This file is shipped with karaf and contains already a few such options.
I would like to extend the list of properties. So I can add new
Hi,
> So, basically, you can have an empty system.properties, and populate all
> with -D.
I do not want to change the system.properties that comes with Karaf
(also not empty it). ;-)
I would like to add a separate file with system properties.
Another approach would be if the assembly builder will
> The fact is that Karaf reads etc/override.properties and treats its
> contents as 'overrides' over system.properties. So, my assembly has
> one of these to set some properties.
At which time the file is read?
I added a file override.properties to my 'src/main/resources/etc/' directory.
The file
2015-08-21 15:25 GMT+02:00 Benson Margulies [via Karaf]
:
> It is read at startup. The important question is whether it ends up in the
> etc directory. Have you looked at the generated assembly to see if the file
> is in the right place? Perhaps it's not travelling from src/main/resources
> to etc
; Regards
>> JB
>>
>> On 08/21/2015 03:44 PM, Benson Margulies wrote:
>>>
>>> Wait, don't use 'overrides.properties', use 'custom.properties'.
>>>
>>>
>>>
>>> On Fri, Aug 21, 2015 at 9:41 AM, maggu2810
userdata=${karaf.base}/oh2/userdata
smarthome.configdir=${karaf.base}/oh2/conf
==
Could you point me to the correct content for the setenv?
>
> I can add a systemoverride.properties file, but it's basically the same
> as bin/setenv.
>
> Regards
> JB
>
> On 08/21/2015 0
2015-08-21 16:16 GMT+02:00 Benson Margulies [via Karaf]
:
> I think that having a whole series of separate override files is a bad
> design, and it would be better to be able to say:
>
> KARAF_ETC=/my/override-directory:/the/directory/with/the/usual/files
An overlay is a nice thing, but you have t
Hello,
is the EIK project still alive?
It seems not to be working with Karaf 4 and perhaps also not with Eclipse
Mars. Don't know who is responsible for the NPE.
Found missing support in the current EIK sources. The current implementation
does a
* lookup in etc for a file called "org.apache.felix.
20 matches
Mail list logo