sharedlib config has a dependency on rmi-naming. If a configuration that depends on sharedlib is to be deployed using offline deployer (see
GERONIMO-3544), the required changes will result in rmi-naming config getting started during deployment which will result in bind exception while using multiple server instances. See GERONIMO-3481. Since sharedlib only requires ServerInfo gbean which is part of j2ee-system config, it shouldn't harm making the sharedlib depend on j2ee-system instead of rmi-naming.