You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by asookazian2 <as...@gmail.com> on 2014/05/08 20:50:22 UTC
copying karaf high level folder for testing purposes
I am copying an existing working karaf extraction with features/bundles
installed, etc. I'm doing this to jump start testing so I don't have to
uninstall/install all features/bundles all over again every test cycle. It
seems that there are some hard-codings in some config files in karaf that
point to the original (source) karaf I copied from.
Is this generally unrecommended to copy setup Karafs like this?
--
View this message in context: http://karaf.922171.n3.nabble.com/copying-karaf-high-level-folder-for-testing-purposes-tp4033068.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: copying karaf high level folder for testing purposes
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
You can do that, and it's basically what's instance:clone does. But some
file should be filtered like data/karaf.log for instance.
Regards
JB
On 05/08/2014 08:50 PM, asookazian2 wrote:
> I am copying an existing working karaf extraction with features/bundles
> installed, etc. I'm doing this to jump start testing so I don't have to
> uninstall/install all features/bundles all over again every test cycle. It
> seems that there are some hard-codings in some config files in karaf that
> point to the original (source) karaf I copied from.
>
> Is this generally unrecommended to copy setup Karafs like this?
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/copying-karaf-high-level-folder-for-testing-purposes-tp4033068.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com