<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:27:40 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-117] nexus.opendaylight.org to proxy an external SNAPSHOT Maven repo, for lastnpe.org EEA</title>
                <link>https://jira.opendaylight.org/browse/ODLPARENT-117</link>
                <project id="10149" key="ODLPARENT">odlparent</project>
                    <description>&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;I&amp;#39;m not sure which project to file this issue under; it&amp;#39;s really linuxfoundation.org infrastructure related, not &amp;quot;odlparent&amp;quot; (code) specific... is this more of a helpdesk@ than a BZ kinda thing?  Or can we have a LF JIRA about this instead of this BZ?&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;In the context of &lt;a href=&quot;https://jira.opendaylight.org/browse/ODLPARENT-116&quot; title=&quot;Use lastnpe.org stuff to help avoiding the infamous NullPointerException in OpenDaylight code&quot; class=&quot;issue-link&quot; data-issue-key=&quot;ODLPARENT-116&quot;&gt;ODLPARENT-116&lt;/a&gt; for ODL to be able to use the external null annotations (EEA; see e.g. &lt;a href=&quot;http://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Ftasks%2Ftask-using_external_null_annotations.htm&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Ftasks%2Ftask-using_external_null_annotations.htm&lt;/a&gt;) coming together from the &lt;a href=&quot;http://lastnpe.org&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://lastnpe.org&lt;/a&gt; in the build of some ODL projects, I would have to frequently cut releases of &lt;a href=&quot;https://github.com/lastnpe/eclipse-null-eea-augments/tree/master/libraries&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/lastnpe/eclipse-null-eea-augments/tree/master/libraries&lt;/a&gt; and often deploy to Maven central (as I have on &lt;a href=&quot;https://repo1.maven.org/maven2/org/lastnpe/eea/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://repo1.maven.org/maven2/org/lastnpe/eea/&lt;/a&gt;, once).&lt;/p&gt;

&lt;p&gt;However, this is likely going to be a major PITA, especially in the early days and during ongoing dev cycles (it will be different as the EEA repo becomes more mature later, and when we cut ODL releases with it later as well).&lt;/p&gt;

&lt;p&gt;Therefore, in an ideal world it would be neat if &lt;a href=&quot;http://nexus.opendaylight.org&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://nexus.opendaylight.org&lt;/a&gt; could proxy some (TBD) external Maven repo where I would continuously deploy (CD, e.g. using travis-ci.org) SNAPSHOT EEA JARs to from &lt;a href=&quot;https://github.com/lastnpe/eclipse-null-eea-augments/tree/master/libraries&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/lastnpe/eclipse-null-eea-augments/tree/master/libraries&lt;/a&gt; (e.g. on Bintray.com, or wherever).&lt;/p&gt;

&lt;p&gt;Requires &lt;a href=&quot;https://github.com/lastnpe/eclipse-null-eea-augments/issues/14&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/lastnpe/eclipse-null-eea-augments/issues/14&lt;/a&gt;&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="22240">ODLPARENT-117</key>
            <summary>nexus.opendaylight.org to proxy an external SNAPSHOT Maven repo, for lastnpe.org EEA</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <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="10001">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="vorburger">Michael Vorburger</reporter>
                        <labels>
                    </labels>
                <created>Fri, 15 Sep 2017 12:51:08 +0000</created>
                <updated>Wed, 24 Jan 2018 14:26:41 +0000</updated>
                            <resolved>Tue, 19 Sep 2017 13:48:22 +0000</resolved>
                                    <version>2.0.5</version>
                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="42077" author="skitt@redhat.com" created="Fri, 15 Sep 2017 16:38:04 +0000"  >&lt;p&gt;Umm... Can&apos;t you use local EEAs to work things out before pushing them upstream and releasing?&lt;/p&gt;</comment>
                            <comment id="42078" author="vorburger" created="Sat, 16 Sep 2017 02:38:33 +0000"  >&lt;p&gt;&amp;gt; use local EEAs to work things out before pushing them upstream and releasing?&lt;/p&gt;

&lt;p&gt;Yeah of course that will work (once it&apos;s all set up correctly; working on that...) for local development, BUT:&lt;/p&gt;

&lt;p&gt;Once (later..) I&apos;ll want to start enforcing null safety in the build (opt in),&lt;/p&gt;

&lt;p&gt;when I refine some EEA for something being coded in a Gerrit,&lt;/p&gt;

&lt;p&gt;that EEA change will have to go &quot;live&quot;, so the build of projects who opted in to enforcement doesn&apos;t break.&lt;/p&gt;

&lt;p&gt;In an ideal world, especially in the early days, this would avoid having to having to release EEA updates as releases to Central all too frequently.&lt;/p&gt;</comment>
                            <comment id="42079" author="rovarga" created="Sun, 17 Sep 2017 10:06:15 +0000"  >&lt;p&gt;I really dislike us depending on third-party snapshots &amp;#8211; that really is bringing our release flexibility down.&lt;/p&gt;

&lt;p&gt;Why is stabilizing upstream first and then pulling it into ODL not a feasible approach?&lt;/p&gt;</comment>
                            <comment id="42080" author="skitt@redhat.com" created="Mon, 18 Sep 2017 08:02:37 +0000"  >&lt;p&gt;(In reply to Michael Vorburger from comment #2)&lt;br/&gt;
&amp;gt; Once (later..) I&apos;ll want to start enforcing null safety in the build (opt&lt;br/&gt;
&amp;gt; in),&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; when I refine some EEA for something being coded in a Gerrit,&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; that EEA change will have to go &quot;live&quot;, so the build of projects who opted&lt;br/&gt;
&amp;gt; in to enforcement doesn&apos;t break.&lt;/p&gt;

&lt;p&gt;So how&apos;s that going to work for general users of EEA, other than ODL? Will everyone be expected to use snapshots? It seems to me the EEA project needs to figure out some way of allowing null-checks with local supplements to cover such cases, instead of relying on changes flowing upstream at the same rate as downstream development.&lt;/p&gt;</comment>
                            <comment id="42081" author="vorburger" created="Tue, 19 Sep 2017 12:56:26 +0000"  >&lt;p&gt;&lt;a href=&quot;https://lists.opendaylight.org/pipermail/odlparent-dev/2017-September/001340.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://lists.opendaylight.org/pipermail/odlparent-dev/2017-September/001340.html&lt;/a&gt; has concluded that is not something which OpenDaylight will want to do.&lt;/p&gt;

&lt;p&gt;If needed, the best alternative I can think of is to either release lastnpe.org EEA very frequently to central, or to have SNAPSHOT EEA in ODL, e.g. in infrautils, as a sort of &quot;incubator&quot; while waiting for lastnpe.org to release say monthly to Maven central.  I&apos;ll probably start to do the latter as and when the need to have this arises.&lt;/p&gt;

&lt;p&gt;Therefore closing this issue.&lt;/p&gt;</comment>
                            <comment id="42082" author="vorburger" created="Tue, 19 Sep 2017 13:48:22 +0000"  >&lt;p&gt;&amp;gt; Why is stabilizing upstream first and then pulling it into ODL not a feasible approach?&lt;/p&gt;

&lt;p&gt;Just for velocity.  I would likely have to very frequently cut releases of lastnpe/eclipse-null-eea-augments and often deploy to Maven central.&lt;/p&gt;

&lt;p&gt;&amp;gt; So how&apos;s that going to work for general users of EEA, other than ODL? Will everyone be expected to use snapshots? &lt;/p&gt;

&lt;p&gt;Nope, just those who want the very latest bleeding edge.  As for any library.&lt;/p&gt;

&lt;p&gt;&amp;gt; It seems to me the EEA project needs to figure out some way of allowing null-checks with local supplements to cover such cases, instead of relying on changes flowing upstream at the same rate as downstream development.&lt;/p&gt;

&lt;p&gt;Forget about EEA... thanks to my &lt;a href=&quot;https://github.com/lastnpe/eclipse-external-annotations-m2e-plugin&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/lastnpe/eclipse-external-annotations-m2e-plugin&lt;/a&gt; it&apos;s actually EXACTLY the same as for any Maven dependency to any library, or whatever.  I had actually worked (hard, last year) to even make &quot;workspace resolution&quot; possible - works very nicely.  The only problem then is builds.&lt;/p&gt;

&lt;p&gt;PS: But I would rather not sink time in further debating this.  I think what I&apos;ll do is offer a first suggested contribution to odlparent based on which whoever is interested in this work can use EEA-based null analysis in Eclipse IDE and with a -P mvn CLI profile for local builds - only.  I want to get some experience with that.  Optional opt-in regular (Jenkins, not local -P) build time enforcement is then a later step.  As only that would really require this, I would like to pause this discussion until then.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="22239">ODLPARENT-116</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_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9170</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=9170]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i023ev:</customfieldvalue>

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