A similar argument could be made for the jar suffixes in the JarStructure.
e.g. the SARdeployer could automatically add itself as a JARMatcher
accepting .sar extensions, etc.
Of course we should still hardwire .jar and .zip ;-)
In this case, it isn't as much of an issue of recognition since they are all jars
and the real test is whether something in META-INF/*.xml gets processed.
I say it is not an issue of recognition because everything can now be .jar
files, but there will be legacy deployments that use the old extensions
like .beans or .hibernate for subdeployments.
I can make this happen for CR1.
Integrating this with deployers tests that've already promised. ;-)
Can you create a JIRA issue?