As I'm looking over this stuff now, the reason why we have been having so much trouble making head way with the refactoring wizard is that, unlike the "new enum" wizard, this wizard can result in the creation of multiple enum types. That is, the refactoring groups the input constants into their minimal type dependent sets (where changing one member of the set requires refactoring all other members) and proceeds to refactor each of these sets into its own enum type. An alternative thing to do would be to group the constants into their maximal sets instead and let the user break them down. In either case, the wizard should allow the user to:
1. Merge and split the constant grouping, checking the initial preconditions each time.
2. Specify the names and packages for multiple enum types to be created.