[MDSAL-233] Java Binding v2: Invalid file/directory names for Windows in JAR Created: 21/Feb/17 Updated: 09/Mar/18 Resolved: 10/Mar/17 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Martin Ciglan | Assignee: | Jakub Toth |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||||||
| External issue ID: | 7834 | ||||||||||||
| Description |
|
+++ This bug was initially created as a clone of Some innocuous identifiers can lead to maven-bundle-plugin refusing to create the final jar file. For example: container con { Leads to: [ERROR] Bundle <...> : Invalid file/directory names for Windows in JAR: [<...>]. You can set the regular expression used with -invalidfilenames, the default expression is CON(\..)?|PRN(\..)?|AUX(\..)?|CLOCK\$|NUL(\..)?|COM[1-9](\..)?|LPT[1-9](\..)?|\$Mft|\$MftMirr|\$LogFile|\$Volume|\$AttrDef|\$Bitmap|\$Boot|\$BadClus|\$Secure|\$Upcase|\$Extend|\$Quota|\$ObjId|\$Reparse It should be possible to use a less restrictive pattern (after verifying it on Windows). |
| Comments |
| Comment by Martin Ciglan [ 23/Feb/17 ] |
|
patch as a part of identifier handling utility: https://git.opendaylight.org/gerrit/#/c/52007/ work in progress |
| Comment by Jakub Toth [ 27/Feb/17 ] |