reformat table

[elharo]

No description provided.

[gnodet]

-1

This code is generated afaik:

maven/apache-maven/pom.xml

Lines 271 to 302 in d80804c

	<plugin>
	<groupId>org.codehaus.mojo</groupId>
	<artifactId>exec-maven-plugin</artifactId>
	<version>3.5.0</version>
	<executions>
	<execution>
	<id>render-configuration-page</id>
	<goals>
	<goal>java</goal>
	</goals>
	<phase>verify</phase>
	<configuration>
	<classpathScope>test</classpathScope>
	<additionalClasspathElements>
	<additionalClasspathElement>${basedir}/src/test/resources</additionalClasspathElement>
	</additionalClasspathElements>
	<mainClass>org.eclipse.aether.tools.CollectConfiguration</mainClass>
	<arguments>
	<argument>--mode=maven</argument>
	<!--
	TODO: templates are loaded from classpath, in "normal" JAR project local template would override docgen one,
	but in this case the packaging=pom all I could do is use additionalClasspathElement that APPENDS classpath,
	hence template is renamed to maven-configuration.md.vm, to avoid conflict (and picking up resolver template)
	-->
	<argument>--templates=maven-configuration.md,configuration.properties,configuration.yaml</argument>
	<argument>${basedir}/..</argument>
	<argument>${basedir}/../src/site/markdown/</argument>
	</arguments>
	</configuration>
	</execution>
	</executions>
	</plugin>

The templates are actually embedded in the corresponding resolver jar.

[michael-o]

This file should contain an appropriate header for auto-generation

[gnodet]

apache/maven-resolver#691