This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | no reverse engineering output if uml project name contains :: or ( or ) | ||
---|---|---|---|
Product: | uml | Reporter: | stadelma <stadelma> |
Component: | Reverse Engineering | Assignee: | issues@uml <issues> |
Status: | STARTED --- | ||
Severity: | normal | CC: | hmichel |
Priority: | P3 | Keywords: | UI, USABILITY |
Version: | 7.0 | ||
Hardware: | PC | ||
OS: | Windows Vista | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | the log file of NB 6.9.1 for the reported UML error |
Description
stadelma
2010-11-22 16:00:48 UTC
Created attachment 103194 [details]
the log file of NB 6.9.1 for the reported UML error
The empty project has nothing to do with the name of the project. See issue #171788. About the name issue that seems to be a Maven integration issue as UML uses the project name reported by the project. Changing to Maven for review. No clue what "the name issue" is. If you have steps to reproduce some problem that do not involve UML, let me know. The issue was the :: in the Maven Name. I have a fix replacing :: with -. Is that acceptable? Or should just strip the first part (i.e. Doxia :: APT Module to APT Module) What are your thoughts? Just a note, if you are asking Jesse, it' unlikely if he is in issues@uml list and also he is not in cc. Can't say regarding issue if it will work it may be ok as it's better then exception anyway. With regards to fixing names containing '::' I think I would prefer a single ':' rather than changing to '-', seems to keep things a little more consistent. But, if single ':' are bad too, then a hyphen will do. I definitely prefer either of these two options over stripping the whole first section off (in this case 'Doxia ::'). Although it may make sense in this instance, it would be hard to predict what 'effect' this will have in another context. Consider if this project had been named "Maven Plugin (maven-plugin) :: Doxia" instead. Perhaps a less likely scenario, but by no means impossible. That's my thoughts anyway. -David Have you tested it against 7.0 daily builds? IF I am not wrong some changes was made about project names and maybe it could be already fixed (or not). I just can't found the issue about it to make sure if it is related or not. Thanks Michael, I'll give it a try with 7.0 Beta platform. I tried with build 201011280001 with this results: Here the project was already opened (from previous IDE shutdown): SEVERE: Cannot create folder Doxia :: Logging API-c593aeb7 in Z:\Netbeans\community-uml\build\testuserdir\config (Z:\Netbeans\community-uml\build\testuserdir\config\Projects\extra\Doxia :: Logging API-c593aeb7). SEVERE: Cannot create folder Doxia :: Logging API-c593aeb7 in Z:\Netbeans\community-uml\build\testuserdir\config (Z:\Netbeans\community-uml\build\testuserdir\config\Projects\extra\Doxia :: Logging API-c593aeb7). SEVERE: Cannot create folder Doxia :: Logging API-c593aeb7 in Z:\Netbeans\community-uml\build\testuserdir\config (Z:\Netbeans\community-uml\build\testuserdir\config\Projects\extra\Doxia :: Logging API-c593aeb7). SEVERE: Cannot create folder Doxia :: Logging API-c593aeb7 in Z:\Netbeans\community-uml\build\testuserdir\config (Z:\Netbeans\community-uml\build\testuserdir\config\Projects\extra\Doxia :: Logging API-c593aeb7). SEVERE: Cannot create folder Doxia :: Logging API-c593aeb7 in Z:\Netbeans\community-uml\build\testuserdir\config (Z:\Netbeans\community-uml\build\testuserdir\config\Projects\extra\Doxia :: Logging API-c593aeb7). Closing and reopening caused the mentioned error anyway. |