Hi Christian,
I have came across the same issue you mentioned about the child instances not
having full set of maven repos. I think the approach you mentioned of using
template is a good idea. I always felt it reduces the benefit of having child
instance command greatly if it can't be used
Another way would be to use the org.ops4j.pax.url.mvn.cfg from the root
instance. I think the maven settings are typically global and will not
change from instance to instance.
What do you think?
Christian
Am 16.05.2012 11:26, schrieb Ulhas Bhole (OS):
Hi Christian,
I have came across the
Just a reminder.
The purpose of child instance is to create:
- atomic instances
- isolated from others instances (including the root one)
That's why an child instance (at creation) doesn't inherit from the root
one (it's a embedded bootstrap).
We introduced the clone command to create child
I think the clone command might be good enough.
So you could
instance:create template
.. add the configurations necessary
instance:clone instance1
That might already be good enough.
Christian
Am 16.05.2012 11:56, schrieb Jean-Baptiste Onofré:
Just a reminder.
The purpose of child instance
Yes, it's the goal. admin:clone is available since Karaf 2.2.4 or so.
Regards
JB
On 05/16/2012 12:03 PM, Christian Schneider wrote:
I think the clone command might be good enough.
So you could
instance:create template
.. add the configurations necessary
instance:clone instance1
That might
Hi all,
We fixed 77 issues in this release, 22 issues are pending for next releases.
Release Notes:
http://svn.apache.org/repos/asf/karaf/cellar/tags/cellar-2.2.4/RELEASE-NOTES
Staging repo:
https://repository.apache.org/content/repositories/orgapachekaraf-096/
Please vote to approve this
