https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/MDSAL-75 mdsal <p>Unable to generate java class file, for yang which contains these groupings:</p> <p>grouping linkstate {<br/> leaf distinguisher </p> { type route-distinguisher; } <p>}</p> <p>grouping link-state {<br/> leaf local-ipv4-router-id </p> { type ipv4-router-identifier; } <p>}</p> <p>In console output:</p> <p><span class="error">&#91;WARNING&#93;</span> Naming conflict for type 'org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.linkstate.rev150210.Linkstate': file with same name already exists and will not be generated.</p> <p>This problem occurs in Windows environment, in linux all classes were generated properly.</p> <p>Operating System: Windows<br/> Platform: PC</p> MDSAL-75

CodeGenerator unable to generate class for grouping

Bug Resolved Won't Do Unassigned Ladislav Borak Thu, 12 Mar 2015 12:48:26 +0000 Fri, 9 Mar 2018 18:00:06 +0000 Fri, 10 Mar 2017 11:56:47 +0000 0 3 <p>What filesystem was this on? It sounds like a case-sensitivity issue. For obvious reasons we do not supporte case-insensitive filesystems.</p> <p>It was tested on NTFS file system.</p> <p>Is limiting ourselves to case-sensitive filesystems a good idea? It seems like something that's likely to bite us (or more realistically a customer) at some point that could be avoided.</p> <p>The java compiler insists on public compilation units containing a matching class declaration: <a href="http://www.javaworld.com/article/2073236/java---duplicate-class--and-mismatched-file-name-error.html" class="external-link" target="_blank" rel="nofollow noopener">http://www.javaworld.com/article/2073236/java---duplicate-class--and-mismatched-file-name-error.html</a>.</p> <p>The Binding Spec is very explicit as to when camel-casing occurs, e.g. 'container foo-bar' and 'container foobar' generate 'FooBar' and 'Foobar'.</p> <p>Those two classes are not the same class in Java. If you throw in a case-insensitive filesystem, that means that two classes (FooBar and Foobar) which differ only in capitalization would map themselves to the same file &#8211; hence kaboom.</p> <p>Solving this would mean a much more involved and user-unfriendly name mapping rules, so no, I would say not supporting case-insensitive filesystems is a very reasonable trade-off.</p> Blocks MDSAL-40 Development External issue ID 2822 External issue URL Issue Type ODL SR Target Milestone Priority Rank 0|i02w5r: