Summary: | 'refactor rename' allows subpackage name to start with a space. | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Chris McLaren <csmclaren> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | akiezun |
Version: | 2.0 | ||
Target Milestone: | 2.1 M3 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Chris McLaren
2002-07-26 11:05:18 EDT
JavaConventions bug The problem is not a bug in the JavaConventions. It is possible to have a package name like: package test. test1; This should result in a test.test1 package name. So the creation of the folder is incorrect. But such a name with whitespaces could be theorically passed as a package name. Not sure we should support it at the API level... unless all our APIs taking qualified names did behave in the same way. Need to investigate and make a move to be consistent (if necessary). Now tolerate to create a package fragment handle with spaces in its name. These spaces are removed right away. Verified. |