You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Fabian Lange (JIRA)" <ji...@apache.org> on 2015/02/09 11:09:34 UTC

[jira] [Created] (KARAF-3509) make it easier to customize properties like org.osgi.framework.system.packages.extra

Fabian Lange created KARAF-3509:
-----------------------------------

             Summary: make it easier to customize properties like org.osgi.framework.system.packages.extra
                 Key: KARAF-3509
                 URL: https://issues.apache.org/jira/browse/KARAF-3509
             Project: Karaf
          Issue Type: Improvement
          Components: karaf-tooling
            Reporter: Fabian Lange


I am using the 4.0M1 maven plugin to generate a Karaf distribution.

I need to include Hyperic Sigar for many bundles. Because Sigar uses some odd resolution mechanism for native libraries (which need to be in the same folder), the easiest solution is to put sigar and the native libs into the lib directory during build.
However I need to add "org.hyperic.sigar" to the "org.osgi.framework.system.packages.extra".

It turns out that this is not so easy. This value contains some generated values. What I do right ow, is that I copied this long value to the custom.properties, which i copy over using maven-resources plugin, but I also need to specify overwrite, because an empty custom.properties file is already present.

What I dislike most about this solution is that my custom properties needs to contain the value from config.properties + my extension. But if the value in config.properties changes (like when upgrading to M2) I will not notice that I "destroy" the value by overwriting with my own.

I wonder if there also use cases for other properties to be modified with the maven plugin.



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