[jira] [Commented] (KARAF-4347) Define scr feature as featureBoot in standard distribution
[ https://issues.apache.org/jira/browse/KARAF-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15170565#comment-15170565 ] Vladimir Konkov commented on KARAF-4347: +1 Guillaume Nodet : we should remove blueprint from default featureBoot. Karaf is very universal container in contrast with JEE servers like GlassFish and JBoss (witch is also OSGI enabled). And to stay so it should provide minimum preinstalled runtime components. It is trivial to install needed feature, there is 3 approaches at minimum: 1. Install it as dependency for your business feature 2. Change featureBoot setting before first start (it is easy with automation) 3. Build your own assembly with needed boot features and local artifact repo for it. We are successfully using all this approaches for our projects. But to there is only one option to remove feature from default featureBoot - change config before boot. Even preinstalled blueprint can cause troubles (what if we needed Gemini impl of blueprint ?). > Define scr feature as featureBoot in standard distribution > -- > > Key: KARAF-4347 > URL: https://issues.apache.org/jira/browse/KARAF-4347 > Project: Karaf > Issue Type: Improvement > Components: karaf-core, karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.5 > > > As more and more people use DS/SCR, it's not always obvious to them that they > need to install the scr feature. As blueprint programming model is installed > by default, and regarding the very low overhead of scr feature, it would make > sense to install scr at boot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4347) Define scr feature as featureBoot in standard distribution
[ https://issues.apache.org/jira/browse/KARAF-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158716#comment-15158716 ] Guillaume Nodet commented on KARAF-4347: I'm not really sure we should install more optional features by default. I'd rather go into the opposite direction and remove some optional features for 4.1 such as blueprint, etc... The reason is that when features should reference the SCR feature or extender and so those parts should be installed automatically. Another possible way to ease the user pain would be to define "default" optional features, i.e. some features which would be automatically installed "on demand". So blueprint and scr would not be installed by default, but if they are needed by a feature, they could be installed automatically. The danger would be to start making all features this way, which would then severely limit the amount of control the user has when actually installing features. > Define scr feature as featureBoot in standard distribution > -- > > Key: KARAF-4347 > URL: https://issues.apache.org/jira/browse/KARAF-4347 > Project: Karaf > Issue Type: Improvement > Components: karaf-core, karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.5 > > > As more and more people use DS/SCR, it's not always obvious to them that they > need to install the scr feature. As blueprint programming model is installed > by default, and regarding the very low overhead of scr feature, it would make > sense to install scr at boot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
