Yes, Cave is a good option, especially with the last Cave Deployer
feature included by JB that is really interesting :)
Le 09/07/2018 à 21:29, Nicolas Brasey a écrit :
> Our ideas is to provide maven repositories for each "application".
> These repos should contains features.xml which refers to
Cool !
Don't hesitate to ping me (even on Hangout or whatever).
I'm always happy to help !
Regards
JB
On 09/07/2018 19:30, Nicolas Brasey wrote:
> Thanks for that.
>
> I'll experiment a little bit this week and come back to you in case I
> need more guidance.
>
> Thanks again.
>
> Nicolas
>
Thanks for that.
I'll experiment a little bit this week and come back to you in case I need
more guidance.
Thanks again.
Nicolas
On Fri, Jul 6, 2018 at 3:56 PM Jean-Baptiste Onofré wrote:
> Hi Nicolas,
>
> I would recommend:
>
> 1. To take a look if you can't populate the system folder or
Our ideas is to provide maven repositories for each "application". These
repos should contains features.xml which refers to jars which are also in
the same repos or jars that are already available. I wanted to leverage the
fact that each kar repo is automatically available as remote repo by the
Hi Francois,
No worries, thanks for the link, I'll have a look!
Nicolas
On Fri, Jul 6, 2018 at 3:43 PM Francois Papon
wrote:
> Ok, sorry for the noise ;)
>
> May be you can write your own Deployer as a workaround, there is an
> example here :
>
Hi Nicolas,
I would recommend:
1. To take a look if you can't populate the system folder or even use
Cave on Karaf instance, acting as Maven repository that you can populated
Anyway, Kar is also an option but it needs a clean packaging and
dependency on kar file:
1. Your can package all as a
Le ven. 6 juil. 2018 à 14:56, Nicolas Brasey a
écrit :
> Yes we tried but had problems with the KarService implementation of
> karaf v.4.1.2 which had some issues with starting our features, there was
> some kind of loop which ended-up installing/uninstalling many time the same
> features, it
Ok, sorry for the noise ;)
May be you can write your own Deployer as a workaround, there is an
example here :
https://github.com/jbonofre/karaf/tree/DEV_GUIDE/examples/karaf-deployer-example
François
Le 06/07/2018 à 17:33, Nicolas Brasey a écrit :
> Hi Francois,
>
> This is not possible, the
Hi Francois,
This is not possible, the servers are running in security zones without
internet access, no proxying or tunneling is possible. But this is not
really the problem as we use the kars which contain all we need.
Nicolas
On Fri, Jul 6, 2018 at 3:26 PM Francois Papon
wrote:
> Hi
Hi Nicolas,
When target machines are on a private network, it's usefull to have an
instance of Nexus used like a proxy for the externals dependencies and
the dev team can also publish their bundles on this Nexus.
regards,
François Papon
fpa...@apache.org
Yupiik - https://www.yupiik.com
Le
Yes we tried but had problems with the KarService implementation of
karaf v.4.1.2 which had some issues with starting our features, there was
some kind of loop which ended-up installing/uninstalling many time the same
features, it was not working for us, so we have now our own implementation
of a
Have you tried simply dropping the kars in the deploy folder ?
This should install / start them automatically without the need to create a
custom distribution.
Guillaume
Le jeu. 5 juil. 2018 à 13:53, Nicolas Brasey a
écrit :
> Hi all,
>
> I'm trying to find out if there is way to install a
Hi Jean-Baptiste,
Yes, our different kars have dependencies, so they must installed in a
certain order.
The features.xml only is not possible in our case because our target
machines are running on private networks without internet access, so the
kars must contain all the runtime transitive
13 matches
Mail list logo
