You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Sai Sankar <sa...@motivitylabs.com> on 2018/12/05 09:49:55 UTC
Help to get out of pax-web from karaf distribution
Hi All
I dont want Pax-web features to be installed or installable with KARAF
4.2.0. Tried Standard and minimal distributions too, but either way it is
installing pax-web features.
Karaf Version is : 4.2
pax-web-core | 7.0.0 | | Started
| org.ops4j.pax.web-7.0.0 | Provide Core pax-web bundles
pax-jetty | 9.4.6.v20170531 | | Started
| org.ops4j.pax.web-7.0.0 | Provide Jetty engine support
pax-jetty-http2 | 7.0.0 | | Uninstalled
| org.ops4j.pax.web-7.0.0 | Optional additional feature to run
Jetty with SPDY
pax-http-jetty | 7.0.0 | | Started
| org.ops4j.pax.web-7.0.0 |
pax-http | 7.0.0 | | Started
| org.ops4j.pax.web-7.0.0 | Implementation of the OSGI HTTP
Service
pax-http-whiteboard | 7.0.0 | | Started
| org.ops4j.pax.web-7.0.0 | Provide HTTP Whiteboard pattern
support
pax-war | 7.0.0 | | Started
| org.ops4j.pax.web-7.0.0 | Provide support of a full WebContainer
pax-http-tomcat | 7.0.0 | | Uninstalled
| org.ops4j.pax.web-7.0.0 | Provide Tomcat support
pax-war-tomcat | 7.0.0 | | Uninstalled
| org.ops4j.pax.web-7.0.0 |
pax-jsf-support | 7.0.0 | | Uninstalled
| org.ops4j.pax.web-7.0.0 |
pax-jsf-resources-support | 7.0.0 | | Uninstalled
| org.ops4j.pax.web-7.0.0 | Provide sharing of resources according
to Servlet
undertow | 1.4.23.Final | | Uninstalled
| org.ops4j.pax.web-7.0.0 |
pax-http-undertow | 7.0.0 | | Uninstalled
| org.ops4j.pax.web-7.0.0 |
is there any way to skip installing pax-web features in karaf -distribution.
Thanks
Sai
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html
Re: Help to get out of pax-web from karaf distribution
Posted by Ranx <ra...@enjekt.org>.
I like the minimal distro. I've always found it easy to identify and install
features/repos that I need. It's fairly easy to be additive in using
features but more problematic to update or remove.
I'm not sure how you really get around the problem JB mentioned with third
parties that don't have valid features as was the case with Hibernate.
Obviously that's a separate issue from what should be installed by default.
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html
Re: Help to get out of pax-web from karaf distribution
Posted by Grzegorz Grzybek <gr...@gmail.com>.
Hello
Here's the configuration for official minimal distro[1].
<bootFeatures>
<feature>jaas</feature>
<feature>shell</feature>
<feature>feature</feature>
<feature>ssh</feature>
<feature>bundle</feature>
<feature>config</feature>
<feature>log</feature>
</bootFeatures>
regards
Grzegorz Grzybek
===
[1]:
https://github.com/apache/karaf/blob/master/assemblies/apache-karaf-minimal/pom.xml#L121-L130
śr., 5 gru 2018 o 13:02 Sai Sankar <sa...@motivitylabs.com>
napisał(a):
> Hello Grzegorz Grzybek
>
> Thanks for your response.
>
> For minimal distribution , in my pom.xml mentioned like below.
>
> <plugin>
> <configuration>
> <bootFeatures>
> <feature>minimal</feature>
> </bootFeatures>
> </configuration>
> </plugin>
>
>
> So, is it the way to do minimal distribution ? If not can you please
> correct
> me with right way of performing minimal distribution.
>
> regards
> Sai
>
>
>
>
>
> --
> Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html
>
Re: Help to get out of pax-web from karaf distribution
Posted by Sai Sankar <sa...@motivitylabs.com>.
Hello Grzegorz Grzybek
Thanks for your response.
For minimal distribution , in my pom.xml mentioned like below.
<plugin>
<configuration>
<bootFeatures>
<feature>minimal</feature>
</bootFeatures>
</configuration>
</plugin>
So, is it the way to do minimal distribution ? If not can you please correct
me with right way of performing minimal distribution.
regards
Sai
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html
Re: Help to get out of pax-web from karaf distribution
Posted by Grzegorz Grzybek <gr...@gmail.com>.
Hello
You have 3 choices:
- feature:uninstall them after startup (they won't be started next time
you run Karaf)
- ensure there are no such features in etc/org.apache.karaf.features.cfg
- build your own Karaf distro:
http://karaf.apache.org/manual/latest/#_custom_distributions
btw. I've started minimal 4.2.1 distribution and I don't see pax-web
bundles:
karaf@root()> la -l
START LEVEL 100 , List Threshold: 0
ID │ State │ Lvl │ Version │ Location
───┼──────────┼─────┼──────────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
0 │ Active │ 0 │ 5.6.10 │ System Bundle
1 │ Resolved │ 1 │ 4.2.1 │
mvn:org.apache.karaf.features/org.apache.karaf.features.extension/4.2.1
2 │ Active │ 5 │ 2.5.4 │ mvn:org.ops4j.pax.url/pax-url-aether/2.5.4
3 │ Active │ 8 │ 1.17.1 │ mvn:org.fusesource.jansi/jansi/1.17.1
4 │ Active │ 8 │ 1.10.1 │
mvn:org.ops4j.pax.logging/pax-logging-api/1.10.1
5 │ Active │ 8 │ 1.10.1 │
mvn:org.ops4j.pax.logging/pax-logging-log4j2/1.10.1
6 │ Active │ 9 │ 1.0.2 │
mvn:org.apache.felix/org.apache.felix.coordinator/1.0.2
7 │ Active │ 10 │ 1.9.4 │
mvn:org.apache.felix/org.apache.felix.configadmin/1.9.4
8 │ Active │ 11 │ 3.6.4 │
mvn:org.apache.felix/org.apache.felix.fileinstall/3.6.4
9 │ Active │ 15 │ 4.2.1 │
mvn:org.apache.karaf.features/org.apache.karaf.features.core/4.2.1
10 │ Active │ 20 │ 2.2.11.1 │
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jaxb-impl/2.2.11_1
11 │ Active │ 30 │ 4.2.1 │
mvn:org.apache.karaf.bundle/org.apache.karaf.bundle.core/4.2.1
12 │ Active │ 30 │ 4.2.1 │
mvn:org.apache.karaf.config/org.apache.karaf.config.core/4.2.1
13 │ Active │ 30 │ 4.2.1 │
mvn:org.apache.karaf.features/org.apache.karaf.features.command/4.2.1
14 │ Active │ 30 │ 4.2.1 │
mvn:org.apache.karaf.jaas/org.apache.karaf.jaas.command/4.2.1
15 │ Active │ 30 │ 4.2.1 │
mvn:org.apache.karaf.jaas/org.apache.karaf.jaas.config/4.2.1
16 │ Active │ 30 │ 4.2.1 │
mvn:org.apache.karaf.jaas/org.apache.karaf.jaas.modules/4.2.1
17 │ Active │ 30 │ 4.2.1 │
mvn:org.apache.karaf.log/org.apache.karaf.log.core/4.2.1
18 │ Active │ 30 │ 4.2.1 │
mvn:org.apache.karaf.shell/org.apache.karaf.shell.commands/4.2.1
19 │ Active │ 30 │ 4.2.1 │
mvn:org.apache.karaf.shell/org.apache.karaf.shell.core/4.2.1
20 │ Active │ 30 │ 4.2.1 │
mvn:org.apache.karaf.shell/org.apache.karaf.shell.ssh/4.2.1
21 │ Active │ 30 │ 0.3.11.1 │
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.not-yet-commons-ssl/0.3.11_1
22 │ Active │ 30 │ 1.7.0 │ mvn:org.apache.sshd/sshd-core/1.7.0
23 │ Active │ 30 │ 3.9.0 │ mvn:org.jline/jline-builtins/3.9.0
24 │ Active │ 30 │ 3.9.0 │ mvn:org.jline/jline-reader/3.9.0
25 │ Active │ 30 │ 3.9.0 │ mvn:org.jline/jline-terminal/3.9.0
26 │ Resolved │ 30 │ 3.9.0 │ mvn:org.jline/jline-terminal-jansi/3.9.0
regards
Grzegorz Grzybek
śr., 5 gru 2018 o 11:41 Sai Sankar <sa...@motivitylabs.com>
napisał(a):
> Hi All
>
> I dont want Pax-web features to be installed or installable with KARAF
> 4.2.0. Tried Standard and minimal distributions too, but either way it is
> installing pax-web features.
>
> Karaf Version is : 4.2
>
> pax-web-core | 7.0.0 | | Started
> | org.ops4j.pax.web-7.0.0 | Provide Core pax-web bundles
> pax-jetty | 9.4.6.v20170531 | | Started
> | org.ops4j.pax.web-7.0.0 | Provide Jetty engine support
> pax-jetty-http2 | 7.0.0 | | Uninstalled
> | org.ops4j.pax.web-7.0.0 | Optional additional feature to run
> Jetty with SPDY
> pax-http-jetty | 7.0.0 | | Started
> | org.ops4j.pax.web-7.0.0 |
> pax-http | 7.0.0 | | Started
> | org.ops4j.pax.web-7.0.0 | Implementation of the OSGI HTTP
> Service
> pax-http-whiteboard | 7.0.0 | | Started
> | org.ops4j.pax.web-7.0.0 | Provide HTTP Whiteboard pattern
> support
> pax-war | 7.0.0 | | Started
> | org.ops4j.pax.web-7.0.0 | Provide support of a full
> WebContainer
> pax-http-tomcat | 7.0.0 | | Uninstalled
> | org.ops4j.pax.web-7.0.0 | Provide Tomcat support
> pax-war-tomcat | 7.0.0 | | Uninstalled
> | org.ops4j.pax.web-7.0.0 |
> pax-jsf-support | 7.0.0 | | Uninstalled
> | org.ops4j.pax.web-7.0.0 |
> pax-jsf-resources-support | 7.0.0 | | Uninstalled
> | org.ops4j.pax.web-7.0.0 | Provide sharing of resources
> according
> to Servlet
> undertow | 1.4.23.Final | | Uninstalled
> | org.ops4j.pax.web-7.0.0 |
> pax-http-undertow | 7.0.0 | | Uninstalled
> | org.ops4j.pax.web-7.0.0 |
>
>
> is there any way to skip installing pax-web features in karaf
> -distribution.
>
> Thanks
> Sai
>
>
>
>
>
> --
> Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html
>
Re: Help to get out of pax-web from karaf distribution
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
That's the difference between minimal and standard distributions.
We can have an even "small" minimal distribution, removing the
enterprise and other standard features repos.
That's the way to go IMHO.
Regards
JB
On 05/12/2018 12:21, Christian Schneider wrote:
> I think this points to an interesting problem in current karaf.
> Karaf comes with some feature repos installed and even with some features
> installed.
> This is very good for learning karaf but it is not good when you build and
> maintain your application.
>
> Things that we currently make hard to do:
> - You have an application that is based on karaf features as well as other
> features. It is quite hard to update your application to a new karaf as it
> brings a lot of feature updates that you might not want.
> - Switch some implementations. For Sai wanted to not install pax web. In my
> recent case I wanted to update blueprint core.
>
> I think many of these problems come from the way karaf features are offered:
> - Many features are versioned together with karaf. So when you update karaf
> you get new versions of the features / bundles even if you do not want them.
> - Some karaf features combine too many unrelated things. E.g the enterprise
> feature repo combines jpa, jms, peristence providers. Sometimes even
> different versions of these.
>
> I think we can fix a lot of this by moving as many features as possible to
> the projects where the bundles come from. E.g Aries jpa already provides a
> features. This allows to use any karaf version and install any jpa version
> on it. Unfortunately this does not work in practice as the feature needs
> transactions as well as blueprint that are part of karaf itself.
>
> So I think we should move more features out of karaf and into the
> individual projects.
> Of course we must give these repos nice aliases so they are still easy to
> install.
>
> WDYT?
>
> Christian
>
>
> Am Mi., 5. Dez. 2018 um 11:41 Uhr schrieb Sai Sankar <
> saisankar.c@motivitylabs.com>:
>
>> Hi All
>>
>> I dont want Pax-web features to be installed or installable with KARAF
>> 4.2.0. Tried Standard and minimal distributions too, but either way it is
>> installing pax-web features.
>>
>> Karaf Version is : 4.2
>>
>> pax-web-core | 7.0.0 | | Started
>> | org.ops4j.pax.web-7.0.0 | Provide Core pax-web bundles
>> pax-jetty | 9.4.6.v20170531 | | Started
>> | org.ops4j.pax.web-7.0.0 | Provide Jetty engine support
>> pax-jetty-http2 | 7.0.0 | | Uninstalled
>> | org.ops4j.pax.web-7.0.0 | Optional additional feature to run
>> Jetty with SPDY
>> pax-http-jetty | 7.0.0 | | Started
>> | org.ops4j.pax.web-7.0.0 |
>> pax-http | 7.0.0 | | Started
>> | org.ops4j.pax.web-7.0.0 | Implementation of the OSGI HTTP
>> Service
>> pax-http-whiteboard | 7.0.0 | | Started
>> | org.ops4j.pax.web-7.0.0 | Provide HTTP Whiteboard pattern
>> support
>> pax-war | 7.0.0 | | Started
>> | org.ops4j.pax.web-7.0.0 | Provide support of a full
>> WebContainer
>> pax-http-tomcat | 7.0.0 | | Uninstalled
>> | org.ops4j.pax.web-7.0.0 | Provide Tomcat support
>> pax-war-tomcat | 7.0.0 | | Uninstalled
>> | org.ops4j.pax.web-7.0.0 |
>> pax-jsf-support | 7.0.0 | | Uninstalled
>> | org.ops4j.pax.web-7.0.0 |
>> pax-jsf-resources-support | 7.0.0 | | Uninstalled
>> | org.ops4j.pax.web-7.0.0 | Provide sharing of resources
>> according
>> to Servlet
>> undertow | 1.4.23.Final | | Uninstalled
>> | org.ops4j.pax.web-7.0.0 |
>> pax-http-undertow | 7.0.0 | | Uninstalled
>> | org.ops4j.pax.web-7.0.0 |
>>
>>
>> is there any way to skip installing pax-web features in karaf
>> -distribution.
>>
>> Thanks
>> Sai
>>
>>
>>
>>
>>
>> --
>> Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html
>>
>
>
Re: Help to get out of pax-web from karaf distribution
Posted by Francois Papon <fr...@openobject.fr>.
Hi,
This is very interesting!
I agree that it would be a good thing but in some case, moving some
features out of Karaf mean that the owner of the librairies/framework
have to maintain the compatibility and they don't have skills or don't
have time to do it.
Projects like Aries and Pax are nice because people are already invovled
in Karaf :)
regards,
François Papon
fpapon@apache.org
Le 05/12/2018 à 15:30, Grzegorz Grzybek a écrit :
> Hello
>
> +1 That for example happened to Hibernate which (at some point) started to
> provide own features. Same for JPA.
> PAX-WEB (and other PAX projects) provide own Karaf features and it's worth
> considering to remove the inclusion of pax-web features from karaf
> enterprise features.
>
> There's no need to change terminology, simply we should avoid including
> other repos from "native" / "built in" repos.
>
> Maybe it's worth considering in Karaf 4.3.0 (Karaf 5.0.0?).
>
> regards
> Grzegorz Grzybek
>
> śr., 5 gru 2018 o 12:21 Christian Schneider <ch...@die-schneider.net>
> napisał(a):
>
>> I think this points to an interesting problem in current karaf.
>> Karaf comes with some feature repos installed and even with some features
>> installed.
>> This is very good for learning karaf but it is not good when you build and
>> maintain your application.
>>
>> Things that we currently make hard to do:
>> - You have an application that is based on karaf features as well as other
>> features. It is quite hard to update your application to a new karaf as it
>> brings a lot of feature updates that you might not want.
>> - Switch some implementations. For Sai wanted to not install pax web. In my
>> recent case I wanted to update blueprint core.
>>
>> I think many of these problems come from the way karaf features are
>> offered:
>> - Many features are versioned together with karaf. So when you update karaf
>> you get new versions of the features / bundles even if you do not want
>> them.
>> - Some karaf features combine too many unrelated things. E.g the enterprise
>> feature repo combines jpa, jms, peristence providers. Sometimes even
>> different versions of these.
>>
>> I think we can fix a lot of this by moving as many features as possible to
>> the projects where the bundles come from. E.g Aries jpa already provides a
>> features. This allows to use any karaf version and install any jpa version
>> on it. Unfortunately this does not work in practice as the feature needs
>> transactions as well as blueprint that are part of karaf itself.
>>
>> So I think we should move more features out of karaf and into the
>> individual projects.
>> Of course we must give these repos nice aliases so they are still easy to
>> install.
>>
>> WDYT?
>>
>> Christian
>>
>>
>> Am Mi., 5. Dez. 2018 um 11:41 Uhr schrieb Sai Sankar <
>> saisankar.c@motivitylabs.com>:
>>
>>> Hi All
>>>
>>> I dont want Pax-web features to be installed or installable with KARAF
>>> 4.2.0. Tried Standard and minimal distributions too, but either way it is
>>> installing pax-web features.
>>>
>>> Karaf Version is : 4.2
>>>
>>> pax-web-core | 7.0.0 | | Started
>>> | org.ops4j.pax.web-7.0.0 | Provide Core pax-web bundles
>>> pax-jetty | 9.4.6.v20170531 | | Started
>>> | org.ops4j.pax.web-7.0.0 | Provide Jetty engine support
>>> pax-jetty-http2 | 7.0.0 | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 | Optional additional feature to run
>>> Jetty with SPDY
>>> pax-http-jetty | 7.0.0 | | Started
>>> | org.ops4j.pax.web-7.0.0 |
>>> pax-http | 7.0.0 | | Started
>>> | org.ops4j.pax.web-7.0.0 | Implementation of the OSGI HTTP
>>> Service
>>> pax-http-whiteboard | 7.0.0 | | Started
>>> | org.ops4j.pax.web-7.0.0 | Provide HTTP Whiteboard pattern
>>> support
>>> pax-war | 7.0.0 | | Started
>>> | org.ops4j.pax.web-7.0.0 | Provide support of a full
>>> WebContainer
>>> pax-http-tomcat | 7.0.0 | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 | Provide Tomcat support
>>> pax-war-tomcat | 7.0.0 | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 |
>>> pax-jsf-support | 7.0.0 | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 |
>>> pax-jsf-resources-support | 7.0.0 | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 | Provide sharing of resources
>>> according
>>> to Servlet
>>> undertow | 1.4.23.Final | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 |
>>> pax-http-undertow | 7.0.0 | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 |
>>>
>>>
>>> is there any way to skip installing pax-web features in karaf
>>> -distribution.
>>>
>>> Thanks
>>> Sai
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html
>>>
>>
>> --
>> --
>> Christian Schneider
>> http://www.liquid-reality.de
>>
>> Computer Scientist
>> http://www.adobe.com
>>
Re: Help to get out of pax-web from karaf distribution
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
We can do a cleanup for Karaf 4.3.0.
However, there's reason why we have features in standard Karaf
distribution. For instance, the "official" Hibernates features repo was
not fully correct, that's why we override in Karaf.
As said in another e-mail, my proposal would be:
1. Reduce the minimal distribution to be even more light without a lot
of features repos references
2. Cleanup the standard features repos to better leverage repos provided
by third parties, assuming they are good enough.
Regards
JB
On 05/12/2018 12:30, Grzegorz Grzybek wrote:
> Hello
>
> +1 That for example happened to Hibernate which (at some point) started to
> provide own features. Same for JPA.
> PAX-WEB (and other PAX projects) provide own Karaf features and it's worth
> considering to remove the inclusion of pax-web features from karaf
> enterprise features.
>
> There's no need to change terminology, simply we should avoid including
> other repos from "native" / "built in" repos.
>
> Maybe it's worth considering in Karaf 4.3.0 (Karaf 5.0.0?).
>
> regards
> Grzegorz Grzybek
>
> śr., 5 gru 2018 o 12:21 Christian Schneider <ch...@die-schneider.net>
> napisał(a):
>
>> I think this points to an interesting problem in current karaf.
>> Karaf comes with some feature repos installed and even with some features
>> installed.
>> This is very good for learning karaf but it is not good when you build and
>> maintain your application.
>>
>> Things that we currently make hard to do:
>> - You have an application that is based on karaf features as well as other
>> features. It is quite hard to update your application to a new karaf as it
>> brings a lot of feature updates that you might not want.
>> - Switch some implementations. For Sai wanted to not install pax web. In my
>> recent case I wanted to update blueprint core.
>>
>> I think many of these problems come from the way karaf features are
>> offered:
>> - Many features are versioned together with karaf. So when you update karaf
>> you get new versions of the features / bundles even if you do not want
>> them.
>> - Some karaf features combine too many unrelated things. E.g the enterprise
>> feature repo combines jpa, jms, peristence providers. Sometimes even
>> different versions of these.
>>
>> I think we can fix a lot of this by moving as many features as possible to
>> the projects where the bundles come from. E.g Aries jpa already provides a
>> features. This allows to use any karaf version and install any jpa version
>> on it. Unfortunately this does not work in practice as the feature needs
>> transactions as well as blueprint that are part of karaf itself.
>>
>> So I think we should move more features out of karaf and into the
>> individual projects.
>> Of course we must give these repos nice aliases so they are still easy to
>> install.
>>
>> WDYT?
>>
>> Christian
>>
>>
>> Am Mi., 5. Dez. 2018 um 11:41 Uhr schrieb Sai Sankar <
>> saisankar.c@motivitylabs.com>:
>>
>>> Hi All
>>>
>>> I dont want Pax-web features to be installed or installable with KARAF
>>> 4.2.0. Tried Standard and minimal distributions too, but either way it is
>>> installing pax-web features.
>>>
>>> Karaf Version is : 4.2
>>>
>>> pax-web-core | 7.0.0 | | Started
>>> | org.ops4j.pax.web-7.0.0 | Provide Core pax-web bundles
>>> pax-jetty | 9.4.6.v20170531 | | Started
>>> | org.ops4j.pax.web-7.0.0 | Provide Jetty engine support
>>> pax-jetty-http2 | 7.0.0 | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 | Optional additional feature to run
>>> Jetty with SPDY
>>> pax-http-jetty | 7.0.0 | | Started
>>> | org.ops4j.pax.web-7.0.0 |
>>> pax-http | 7.0.0 | | Started
>>> | org.ops4j.pax.web-7.0.0 | Implementation of the OSGI HTTP
>>> Service
>>> pax-http-whiteboard | 7.0.0 | | Started
>>> | org.ops4j.pax.web-7.0.0 | Provide HTTP Whiteboard pattern
>>> support
>>> pax-war | 7.0.0 | | Started
>>> | org.ops4j.pax.web-7.0.0 | Provide support of a full
>>> WebContainer
>>> pax-http-tomcat | 7.0.0 | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 | Provide Tomcat support
>>> pax-war-tomcat | 7.0.0 | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 |
>>> pax-jsf-support | 7.0.0 | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 |
>>> pax-jsf-resources-support | 7.0.0 | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 | Provide sharing of resources
>>> according
>>> to Servlet
>>> undertow | 1.4.23.Final | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 |
>>> pax-http-undertow | 7.0.0 | |
>> Uninstalled
>>> | org.ops4j.pax.web-7.0.0 |
>>>
>>>
>>> is there any way to skip installing pax-web features in karaf
>>> -distribution.
>>>
>>> Thanks
>>> Sai
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html
>>>
>>
>>
>> --
>> --
>> Christian Schneider
>> http://www.liquid-reality.de
>>
>> Computer Scientist
>> http://www.adobe.com
>>
>
Re: Help to get out of pax-web from karaf distribution
Posted by Grzegorz Grzybek <gr...@gmail.com>.
Hello
+1 That for example happened to Hibernate which (at some point) started to
provide own features. Same for JPA.
PAX-WEB (and other PAX projects) provide own Karaf features and it's worth
considering to remove the inclusion of pax-web features from karaf
enterprise features.
There's no need to change terminology, simply we should avoid including
other repos from "native" / "built in" repos.
Maybe it's worth considering in Karaf 4.3.0 (Karaf 5.0.0?).
regards
Grzegorz Grzybek
śr., 5 gru 2018 o 12:21 Christian Schneider <ch...@die-schneider.net>
napisał(a):
> I think this points to an interesting problem in current karaf.
> Karaf comes with some feature repos installed and even with some features
> installed.
> This is very good for learning karaf but it is not good when you build and
> maintain your application.
>
> Things that we currently make hard to do:
> - You have an application that is based on karaf features as well as other
> features. It is quite hard to update your application to a new karaf as it
> brings a lot of feature updates that you might not want.
> - Switch some implementations. For Sai wanted to not install pax web. In my
> recent case I wanted to update blueprint core.
>
> I think many of these problems come from the way karaf features are
> offered:
> - Many features are versioned together with karaf. So when you update karaf
> you get new versions of the features / bundles even if you do not want
> them.
> - Some karaf features combine too many unrelated things. E.g the enterprise
> feature repo combines jpa, jms, peristence providers. Sometimes even
> different versions of these.
>
> I think we can fix a lot of this by moving as many features as possible to
> the projects where the bundles come from. E.g Aries jpa already provides a
> features. This allows to use any karaf version and install any jpa version
> on it. Unfortunately this does not work in practice as the feature needs
> transactions as well as blueprint that are part of karaf itself.
>
> So I think we should move more features out of karaf and into the
> individual projects.
> Of course we must give these repos nice aliases so they are still easy to
> install.
>
> WDYT?
>
> Christian
>
>
> Am Mi., 5. Dez. 2018 um 11:41 Uhr schrieb Sai Sankar <
> saisankar.c@motivitylabs.com>:
>
> > Hi All
> >
> > I dont want Pax-web features to be installed or installable with KARAF
> > 4.2.0. Tried Standard and minimal distributions too, but either way it is
> > installing pax-web features.
> >
> > Karaf Version is : 4.2
> >
> > pax-web-core | 7.0.0 | | Started
> > | org.ops4j.pax.web-7.0.0 | Provide Core pax-web bundles
> > pax-jetty | 9.4.6.v20170531 | | Started
> > | org.ops4j.pax.web-7.0.0 | Provide Jetty engine support
> > pax-jetty-http2 | 7.0.0 | |
> Uninstalled
> > | org.ops4j.pax.web-7.0.0 | Optional additional feature to run
> > Jetty with SPDY
> > pax-http-jetty | 7.0.0 | | Started
> > | org.ops4j.pax.web-7.0.0 |
> > pax-http | 7.0.0 | | Started
> > | org.ops4j.pax.web-7.0.0 | Implementation of the OSGI HTTP
> > Service
> > pax-http-whiteboard | 7.0.0 | | Started
> > | org.ops4j.pax.web-7.0.0 | Provide HTTP Whiteboard pattern
> > support
> > pax-war | 7.0.0 | | Started
> > | org.ops4j.pax.web-7.0.0 | Provide support of a full
> > WebContainer
> > pax-http-tomcat | 7.0.0 | |
> Uninstalled
> > | org.ops4j.pax.web-7.0.0 | Provide Tomcat support
> > pax-war-tomcat | 7.0.0 | |
> Uninstalled
> > | org.ops4j.pax.web-7.0.0 |
> > pax-jsf-support | 7.0.0 | |
> Uninstalled
> > | org.ops4j.pax.web-7.0.0 |
> > pax-jsf-resources-support | 7.0.0 | |
> Uninstalled
> > | org.ops4j.pax.web-7.0.0 | Provide sharing of resources
> > according
> > to Servlet
> > undertow | 1.4.23.Final | |
> Uninstalled
> > | org.ops4j.pax.web-7.0.0 |
> > pax-http-undertow | 7.0.0 | |
> Uninstalled
> > | org.ops4j.pax.web-7.0.0 |
> >
> >
> > is there any way to skip installing pax-web features in karaf
> > -distribution.
> >
> > Thanks
> > Sai
> >
> >
> >
> >
> >
> > --
> > Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html
> >
>
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Computer Scientist
> http://www.adobe.com
>
Re: Help to get out of pax-web from karaf distribution
Posted by Christian Schneider <ch...@die-schneider.net>.
I think this points to an interesting problem in current karaf.
Karaf comes with some feature repos installed and even with some features
installed.
This is very good for learning karaf but it is not good when you build and
maintain your application.
Things that we currently make hard to do:
- You have an application that is based on karaf features as well as other
features. It is quite hard to update your application to a new karaf as it
brings a lot of feature updates that you might not want.
- Switch some implementations. For Sai wanted to not install pax web. In my
recent case I wanted to update blueprint core.
I think many of these problems come from the way karaf features are offered:
- Many features are versioned together with karaf. So when you update karaf
you get new versions of the features / bundles even if you do not want them.
- Some karaf features combine too many unrelated things. E.g the enterprise
feature repo combines jpa, jms, peristence providers. Sometimes even
different versions of these.
I think we can fix a lot of this by moving as many features as possible to
the projects where the bundles come from. E.g Aries jpa already provides a
features. This allows to use any karaf version and install any jpa version
on it. Unfortunately this does not work in practice as the feature needs
transactions as well as blueprint that are part of karaf itself.
So I think we should move more features out of karaf and into the
individual projects.
Of course we must give these repos nice aliases so they are still easy to
install.
WDYT?
Christian
Am Mi., 5. Dez. 2018 um 11:41 Uhr schrieb Sai Sankar <
saisankar.c@motivitylabs.com>:
> Hi All
>
> I dont want Pax-web features to be installed or installable with KARAF
> 4.2.0. Tried Standard and minimal distributions too, but either way it is
> installing pax-web features.
>
> Karaf Version is : 4.2
>
> pax-web-core | 7.0.0 | | Started
> | org.ops4j.pax.web-7.0.0 | Provide Core pax-web bundles
> pax-jetty | 9.4.6.v20170531 | | Started
> | org.ops4j.pax.web-7.0.0 | Provide Jetty engine support
> pax-jetty-http2 | 7.0.0 | | Uninstalled
> | org.ops4j.pax.web-7.0.0 | Optional additional feature to run
> Jetty with SPDY
> pax-http-jetty | 7.0.0 | | Started
> | org.ops4j.pax.web-7.0.0 |
> pax-http | 7.0.0 | | Started
> | org.ops4j.pax.web-7.0.0 | Implementation of the OSGI HTTP
> Service
> pax-http-whiteboard | 7.0.0 | | Started
> | org.ops4j.pax.web-7.0.0 | Provide HTTP Whiteboard pattern
> support
> pax-war | 7.0.0 | | Started
> | org.ops4j.pax.web-7.0.0 | Provide support of a full
> WebContainer
> pax-http-tomcat | 7.0.0 | | Uninstalled
> | org.ops4j.pax.web-7.0.0 | Provide Tomcat support
> pax-war-tomcat | 7.0.0 | | Uninstalled
> | org.ops4j.pax.web-7.0.0 |
> pax-jsf-support | 7.0.0 | | Uninstalled
> | org.ops4j.pax.web-7.0.0 |
> pax-jsf-resources-support | 7.0.0 | | Uninstalled
> | org.ops4j.pax.web-7.0.0 | Provide sharing of resources
> according
> to Servlet
> undertow | 1.4.23.Final | | Uninstalled
> | org.ops4j.pax.web-7.0.0 |
> pax-http-undertow | 7.0.0 | | Uninstalled
> | org.ops4j.pax.web-7.0.0 |
>
>
> is there any way to skip installing pax-web features in karaf
> -distribution.
>
> Thanks
> Sai
>
>
>
>
>
> --
> Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html
>
--
--
Christian Schneider
http://www.liquid-reality.de
Computer Scientist
http://www.adobe.com