<!-- 
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-265] Do not declare depends-maven-plugin in odlparent</title>
                <link>https://jira.opendaylight.org/browse/ODLPARENT-265</link>
                <project id="10149" key="ODLPARENT">odlparent</project>
                    <description>&lt;p&gt;This declaration is only used in SFT as far as I can tell. The plugin is quite dead upstream to the point of not having been updated for parallel builds (&lt;a href=&quot;https://jira.opendaylight.org/browse/ODLPARENT-264&quot; title=&quot;Fix thread safety around depends-maven-plugin&quot; class=&quot;issue-link&quot; data-issue-key=&quot;ODLPARENT-264&quot;&gt;ODLPARENT-264&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;Remove its declaration from odlparent/pom.xml, so downstreams are not tempted to use it.&lt;/p&gt;

&lt;p&gt;There are a few downstream users:&lt;/p&gt;

&lt;p&gt;&#160;&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;ovsdb/southbound/southbound-it/pom.xml
ovsdb/hwvtepsouthbound/hwvtepsouthbound-it/pom.xml
controller/opendaylight/md-sal/mdsal-it-parent/pom.xml
infrautils/itestutils/parent/pom.xml
infrautils/caches/sample/it/pom.xml&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;all of which seems to point towards the need for better pax-exam integration.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment></environment>
        <key id="34499">ODLPARENT-265</key>
            <summary>Do not declare depends-maven-plugin in odlparent</summary>
                <type id="10101" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10318&amp;avatarType=issuetype">Task</type>
                                            <priority id="2" iconUrl="https://jira.opendaylight.org/images/icons/priorities/critical.svg">High</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:19:01 +0000</created>
                <updated>Tue, 30 May 2023 09:12:25 +0000</updated>
                                                            <fixVersion>14.0.0</fixVersion>
                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="69650" author="rovarga" created="Wed, 29 Sep 2021 12:19:20 +0000"  >&lt;p&gt;If we solve &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; correctly, then all the IT users should be easy to convert:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;create a test @Component(immediate=true)&lt;/li&gt;
	&lt;li&gt;put test logic into the @Activate method, returning from it only all tests have passed (or throw a failure)&lt;/li&gt;
	&lt;li&gt;package the component into a feature&lt;/li&gt;
	&lt;li&gt;run SFT on the feature&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;This way SFT deals with all the container setup and execution, without the test needing to know anything about execution environment &#8211; which is way better than anything Pax-Exam-based can provide.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="34498">ODLPARENT-264</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </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|i03zun:</customfieldvalue>

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