<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:54:55 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-1009] Emit YangModuleInfo packaging from yang-maven-plugin</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-1009</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;org.opendaylight.yangtools.yang.binding.YangModuleInfo (as present in md-sal&apos;s yang-binding) artifact really belongs to yangtools, or at least yangtools needs an equivalent.&lt;/p&gt;

&lt;p&gt;This will allow us to package models in a runtime-discoverable way, without generating MD-SAL binding interfaces out of it. It also provides a Java foothold, which is good enough to extract packaged model&apos;s sources while also making sure dependencies are satisfied.&lt;/p&gt;

&lt;p&gt;This will allow us to package models and their parser support in centralized bundles, which md-sal can later enrich externally with corresponding Java bindings (or any other bindings, really).&lt;/p&gt;

&lt;p&gt;The MD-SAL version also links to imported modules, which creates a strong package-level binding between revisions.&lt;/p&gt;

&lt;p&gt;We do not want our version to do that &#8211; it should only expose the main module (and its submodules) and metadata about them. Any dependencies will be resolved through parsing anyway.&lt;/p&gt;

&lt;p&gt;We also should provide a utility wrapper, which will turn each such YangModuleInfo into a set of model.repo.api.YangTextSchemaSources &#8211; which can then be fed into a parser reactor.&lt;/p&gt;</description>
                <environment></environment>
        <key id="31772">YANGTOOLS-1009</key>
            <summary>Emit YangModuleInfo packaging from yang-maven-plugin</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="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>
                    </labels>
                <created>Wed, 3 Jul 2019 23:49:51 +0000</created>
                <updated>Tue, 19 Sep 2023 16:20:20 +0000</updated>
                                                            <fixVersion>14.0.0</fixVersion>
                                    <component>maven plugin</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="66957" author="rovarga" created="Wed, 3 Jul 2019 23:54:27 +0000"  >&lt;p&gt;A package name string pointing to the YangModuleInfo should be exported for each local module, so that MD-SAL binding generator can point to these when generating its implementation (which additionally has inter-revision ties).&lt;/p&gt;

&lt;p&gt;Also, this packaging has implications on parser extensions, as these should package the models separately, so as not to pollute model packaging with yang.model.api dependencies.&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|i03obz:</customfieldvalue>

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