Hi Marco, 1. There is a custom.properties file in the Karaf etc folder where you can override properties set in the other properties files.
2. Cellar doesn't use a custom distribution. Everything can be setup from the features file. Cellar also creates a kar file which allows for offline installation since everything is bundled into it rather than retrieved from the maven repo. The following should help clarify how the properties files are handled in a maven build. The first thing is that you use the maven build plugin (I think is the name offhand) to specify additional files to be placed into the maven repo as individual artifacts, such as the configuration files. Maven only allows a single artifact to be produced for each pom.xml, this plugin works around that. The second thing is that you use specify the maven coordinates of the configuration file that was put into the maven repo in your features.xml as an attribute of the config or the configfile element. Hopefully that helps. Ryan On Dec 4, 2013 9:34 AM, "Marco" <[email protected]> wrote: > Nevermind, I got it working (was a mvn url bad syntax, even If I still > don't > know how does maven handle these two steps to work in different phases). > > I take the chance to ask you something else, but still related: > > 1) override existing .properties file (e.g. I need to customize > system.packeges.extra to export some libraries in /lib) > > 2) make all the application ready-to-install by feature, avoiding the use > of > a custom distribution (like you do in cellar), considering the fact that I > need to customize : > > - some cfg files (ok I got it) > - adding non-OSGi libraries in /lib and > - system.properties to export some packages of the lib > > Is it possible to do all those step by feature? Thank you again. > > Marco > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Config-in-features-xml-to-config-file-tp4030504p4030520.html > Sent from the Karaf - User mailing list archive at Nabble.com. >
