So all 37 files in the etc directory and the 6 files in the bin directory are hard-coded into Karaf somewhere?
I can create a new instance using instance:clone, but then there doesn't appear to be a way to start a feature programatically. On Thu, Apr 17, 2014 at 1:57 PM, Achim Nierbeck <[email protected]> wrote: > No, > > it's creating a clean installation of a Karaf setup, without any previous > knowledge, if you need a new instance that is almost the same as the one you > already have, use clone, it copies also all configurations. > > regards, Achim > > > > > 2014-04-17 18:37 GMT+02:00 Tim Moloney <[email protected]>: > >> So what is create actually doing? Can I control the configuration >> files that it creates? >> >> Thanks, >> Tim >> >> >> On Thu, Apr 17, 2014 at 12:31 PM, Achim Nierbeck >> <[email protected]> wrote: >> > No it's the other way round. If you use clone the root instance is >> > cloned. >> > If you use create it is literally like unzipping but its not actually >> > doing >> > so. >> > >> > Regards, Achim >> > >> > sent from mobile device >> > >> > Am 17.04.2014 17:48 schrieb "Tim Moloney" <[email protected]>: >> > >> >> You said that using instance:clone is "like" unzipping the Karaf zip >> >> artifact. Does is actually unzip the Karaf zip artifact? If I'm >> >> running Karaf on a machine without an Internet connection, will I have >> >> to have the Karaf zip artifact in one of my repositories? Can I >> >> override which artifact it unzips? Is there a way to specify a >> >> feature to start when using instance:clone? >> >> >> >> If I use instance:create, where does Karaf get the files for the etc >> >> directory, since it is not simply copying them from the root instance? >> >> >> >> Thanks, >> >> Tim >> >> >> >> >> >> On Thu, Apr 17, 2014 at 11:21 AM, Tim Moloney <[email protected]> >> >> wrote: >> >> > Thanks for pointing me in the right direction. >> >> > >> >> > Tim >> >> > >> >> > >> >> > On Thu, Apr 17, 2014 at 11:19 AM, Achim Nierbeck >> >> > <[email protected]> wrote: >> >> >> If you clone the root instance your modifications are transferred to >> >> >> the >> >> >> cloned instances too. If you create a new instance it's like >> >> >> unzipping >> >> >> the >> >> >> karaf zip artifact. >> >> >> >> >> >> Regards, Achim >> >> >> >> >> >> sent from mobile device >> >> >> >> >> >> Am 17.04.2014 16:55 schrieb "Tim Moloney" <[email protected]>: >> >> >> >> >> >>> I just started experimenting with instances in Karaf. I've noticed >> >> >>> that the child instances aren't getting the changes I've made to >> >> >>> etc/org.apache.karaf.features.cfg. I did the following: >> >> >>> >> >> >>> - modified the featuresRepositories property in >> >> >>> etc/org.apache.karaf.features.cfg (added a custom features >> >> >>> repository) >> >> >>> - started Karaf >> >> >>> - created an instance (instance:create foo) >> >> >>> - compared the configuration files (diff -u >> >> >>> {etc,instances/foo}/org.apache.karaf.features.cfg >> >> >>> >> >> >>> The child instance does not have my custom features repository. If >> >> >>> the child instances aren't getting org.apache.karaf.features.cfg >> >> >>> from >> >> >>> the root etc directory, where are they getting them from? Can I >> >> >>> modify this location? I know that I can use the --furl option, but >> >> >>> all of the my child instances will need my custom features >> >> >>> repository >> >> >>> and it would be simpler to configure that in one spot. >> >> >>> >> >> >>> BTW, both Karaf 3.0.0 and 3.0.1 act this way. I haven't tried any >> >> >>> other versions. >> >> >>> >> >> >>> Thanks, >> >> >>> Tim > > > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > blog <http://notizblog.nierbeck.de/> > > Software Architect / Project Manager / Scrum Master >
