OpenDaylight JIRA

OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us

8.20.10

820010

22-06-2022

[MDSAL-185] Java binding v1: Invalid file/directory names for Windows in JAR https://jira.opendaylight.org/browse/MDSAL-185 mdsal <p>Some innocuous identifiers can lead to maven-bundle-plugin refusing to create the final jar file.</p> <p>For example:</p> <p>container con {<br/> }</p> <p>Leads to:</p> <p><span class="error">[ERROR]</span> Bundle <...> : Invalid file/directory names for Windows in JAR: <span class="error">[<...>]</span>. You can set the regular expression used with -invalidfilenames, the default expression is CON(\..<ins>)?|PRN(\..</ins>)?|AUX(\..<ins>)?|CLOCK\$|NUL(\..</ins>)?|COM<span class="error">[1-9]</span>(\..<ins>)?|LPT<span class="error">[1-9]</span>(\..</ins>)?|\$Mft|\$MftMirr|\$LogFile|\$Volume|\$AttrDef|\$Bitmap|\$Boot|\$BadClus|\$Secure|\$Upcase|\$Extend|\$Quota|\$ObjId|\$Reparse<br/> <span class="error">[ERROR]</span> Error(s) found in bundle configuration</p> <p>It should be possible to use a less restrictive pattern (after verifying it on Windows).</p> <p>Operating System: All<br/> Platform: All</p> MDSAL-185

Java binding v1: Invalid file/directory names for Windows in JAR

Bug Resolved Won't Do Unassigned Vratko Polak Thu, 7 Jul 2016 13:28:28 +0000 Fri, 9 Mar 2018 18:00:16 +0000 Fri, 10 Mar 2017 11:56:47 +0000 0 4 <p>Complete example module: <a href="https://git.opendaylight.org/gerrit/41483" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/41483</a></p> <p>A less obvious example: <a href="https://git.opendaylight.org/gerrit/41485" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/41485</a></p> <p> container in-con-troll {<br/> container foo </p> { presence "bar"; } <p> }</p> <p>Foo gets compiled into (...)/in/con/troll/Foo.class which contains the prohibited "con".</p> <p>looks like OSGi limitation:</p> <p><a href="http://bnd.bndtools.org/instructions/invalidfilenames.html" class="external-link" target="_blank" rel="nofollow noopener">http://bnd.bndtools.org/instructions/invalidfilenames.html</a></p> <p>Actually, this is a Windows limitation, where it resolves some names to devices – irrespective in which context that name is used.</p> <p><a href="https://ionicflux.wordpress.com/2006/09/02/windows-reserved-words/" class="external-link" target="_blank" rel="nofollow noopener">https://ionicflux.wordpress.com/2006/09/02/windows-reserved-words/</a></p> <p>CON, PRN, AUX, CLOCK$, NUL, COM0, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT0, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9</p> <p>this is a simple addition to existing patch in Binding spec v2<br/> <a href="https://git.opendaylight.org/gerrit/#/c/52007/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/52007/</a></p> <p>so let's fix it in new bug and leave this one connected to v1 as it was</p> Blocks MDSAL-233 MDSAL-40 Development External issue ID 6172 External issue URL Issue Type Rank 0|i02wu7: