JB, I noticed that Karaf 2.2.2 is in the works. Have you had any time to look at the issues I reported? At least concerning adding system properties outside the Karaf installation?
/Bengt 2011/6/9 Bengt Rodehav <[email protected]> > Thanks JB! > > /Bengt > > 2011/6/9 Jean-Baptiste Onofré <[email protected]> > >> Hi Bengt, >> >> thanks for the reminder and sorry that you don't get any feedback before. >> >> I'm gonna take a look on your issues. >> >> Regards >> JB >> >> >> On 06/09/2011 07:38 PM, Bengt Rodehav wrote: >> >>> Hi JB, >>> >>> I've created a product (called Connect) that customises Karaf in lots of >>> different ways. One of them is to modify karaf.bat and >>> karaf-wrapper.conf in order to set a number of "standard" system >>> properties that Connect depends on. >>> >>> However, Connect is a pretty general integration platform that we use in >>> many different ways - it is not feasible to make customised packaging in >>> all these cases. Users need to be able to define their own (installation >>> specific) system properties to be used in e g configuration files picked >>> up by file install. I want these system properties to be defined outside >>> of the Karaf installation without having to modify the installation >>> itself. >>> >>> I've written about customisation of Karaf before on this list (I think >>> you took part in that conversation). >>> >>> I ended up creating the following JIRA's but I haven't seen any activity >>> in this area which is why I now try to narrow down the scope to just >>> adding system properties using an extension point. >>> >>> https://issues.apache.org/jira/browse/KARAF-474 >>> https://issues.apache.org/jira/browse/KARAF-475 >>> >>> For me, it's very important that it is possible to customise Karaf by >>> extension points - not by modifying the files that are included in the >>> Karaf installation. >>> >>> /Bengt >>> >>> >>> >>> 2011/6/9 Jean-Baptiste Onofré <[email protected] <mailto:[email protected]>> >>> >>> >>> Hi Bengt, >>> >>> What you can do is: >>> >>> bin/karaf /tmp/my-rc >>> >>> and my-rc can contain: >>> >>> JAVA_OPTS="-Dmy.property=my" >>> >>> You will have my.property in the System properties and you will be >>> able to use it in blueprint for instance. >>> >>> Regards >>> JB >>> >>> >>> On 06/09/2011 04:18 PM, Bengt Rodehav wrote: >>> >>> I would like to add system properties to Karaf without having to >>> manually edit the file system.properties. The reason is that I >>> want to >>> be able to use as much as possible of a vanilla Karaf. Is that >>> possible? >>> >>> I have seen that custom.properties can be used to override >>> settings in >>> config.properties but I haven't seen any property that allows me >>> to >>> specify a filename containing system properties. What I'm >>> looking for is >>> something similar to the "${includes}" property in >>> config.properties. >>> That property allows me to list several files that contain >>> configuration >>> properties. It would be nice if config.properties contained a >>> property - >>> say "system.properties" that would contain a list of files >>> containing >>> system properties that would be added at boot time. >>> >>> /Bengt >>> >>> >>> >
