Project: springxd
Issue XD-2547: Accept any file name for top level module resources
Expecting in module configuration is brittle, especially in conjunction with module upload command which permits the module to be registered under a different name. The convention should be dropped in favor of any file name. This requires at most one foo.xml, foo.groovy, and/or foo.properties in the top level config folder. It is an exception if multiples are found. Accepting any file name provides the most flexibility without sacrificing backward compatibility (except in rare cases in which a module developer may have violated the multiple xml or properties files condition). An alternate approach requiring a well known file name such as 'spring-module' were rejected over concerns that it would break any existing custom module implementations.
Story points: 3