MetadataGeneratorUtil doesn't support custom output folder locations

[rnveach]

MetadataGeneratorUtil doesn't allow any user configuration for where to place the meta files it generates. As such they go to the base src\main\resources folder, and doesn't allow a custom location like checkstyle has at src\main\resources\com\puppycrawl\tools\checkstyle\meta.

In addition, it doesn't allow any configuration to keep XML files separated into different folders like checkstyle has with meta\checks\annotation and meta\checks\blocks as an example.

We should expand this util to be just as configurable as checkstyle allows for itself.

See

checkstyle/src/main/java/com/puppycrawl/tools/checkstyle/meta/XmlMetaWriter.java

Lines 160 to 178 in 13481f2

	if (moduleDetails.getFullQualifiedName().startsWith("com.puppycrawl.tools.checkstyle")) {
	final String moduleFilePath = FILEPATH_CONVERSION
	.matcher(moduleDetails.getFullQualifiedName())
	.replaceAll(fileSeparator);
	final String checkstyleString = "checkstyle";
	final int indexOfCheckstyle =
	moduleFilePath.indexOf(checkstyleString) + checkstyleString.length();
	modifiedPath = rootOutputPath + DEFAULT_FILE_SEPARATOR
	+ moduleFilePath.substring(0, indexOfCheckstyle) + "/meta/"
	+ moduleFilePath.substring(indexOfCheckstyle + 1) + xmlExtension;
	}
	else {
	String moduleName = moduleDetails.getName();
	if (moduleDetails.getModuleType() == ModuleType.CHECK) {
	moduleName += "Check";
	}
	modifiedPath = rootOutputPath + "/checkstylemeta-" + moduleName + xmlExtension;
	}

as the targeted code which give checkstyle the extra functions others don't get.

The 2nd argument can be used for the output location, just like the first argument is for the input location. We may have to switch MetadataGeneratorUtil to picocli for it to take optional arguments.