Community
Participate
Working Groups
refactor -> rename on a package the text field will catch most invalid package names, such as ending with whitespace, or whitespace in the middle of an identifier, etc, but choose to rename to: "package. subpackage" with the space after the "." and it will allow you to continue the refactoring, only to get an 'unexpected exception' dialog during the refactoring process.
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.