<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:37:29 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>[RELENG-97] Update Maven to 3.5.3</title>
                <link>https://jira.opendaylight.org/browse/RELENG-97</link>
                <project id="10164" key="RELENG">releng</project>
                    <description>&lt;p&gt;Release notes: &lt;a href=&quot;https://maven.apache.org/docs/3.5.3/release-notes.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://maven.apache.org/docs/3.5.3/release-notes.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We need to upgrade our Maven build tooling to Maven 3.5.3. From the mailing list discussion (&lt;a href=&quot;https://lists.opendaylight.org/pipermail/release/2018-April/014799.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://lists.opendaylight.org/pipermail/release/2018-April/014799.html&lt;/a&gt;) we discovered that the off by 1 timestamp issues that hit us last release is back and hurting us with distribution check jobs... Maven 3.5.2 was patched to solve the timestamp issues so it&apos;s about time we started updating our build tooling to use it.&lt;/p&gt;

&lt;p&gt;We were hit by this before during the Nitrogen release and caused us to revert our maven-merge jobs from global-jjb back to ODL merge jobs and at the time it affected our merge jobs. It appears that our distribution-check jobs are now hitting the same issue. This time distribution-check is not a new job nor has it changed in awhile so there&apos;s nothing to revert to. It is time we upgraded our Maven builder to 3.5.3.&lt;/p&gt;</description>
                <environment></environment>
        <key id="29806">RELENG-97</key>
            <summary>Update Maven to 3.5.3</summary>
                <type id="10103" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10311&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="2" iconUrl="https://jira.opendaylight.org/images/icons/priorities/critical.svg">High</priority>
                        <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="zxiiro">Thanh Ha (zxiiro)</assignee>
                                    <reporter username="zxiiro">Thanh Ha (zxiiro)</reporter>
                        <labels>
                    </labels>
                <created>Wed, 18 Apr 2018 14:22:43 +0000</created>
                <updated>Thu, 19 Apr 2018 20:47:35 +0000</updated>
                            <resolved>Thu, 19 Apr 2018 20:47:35 +0000</resolved>
                                                                    <component>Jenkins Job Builder</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                                                                <comments>
                            <comment id="62513" author="zxiiro" created="Wed, 18 Apr 2018 14:49:50 +0000"  >&lt;p&gt;Copied Maven 3.5.3 to local Nexus server. We can start transitioning jobs to using it now.&lt;/p&gt;</comment>
                            <comment id="62517" author="zxiiro" created="Wed, 18 Apr 2018 16:46:58 +0000"  >&lt;p&gt;With the distribution-check patch merged. New job runs should be using the new Maven version now. Will monitor and see if this improves things and then look into patching the remaining jobs.&lt;/p&gt;</comment>
                            <comment id="62519" author="zxiiro" created="Wed, 18 Apr 2018 18:46:11 +0000"  >&lt;p&gt;I rechecked a bunch of jobs and they seem to have returned successfully. I think it&apos;s safe to start updating the rest of the jobs to using mvn35 now.&lt;/p&gt;</comment>
                            <comment id="62540" author="zxiiro" created="Thu, 19 Apr 2018 20:47:28 +0000"  >&lt;p&gt;Proposed a final patch to switch global-jjb jobs to using mvn35. I think this can be closed out now.&lt;/p&gt;</comment>
                    </comments>
                    <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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03dkf:</customfieldvalue>

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