https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/ODLPARENT-227 odlparent <p>Downstream projects are using OSGi DS (a.k.a. Service Component Runtime), which they depend on easily be depending on Karaf's "scr" feature. Unfortunately this results in rewiring of pax-logging, hence SFTs end up missing a chunk of their logs.</p> <p>Promote OSGi DS to being equal to Blueprint and always load it. It is much better for OSGi than Blueprint anyway.</p> ODLPARENT-227

Add SCR to default karaf profile

Improvement Medium Resolved Done Robert Varga Robert Varga Thu, 27 Feb 2020 16:39:10 +0000 Tue, 3 Mar 2020 19:12:27 +0000 Tue, 3 Mar 2020 19:12:27 +0000 7.0.0 Karaf SFT 0 1 <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=skitt" class="user-hover" rel="skitt">skitt</a>  so I tried manipulating bootFeatures/startupFeatures, which are supposed to automate this, but no dice, neither file is affected when built with karaf4-parent.</p> <p>The thing is, the fact this does not work seems to be leading to all that configuration around exclusions and maintaining startup.properties – note how our snippet from karaf-resources:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> # The following are added by opendaylight-karaf-resources mvn\:org.osgi/org.osgi.service.event/1.3.1 = 7 mvn\:org.apache.felix/org.apache.felix.metatype/1.2.2 = 8 mvn\:org.opendaylight.odlparent/bcprov-framework-ext/${project.version} = 14 mvn\:org.opendaylight.odlparent/bcpkix-framework-ext/${project.version} = 14 mvn\:org.apache.aries.blueprint/org.apache.aries.blueprint.core.compatibility/1.0.0 = 14 </pre> </div></div> <p>pretty much matches what we want to express in:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> &lt;dependency&gt; &lt;groupId&gt;org.apache.aries.quiesce&lt;/groupId&gt; &lt;artifactId&gt;org.apache.aries.quiesce.api&lt;/artifactId&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.osgi&lt;/groupId&gt; &lt;!-- <span class="code-keyword">for</span> https:<span class="code-comment">//bugs.opendaylight.org/show_bug.cgi?id=4290 --&gt; </span> &lt;artifactId&gt;org.osgi.service.event&lt;/artifactId&gt; &lt;/dependency&gt; [...] &lt;dependency&gt; &lt;groupId&gt;org.opendaylight.odlparent&lt;/groupId&gt; &lt;artifactId&gt;bcpkix-framework-ext&lt;/artifactId&gt; &lt;scope&gt;runtime&lt;/scope&gt; &lt;/dependency&gt; </pre> </div></div> <p>which plus the guidelines to various exclusions such as:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> &lt;excludedArtifactId&gt;org.apache.aries.quiesce.api&lt;/excludedArtifactId&gt; </pre> </div></div> <p>seem to point all over the place <img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/sad.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>I think the startup.properties thing needs to <b>definitely</b> be generated by karaf4-parent – blueprint.core.compatibility matches aries-blueprint in standard-*-features.xml.</p> <p>My question is: any idea on how to do this correctly?</p> <p>Also, <a href="https://svn.apache.org/repos/asf/karaf/site/production/manual/latest/custom-distribution.html" class="external-link" target="_blank" rel="nofollow noopener">https://svn.apache.org/repos/asf/karaf/site/production/manual/latest/custom-distribution.html</a> would lead me to believe if this worked correctly, populate-local-repo would just be a before-step to generate a well-known feature, which has dependencies on all the right features-{project}/individual features and then declaring:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> &lt;installedFeature&gt;${project.groupId}-${project.artifactId}-everything&lt;/installedFeature&gt; </pre> </div></div> <p>and then karaf-maven-plugin would do the rest of the copying based on:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>&lt;installedFeature&gt;baz&lt;/installedFeature&gt; - This will result in all the bundles in the feature being installed in the "system" internal repository. Therefore at runtime the feature may be installed without access to external repositories. You can use feature_name or feature_name/feature_version formats.</pre> </div></div> <p>or are we missing recursiveness?</p> Development Rank 0|i03r87: