Hi,

an alias feature is a wrapper feature just containing another feature.

The reason why we did this is that the http, jetty features were in Karaf before (not in pax-web). So, we created the pax-web features with a different name: pax-web-jetty instead of jetty. However, legacy and other projects/applications use the "old" name. So, for backward compatibility, we created this "alias"/wrap feature.

Regards
JB

On 07/13/2016 04:56 AM, Allan C. wrote:
Hi JB,

Just seeking clarifications.

1. When you say jetty is an alias feature, what does alias feature means?

2. Is it safe to say pax-jetty depends on jetty and not the other way round?

Thanks in advance.

Regards,
Allan C.

On Tue, Jul 5, 2016 at 9:01 AM, Allan C. <[email protected]
<mailto:[email protected]>> wrote:

    Noted. Thanks.

    Regards,
    Allan C.

    On Tue, Jul 5, 2016 at 3:40 AM, Jean-Baptiste Onofré
    <[email protected] <mailto:[email protected]>> wrote:

        Thanks Allan,

        jetty is an alias feature on top of pax-jetty (for backward
        compatibility).

        Definitely, we upgraded in pax-web, but forgot to update the
        jetty alias feature.

        Let me create a Jira to fix that.

        Thanks !
        Regards
        JB

        On 07/04/2016 10:20 AM, Allan C. wrote:

            I am playing around with 4.0.5 and I noticed that the
            versions for the
            jetty and pax-jetty are different. In Fuse 6.2.1 (I think it
            is based on
            Karaf 2.4.0), the versions are the same.

            JBossFuse:karaf@root> features:list | grep jetty
            [installed  ] [*8.1.17.v20150415*     ] jetty
                            karaf-2.4.0.redhat-621084
                  Provide Jetty engine support
            [installed  ] [2.15.1.redhat-621084 ] camel-jetty
                          camel-2.15.1.redhat-621084

            [uninstalled] [2.15.1.redhat-621084 ] camel-jetty9
                         camel-2.15.1.redhat-621084

            [installed  ] [*8.1.17.v20150415*     ] pax-jetty
                            org.ops4j.pax.web-3.2.5
                  Provide Jetty engine support
            [installed  ] [3.0.4.redhat-621084  ] cxf-http-jetty
                         cxf-3.0.4.redhat-621084

            Karaf 4.0.5:

            karaf@root(feature)> list | grep jetty
            jetty                                   | *9.2.10.v20150310* |
               | Started     | standard-4.0.5              |
            jetty                                   | 8.1.14.v20131031
            |          |
            Uninstalled | standard-4.0.5              |
            cxf-http-jetty                          | 3.1.5
            |          |
            Started     | cxf-3.1.5                   |
            pax-jetty                               | *9.2.15.v20160210* |
               | Started     | org.ops4j.pax.web-4.2.6     | Provide
            Jetty engine support
            pax-jetty-spdy                          | 4.2.6
            |          |
            Uninstalled | org.ops4j.pax.web-4.2.6     | Optional
            additional feature
            to run Jetty with SPDY
            pax-http-jetty                          | 4.2.6
            |          |
            Started     | org.ops4j.pax.web-4.2.6     |
            camel-jetty                             | 2.16.3
              |          |
            Uninstalled | camel-2.16.3                |
            camel-jetty9                            | 2.16.3
              |          |
            Started     | camel-2.16.3                |
            karaf@root(feature)>

            Would it be a concern?

            Regards,
            Allan C.


        --
        Jean-Baptiste Onofré
        [email protected] <mailto:[email protected]>
        http://blog.nanthrax.net
        Talend - http://www.talend.com




--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to