1) create new compiler type, this create compiler type with name "Internal Compiler", but this should create compiler with "Internal Compiler (2)" name.
try to delete one of the internal compilers, this disable Internal  Compilation folder
2) sometimes when you try create New Compiler throw exception (in attachment)

[jglick] See below for basic problem. But several other bugs in other places too. #5887 is probably related (cf. Services.InstanceLevel).

--> RELATED BUGS: See "Work around" pane, I did not have space.


--> ORIGINAL PROBLEM: ...loaders.java.gj.JavaCompilerType must not override hashCode + equals; this is what breaks the ServicesNode and God knows what else (or so I think!), since the new instance was
 considered equal to the original. But the change where these two were added said it was for the compilerGroupKey, so perhaps they cannot be simply removed: JavaCompiler (internal) seems to want the c
ompiler type to be used as a key, which means some sort of comparisons. Maybe the methods can be removed anyway? This would mean that if the user had two internal compilers configured the same way, fi
le A with the first compiler and file B with the second, and compiled A + B together, there would be two compiler groups. Is this a problem? The external compiler type seems to work quite differently
as far as this goes.