<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:54:39 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>[YANGTOOLS-910] RFC7950Reactors.defaultReactor can not build the yang file with content &quot;yang-version 1.0&quot;</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-910</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;In my project, I&apos;m trying to parse the yang files with yangtools parser, and RFC7950Reactors.defaultReactor is chosen as below:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;&lt;em&gt;CrossSourceStatementReactor.BuildAction reactor = RFC7950Reactors.defaultReactor().newBuild();&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;addSourceFiles(reactor, compatibleDir);&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;SchemaContext&lt;/em&gt;&#160;schemaContext= reactor.buildEffective();&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Then I test the yang files in&#160;compatibleDir, if the yang file is specified with &quot;yang-version 1.0&quot;, I&apos;ll get the Exception below:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;org.opendaylight.yangtools.yang.parser.spi.meta.SomeModifiersUnresolvedException: Some of FULL_DECLARATION modifiers for statements were not resolved.&lt;br/&gt;
 org.opendaylight.yangtools.yang.parser.stmt.reactor.BuildGlobalContext.propagateException(BuildGlobalContext.java:256)&lt;br/&gt;
 org.opendaylight.yangtools.yang.parser.stmt.reactor.BuildGlobalContext.loadPhaseStatementsFor(BuildGlobalContext.java:310)&lt;br/&gt;
 org.opendaylight.yangtools.yang.parser.stmt.reactor.BuildGlobalContext.loadPhaseStatements(BuildGlobalContext.java:300)&lt;br/&gt;
 org.opendaylight.yangtools.yang.parser.stmt.reactor.BuildGlobalContext.executePhases(BuildGlobalContext.java:218)&lt;br/&gt;
 org.opendaylight.yangtools.yang.parser.stmt.reactor.BuildGlobalContext.buildEffective(BuildGlobalContext.java:230)&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;And if I remove the content &quot;yang-version 1.0&quot; or replace it with &quot;yang-version 1.1&quot;, I&apos;ll get the yang file parsed correctly, no exceptions occured.&lt;/p&gt;

&lt;p&gt;Can anyone help with the issue I encountered.Thacks.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment></environment>
        <key id="30899">YANGTOOLS-910</key>
            <summary>RFC7950Reactors.defaultReactor can not build the yang file with content &quot;yang-version 1.0&quot;</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</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="10001">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="Leo29">Liu Hui</reporter>
                        <labels>
                    </labels>
                <created>Wed, 17 Oct 2018 02:44:34 +0000</created>
                <updated>Wed, 17 Oct 2018 06:43:54 +0000</updated>
                            <resolved>Wed, 17 Oct 2018 05:14:00 +0000</resolved>
                                    <version>2.1.2</version>
                                                    <component>parser</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="65363" author="rovarga" created="Wed, 17 Oct 2018 05:14:00 +0000"  >&lt;p&gt;&quot;1.0&quot; is not a valid yang-version string, as per &lt;a href=&quot;https://tools.ietf.org/html/rfc6020#section-7.1.2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://tools.ietf.org/html/rfc6020#section-7.1.2&lt;/a&gt; and &lt;a href=&quot;https://tools.ietf.org/html/rfc7950#section-7.1.2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://tools.ietf.org/html/rfc7950#section-7.1.2&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="65365" author="leo29" created="Wed, 17 Oct 2018 06:29:27 +0000"  >&lt;p&gt;Thank you&#160;&lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=rovarga&quot; class=&quot;user-hover&quot; rel=&quot;rovarga&quot;&gt;rovarga&lt;/a&gt;, I changed &quot;yang-version 1.0&quot; to &quot;yang-version 1&quot; &#65292; same exception occured, we have some yang files contains the string &quot;yang-version 1&quot;&#160; , how to avoid this exception?&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="65366" author="rovarga" created="Wed, 17 Oct 2018 06:35:35 +0000"  >&lt;p&gt;I cannot diagnose this without a full stack trace, including the cause stack. Given the problem disappears with YANG 1.1, I assume the model is using a YANG 1.1-only construct.&lt;/p&gt;</comment>
                            <comment id="65367" author="leo29" created="Wed, 17 Oct 2018 06:43:54 +0000"  >&lt;p&gt;Thanks &lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=rovarga&quot; class=&quot;user-hover&quot; rel=&quot;rovarga&quot;&gt;rovarga&lt;/a&gt;, Maybe you&apos;re right, I&apos;ll test those files later.&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|i03jpb:</customfieldvalue>

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