Gert,
the only thing is that admin:create won't create a "fresh empty" Karaf
instance: if the user changed the startup.properties, admin:create will
create an instance already with these changes included. Currently,
admin:create creates a complete fresh instance, ignoring the changes
from the user in the root instance.
Regards
JB
On 10/31/2013 09:20 PM, Gert Vanthienen wrote:
Jean-Baptiste, Ehsan,
How about making that configurable instead of using the -c parameter?
We could still leave the default to pick the original, embedded Karaf
config/startup.properties, so for Karaf nothing would change.
But at least that way, projects like ServiceMix could just have the
admin:create command do the right thing for that particular project by
simply adding the org.apache.karaf.admin.core.cfg file to their etc
directory, without the user having to be aware of the little bit of
extra tweaking required to properly bootstrap the container?
Regards,
Gert
On Thu, Oct 31, 2013 at 7:41 PM, Jean-Baptiste Onofré <[email protected]> wrote:
Good idea. I will do that.
The thing
Regards
JB
On 10/31/2013 01:28 PM, zaerymoghaddam wrote:
Hi guys
Isn't it possible having an option on admin:create to decide whether to
create a new plain instance or use root instance configurations?
For example: 'admin:create -c'.
which '-c' could mean clone root instance's configuration.
Regards
Ehsan
-----
E.Z.Moghaddam
[email protected]
--
View this message in context:
http://karaf.922171.n3.nabble.com/Which-config-properties-and-startup-properties-with-admin-create-tp4030050p4030137.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
