While doing a merge for a "renamed" package, I made the mistake of moving a class properties file (with the category set to the old package name) into the new package and when filetree creates the class in the other category, the class is effectively moved to a different package ... since the category pretty much needs to stay in sync with the package, I think an error should be thrown if a class is loaded whose category is not consistent with the package that the class resides within ...
While doing a merge for a "renamed" package, I made the mistake of moving a class properties file (with the category set to the old package name) into the new package and when filetree creates the class in the other category, the class is effectively moved to a different package ... since the category pretty much needs to stay in sync with the package, I think an error should be thrown if a class is loaded whose category is not consistent with the package that the class resides within ...