You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by "Koprowski, Mariusz" <Ma...@Hexagonmining.com> on 2017/04/19 16:58:17 UTC

Hiding standard features

Hi All is ther any way to group or hide standard features ?
E.g. I have a activemq features and I would like to group them all in to MyActiveMQ feature... how this can be done ? And can it be done ?

Should I create new feature that will be a copy of ActiveMQ features with hidden set to true and MyActiveMQ that will combine that features ??

Best regards
--
Mariusz Koprowski

Re: Hiding standard features

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,

tweaking the ACL you can limit the actions on some subset of features.

Regards
JB

On 04/19/2017 06:58 PM, Koprowski, Mariusz wrote:
> Hi All is ther any way to group or hide standard features ?
> E.g. I have a activemq features and I would like to group them all in to
> MyActiveMQ feature... how this can be done ? And can it be done ?
>
> Should I create new feature that will be a copy of ActiveMQ features with hidden
> set to true and MyActiveMQ that will combine that features ??
>
> Best regards
> --
> Mariusz Koprowski
>

-- 
Jean-Baptiste Onofr�
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Hiding standard features

Posted by Steinar Bang <sb...@dod.no>.
>>>>> "Koprowski, Mariusz" <Ma...@Hexagonmining.com>:

> Hi All is ther any way to group or hide standard features ?

Why do you need to hide it?

If you don't install it or require it, it's never loaded.

> E.g. I have a activemq features and I would like to group them all in
> to MyActiveMQ feature... how this can be done ? And can it be done ?

> Should I create new feature that will be a copy of ActiveMQ features
> with hidden set to true and MyActiveMQ that will combine that features
> ??

That's what I would have done.  I would also have given the features
different names than the existing features.

It might be that loading a feature repository with new version of
existing features would "overrule" the built-in features (I haven't
tried), but why court a possible conflict...?