<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:28:04 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[ODLPARENT-264] Fix thread safety around depends-maven-plugin</title>
                <link>https://jira.opendaylight.org/browse/ODLPARENT-264</link>
                <project id="10149" key="ODLPARENT">odlparent</project>
                    <description>&lt;p&gt;We are getting this splat during parallel -Pq build:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;[INFO] -----------&amp;lt; org.opendaylight.odlparent:features-odlparent &amp;gt;------------
[INFO] Building ODL :: odlparent :: features-odlparent 9.0.7-SNAPSHOT &#160;&#160;[61/63]
[INFO] ------------------------------[ feature ]-------------------------------
[WARNING] *****************************************************************
[WARNING] * Your build is requesting parallel execution, but project &#160;&#160;&#160;&#160;&#160;*
[WARNING] * contains the following plugin(s) that have goals not marked &#160;&#160;*
[WARNING] * as @threadSafe to support parallel building. &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;*
[WARNING] * While this /may/ work fine, please look for plugin updates &#160;&#160;&#160;*
[WARNING] * and/or request plugins be made thread-safe. &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;*
[WARNING] * If reporting an issue, report it against the plugin in &#160;&#160;&#160;&#160;&#160;&#160;&#160;*
[WARNING] * question, not against maven-core &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;*
[WARNING] *****************************************************************
[WARNING] The following plugins are not marked @threadSafe in ODL :: odlparent :: features-odlparent:
[WARNING] org.apache.servicemix.tooling:depends-maven-plugin:1.4.0
[WARNING] Enable debug to see more precisely which goals are not marked @threadSafe.
[WARNING] *****************************************************************

&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Unfortunately &lt;a href=&quot;https://github.com/apache/servicemix-maven-plugins&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/apache/servicemix-maven-plugins&lt;/a&gt; seems to be quite dead, so we may need to rework the integration completely.&lt;/p&gt;</description>
                <environment></environment>
        <key id="34498">ODLPARENT-264</key>
            <summary>Fix thread safety around depends-maven-plugin</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <status id="10003" iconUrl="https://jira.opendaylight.org/images/icons/status_generic.gif" description="">Confirmed</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                            <label>pt</label>
                    </labels>
                <created>Wed, 29 Sep 2021 10:10:02 +0000</created>
                <updated>Tue, 26 Dec 2023 17:34:00 +0000</updated>
                                                            <fixVersion>14.0.0</fixVersion>
                    <fixVersion>13.0.11</fixVersion>
                                    <component>SFT</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="69646" author="rovarga" created="Wed, 29 Sep 2021 10:19:26 +0000"  >&lt;p&gt;So this affects only SFT, hence may end up being a duplicate of &lt;a href=&quot;https://jira.opendaylight.org/browse/ODLPARENT-262&quot; title=&quot;SingleFeatureTest needs to be safe to execute in parallel&quot; class=&quot;issue-link&quot; data-issue-key=&quot;ODLPARENT-262&quot;&gt;ODLPARENT-262&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="69647" author="rovarga" created="Wed, 29 Sep 2021 10:24:47 +0000"  >&lt;p&gt;It seems all usage of the plugin has to do with launching pax-exam from surefire. Perhaps we should provide a better alternative?&lt;/p&gt;</comment>
                            <comment id="72449" author="JIRAUSER13216" created="Wed, 16 Aug 2023 13:40:44 +0000"  >&lt;p&gt;&lt;b&gt;depends-maven-plugin&lt;/b&gt; is only used to determine current version of the SCR feature being preset for SFT.&lt;br/&gt;
in code it looks like below (SingleFeatureTest#227)&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
&lt;span class=&quot;code-comment&quot;&gt;// Install SCR
&lt;/span&gt;features(maven().groupId(&lt;span class=&quot;code-quote&quot;&gt;&quot;org.apache.karaf.features&quot;&lt;/span&gt;).artifactId(&lt;span class=&quot;code-quote&quot;&gt;&quot;standard&quot;&lt;/span&gt;).type(&lt;span class=&quot;code-quote&quot;&gt;&quot;xml&quot;&lt;/span&gt;)
    .classifier(&lt;span class=&quot;code-quote&quot;&gt;&quot;features&quot;&lt;/span&gt;).versionAsInProject(), &lt;span class=&quot;code-quote&quot;&gt;&quot;scr&quot;&lt;/span&gt;), &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;the &lt;b&gt;versionAsInProject()&lt;/b&gt; is a pax-exam logic which relies on data from file &lt;br/&gt;
target/classes/META-INF/maven/&lt;b&gt;dependencies.properties&lt;/b&gt; generated by depends-maven-plugin&lt;/p&gt;

&lt;p&gt;in order to rid of dependency on this plugin we just need to provide the version directly&lt;br/&gt;
with no invocation of versionAsInProject(). the simple substitution for gaining information about &lt;br/&gt;
dependencies could be &lt;b&gt;maven-dependency-plugin:list&lt;/b&gt; configured for execution on pre-test stage&lt;br/&gt;
(test-compile) with output to a file which then can be parsed by test logic.&lt;/p&gt;

&lt;p&gt;this is being proposed as apart of solution for &lt;a href=&quot;https://jira.opendaylight.org/browse/ODLPARENT-257&quot; title=&quot;Allow SFT to use a test-only dependency&quot; class=&quot;issue-link&quot; data-issue-key=&quot;ODLPARENT-257&quot;&gt;&lt;del&gt;ODLPARENT-257&lt;/del&gt;&lt;/a&gt;&#160;&lt;br/&gt;
see &lt;a href=&quot;https://git.opendaylight.org/gerrit/c/odlparent/+/106844/3/abstract-feature-parent/pom.xml#87&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/c/odlparent/+/106844/3/abstract-feature-parent/pom.xml#87&lt;/a&gt;&lt;br/&gt;
it makes sense to handle scr feature preset same way as test dependencies&lt;/p&gt;

&lt;p&gt;in further perspectives (if SFT is implemented as maven plugin) then dependencies can be handled internally&lt;/p&gt;</comment>
                            <comment id="72534" author="rovarga" created="Sun, 10 Sep 2023 16:58:01 +0000"  >&lt;p&gt;SFT spawns karaf instances, which may access network ports and similar, hence &lt;a href=&quot;https://jira.opendaylight.org/browse/ODLPARENT-262&quot; title=&quot;SingleFeatureTest needs to be safe to execute in parallel&quot; class=&quot;issue-link&quot; data-issue-key=&quot;ODLPARENT-262&quot;&gt;ODLPARENT-262&lt;/a&gt; will introduce better wiring with maven, e.g. we can resolve these dependencies.&lt;/p&gt;

&lt;p&gt;That will render depends-maven-plugin obsolete.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="34485">ODLPARENT-262</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="34499">ODLPARENT-265</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10002" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>ODLPARENT-261</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03zuf:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>