Yes, both are possible.
Maybe keeping all in org.apache.karaf.features.core with a configuration to use
a different deploy/approach is better than a complete new features bundle.
It’s not a problem to me to refactor what I did.
Thoughts ?
Regards
JB
> Le 19 mai 2021 à 08:01, Grzegorz Grzybek
śr., 19 maj 2021 o 07:53 Jean-Baptiste Onofre napisał(a):
> Hi,
>
> Actually, it’s a complete separated bundle.
>
> So, in the Karaf standard distribution, you will have
> org.apache.karaf.features.core in etc/startup.properties: that’s the
> regular/current one with the resolver.
>
> Alternative
Hi,
Actually, it’s a complete separated bundle.
So, in the Karaf standard distribution, you will have
org.apache.karaf.features.core in etc/startup.properties: that’s the
regular/current one with the resolver.
Alternatively, you will have another distribution (I have to think about the
name),
Hello
śr., 19 maj 2021 o 07:35 Jean-Baptiste Onofre napisał(a):
> Hi,
>
> Regarding recent comments from users and lot of refresh issues/questions
> we have in the past, I moved forward with a new simple features service
> that doesn’t use the resolver. It basically reads the features repo
> def
Hi,
Regarding recent comments from users and lot of refresh issues/questions we
have in the past, I moved forward with a new simple features service that
doesn’t use the resolver. It basically reads the features repo definition and
just install what’s define in there statically.
I will prepare
