<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:48:27 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>[YANGIDE-14] yangide p2 update site for Eclipse installation of yangide plugins (permanent, continously integrated)</title>
                <link>https://jira.opendaylight.org/browse/YANGIDE-14</link>
                <project id="10187" key="YANGIDE">yangide</project>
                    <description>&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;I&amp;#39;m not sure if this should be in Bugzilla project infrautils, integration, releng or yangide?&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;Following the resolution of &lt;a href=&quot;https://jira.opendaylight.org/browse/YANGIDE-1&quot; title=&quot;java.lang.LinkageError: org/antlr/v4/runtime/TokenStream&quot; class=&quot;issue-link&quot; data-issue-key=&quot;YANGIDE-1&quot;&gt;&lt;del&gt;YANGIDE-1&lt;/del&gt;&lt;/a&gt; and &lt;a href=&quot;https://jira.opendaylight.org/browse/YANGIDE-10&quot; title=&quot;java.lang.ClassNotFoundException: org.opendaylight.yangtools.yang2sources.plugin.YangToSourcesProcessor$YangProvider at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;YANGIDE-10&quot;&gt;YANGIDE-10&lt;/a&gt; I&apos;m now interested in bundling yangide as part of &lt;a href=&quot;https://github.com/vorburger/opendaylight-eclipse-setup&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/vorburger/opendaylight-eclipse-setup&lt;/a&gt;.  I believe it would be quite valuable to the ODL developers community to have a nice YANG editor in their ready-made IDE (&quot;ODL SDK&quot;?), and get on-save code generation on YANG model changes.&lt;/p&gt;

&lt;p&gt;This would be easy IFF I knew the URL of where on opendaylight.org we currently host the latest continuously integrated p2 site to distribute yangide?&lt;/p&gt;

&lt;p&gt;Preferably this URL should be a fairly &quot;stable&quot; one, which doesn&apos;t keep changing, and one that will always hold the &quot;latest&quot; version of yangide (so I&apos;d ideally like it NOT to have a 1.1.1-SNAPSHOT or so in the URL), so that the IDE would be able to continuously auto-update from there.&lt;/p&gt;

&lt;p&gt;Personally I also don&apos;t care for &quot;history&quot; on this p2 site - if it always simply holds the latest build yangide plugins &amp;amp; features, for me that&apos;s just fine, IMHO.&lt;/p&gt;

&lt;p&gt;p2 sites have a compositeContent.xml &amp;amp; compositeArtifacts.xml at the root. One could use it for a manual Eclipse Help &amp;gt; Install New Software Add Location - although I&apos;ll fully integrate it into opendaylight-eclipse-setup, no manually installation will be needed.&lt;/p&gt;

&lt;p&gt;If we do not yet have this (HTTP web host a p2 site that is the result of the yangide repository update-site build result), let us use this bug to discuss how to this and make it available ASAP!&lt;/p&gt;

&lt;p&gt;I&apos;ve found &lt;a href=&quot;https://nexus.opendaylight.org/service/local/repositories/opendaylight.snapshot/content/org/opendaylight/yangide/org.opendaylight.yangide.update-site/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://nexus.opendaylight.org/service/local/repositories/opendaylight.snapshot/content/org/opendaylight/yangide/org.opendaylight.yangide.update-site/&lt;/a&gt; which Jenkins pushes the plugins to, but don&apos;t see yet how to use this directly - you cannot directly install from there, can you?  You would need Nexus to serve the contents of (the latest version of) the built yangide/product/update-site/target/org.opendaylight.yangide.update-site-*.zip ... I vaguely recall Nexus having built-in features/extra plugins to be able to do this, and am hoping someone knows exactly how to set this up.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="27233">YANGIDE-14</key>
            <summary>yangide p2 update site for Eclipse installation of yangide plugins (permanent, continously integrated)</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</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="zxiiro">Thanh Ha (zxiiro)</assignee>
                                    <reporter username="vorburger">Michael Vorburger</reporter>
                        <labels>
                    </labels>
                <created>Tue, 10 May 2016 13:05:09 +0000</created>
                <updated>Mon, 4 Nov 2019 14:08:05 +0000</updated>
                            <resolved>Mon, 4 Nov 2019 14:08:05 +0000</resolved>
                                    <version>unspecified</version>
                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="54974" author="vorburger" created="Tue, 10 May 2016 13:06:21 +0000"  >&lt;p&gt;David in email has pointed me to &lt;a href=&quot;https://nexus.opendaylight.org/content/sites/p2repos/org.opendaylight.yangide/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://nexus.opendaylight.org/content/sites/p2repos/org.opendaylight.yangide/&lt;/a&gt;, but right now that contains artifacts last built on Apr 22, so is not continuously integrated.  How can we get it to?&lt;/p&gt;</comment>
                            <comment id="54975" author="vorburger" created="Thu, 2 Jun 2016 13:11:14 +0000"  >&lt;p&gt;&lt;a href=&quot;https://lists.opendaylight.org/pipermail/dev/2016-May/002043.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://lists.opendaylight.org/pipermail/dev/2016-May/002043.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/39132/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/39132/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://nexus.opendaylight.org/content/sites/p2repos/org.opendaylight.yangide/snapshot/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://nexus.opendaylight.org/content/sites/p2repos/org.opendaylight.yangide/snapshot/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="54976" author="vorburger" created="Thu, 2 Jun 2016 13:55:31 +0000"  >&lt;p&gt;&lt;a href=&quot;https://lists.opendaylight.org/pipermail/dev/2016-June/002111.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://lists.opendaylight.org/pipermail/dev/2016-June/002111.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/vorburger/Docker/tree/master/yangide-jenkins&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/vorburger/Docker/tree/master/yangide-jenkins&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://209.132.179.72&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://209.132.179.72&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/vorburger/opendaylight-eclipse-setup/commit/bf67b1fc8f760ca89777e3b924b6f7eec1759a71&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/vorburger/opendaylight-eclipse-setup/commit/bf67b1fc8f760ca89777e3b924b6f7eec1759a71&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="67346" author="zxiiro" created="Mon, 4 Nov 2019 14:08:05 +0000"  >&lt;p&gt;Considering YANG IDE is no longer an activate project we can close this out.&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_10207" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>External References</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/39132/&quot;&gt;https://git.opendaylight.org/gerrit/#/c/39132/&lt;/a&gt;</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5869</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=5869]]></customfieldvalue>

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

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