Fix site (#1578)

It freaks out on `<p>`, while javadoc freaks out on `<p/>`.

Author: cstamas

maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/filter/GroupIdRemoteRepositoryFilterSource.java

@@ -83,17 +83,14 @@ public final class GroupIdRemoteRepositoryFilterSource extends RemoteRepositoryF
     /**
      * Configuration to enable the GroupId filter (enabled by default). Can be fine-tuned per repository using
      * repository ID suffixes.
-     * <p>
      * <strong>Important:</strong> For this filter to take effect, you must provide configuration files. Without
      * configuration files, the enabled filter remains dormant and does not interfere with resolution.
-     * <p>
      * <strong>Configuration Files:</strong>
      * <ul>
      * <li>Location: Directory specified by {@link #CONFIG_PROP_BASEDIR} (defaults to {@code $LOCAL_REPO/.remoteRepositoryFilters})</li>
      * <li>Naming: {@code groupId-$(repository.id).txt}</li>
      * <li>Content: One groupId per line to allow/block from the repository</li>
      * </ul>
-     * <p>
      * <strong>Recommended Setup (Per-Project):</strong>
      * Use project-specific configuration to avoid repository ID clashes. Add to {@code .mvn/maven.config}:
      * <pre>

maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/filter/PrefixesRemoteRepositoryFilterSource.java

@@ -87,19 +87,15 @@ public final class PrefixesRemoteRepositoryFilterSource extends RemoteRepository
     /**
      * Configuration to enable the Prefixes filter (enabled by default). Can be fine-tuned per repository using
      * repository ID suffixes.
-     * <p>
      * <strong>Important:</strong> For this filter to take effect, configuration files must be available. Without
      * configuration files, the enabled filter remains dormant and does not interfere with resolution.
-     * <p>
      * <strong>Configuration File Resolution:</strong>
      * <ol>
      * <li><strong>User-provided files:</strong> Checked first from directory specified by {@link #CONFIG_PROP_BASEDIR}
      *     (defaults to {@code $LOCAL_REPO/.remoteRepositoryFilters})</li>
      * <li><strong>Auto-discovery:</strong> If not found, attempts to download from remote repository and cache locally</li>
      * </ol>
-     * <p>
      * <strong>File Naming:</strong> {@code prefixes-$(repository.id).txt}
-     * <p>
      * <strong>Recommended Setup (Auto-Discovery with Override Capability):</strong>
      * Start with auto-discovery, but prepare for project-specific overrides. Add to {@code .mvn/maven.config}:
      * <pre>
@@ -109,7 +105,6 @@ public final class PrefixesRemoteRepositoryFilterSource extends RemoteRepository
      * <strong>Initial setup:</strong> Don't provide any files - rely on auto-discovery as repositories are accessed.
      * <strong>Override when needed:</strong> Create {@code prefixes-myrepoId.txt} files in {@code .mvn/rrf/} and
      * commit to version control.
-     * <p>
      * <strong>Caching:</strong> Auto-discovered prefix files are cached in the local repository with unique IDs
      * (using {@link RepositoryIdHelper#remoteRepositoryUniqueId(RemoteRepository)}) to prevent conflicts that
      * could cause build failures.

src/site/markdown/configuration.md

@@ -97,10 +97,10 @@ To modify this file, edit the template and regenerate.
 | `"aether.priority.<class>"` | `Float` | The priority to use for a certain extension class. <code>&lt;class&gt;</code> can either be the fully qualified name or the simple name of a class. If the class name ends with Factory that suffix could optionally be left out. This configuration is used by <code>org.eclipse.aether.internal.impl.PrioritizedComponents</code> internal utility to sort classes by priority. This is reusable utility (so an extension can make use of it), but by default in "vanilla" Resolver following classes are sorted: <ul> <li> <code>org.eclipse.aether.spi.localrepo.LocalRepositoryManagerFactory</code> </li> <li> <code>org.eclipse.aether.spi.connector.RepositoryConnectorFactory</code> </li> <li> <code>org.eclipse.aether.spi.connector.layout.RepositoryLayoutFactory</code> </li> <li> <code>org.eclipse.aether.spi.connector.transport.TransporterFactory</code> </li> <li> <code>org.eclipse.aether.spi.artifact.decorator.ArtifactDecoratorFactory</code> </li> <li> <code>org.eclipse.aether.spi.artifact.generator.ArtifactGeneratorFactory</code> </li> <li> <code>org.eclipse.aether.impl.MetadataGeneratorFactory</code> </li> </ul> |  -  |  |  No  | Session Configuration |
 | `"aether.priority.cached"` | `Boolean` | A flag indicating whether the created ordered components should be cached in session. |  `true`  | 2.0.0 |  No  | Session Configuration |
 | `"aether.priority.implicit"` | `Boolean` | A flag indicating whether the priorities of pluggable extensions are implicitly given by their iteration order such that the first extension has the highest priority. If set, an extension's built-in priority as well as any corresponding <code>aether.priority.*</code> configuration properties are ignored when searching for a suitable implementation among the available extensions. This priority mode is meant for cases where the application will present/inject extensions in the desired search order. |  `false`  |  |  No  | Session Configuration |
-| `"aether.remoteRepositoryFilter.groupId"` | `Boolean` | Configuration to enable the GroupId filter (enabled by default). Can be fine-tuned per repository using repository ID suffixes. <p> <strong>Important:</strong> For this filter to take effect, you must provide configuration files. Without configuration files, the enabled filter remains dormant and does not interfere with resolution. <p> <strong>Configuration Files:</strong> <ul> <li>Location: Directory specified by <code>#CONFIG_PROP_BASEDIR</code> (defaults to <code>$LOCAL_REPO/.remoteRepositoryFilters</code> )</li> <li>Naming: <code>groupId-$(repository.id).txt</code> </li> <li>Content: One groupId per line to allow/block from the repository</li> </ul> <p> <strong>Recommended Setup (Per-Project):</strong> Use project-specific configuration to avoid repository ID clashes. Add to <code>.mvn/maven.config</code> : <pre> -Daether.remoteRepositoryFilter.groupId=true -Daether.remoteRepositoryFilter.groupId.basedir=${session.rootDirectory}/.mvn/rrf/ </pre> Then create <code>groupId-myrepoId.txt</code> files in the <code>.mvn/rrf/</code> directory and commit them to version control. |  `true`  | 1.9.0 |  Yes  | Session Configuration |
+| `"aether.remoteRepositoryFilter.groupId"` | `Boolean` | Configuration to enable the GroupId filter (enabled by default). Can be fine-tuned per repository using repository ID suffixes. <strong>Important:</strong> For this filter to take effect, you must provide configuration files. Without configuration files, the enabled filter remains dormant and does not interfere with resolution. <strong>Configuration Files:</strong> <ul> <li>Location: Directory specified by <code>#CONFIG_PROP_BASEDIR</code> (defaults to <code>$LOCAL_REPO/.remoteRepositoryFilters</code> )</li> <li>Naming: <code>groupId-$(repository.id).txt</code> </li> <li>Content: One groupId per line to allow/block from the repository</li> </ul> <strong>Recommended Setup (Per-Project):</strong> Use project-specific configuration to avoid repository ID clashes. Add to <code>.mvn/maven.config</code> : <pre> -Daether.remoteRepositoryFilter.groupId=true -Daether.remoteRepositoryFilter.groupId.basedir=${session.rootDirectory}/.mvn/rrf/ </pre> Then create <code>groupId-myrepoId.txt</code> files in the <code>.mvn/rrf/</code> directory and commit them to version control. |  `true`  | 1.9.0 |  Yes  | Session Configuration |
 | `"aether.remoteRepositoryFilter.groupId.basedir"` | `String` | The basedir where to store filter files. If path is relative, it is resolved from local repository root. |  `".remoteRepositoryFilters"`  | 1.9.0 |  No  | Session Configuration |
 | `"aether.remoteRepositoryFilter.groupId.record"` | `Boolean` | Should filter go into "record" mode (and collect encountered artifacts)? |  `false`  | 1.9.0 |  No  | Session Configuration |
-| `"aether.remoteRepositoryFilter.prefixes"` | `Boolean` | Configuration to enable the Prefixes filter (enabled by default). Can be fine-tuned per repository using repository ID suffixes. <p> <strong>Important:</strong> For this filter to take effect, configuration files must be available. Without configuration files, the enabled filter remains dormant and does not interfere with resolution. <p> <strong>Configuration File Resolution:</strong> <ol> <li><strong>User-provided files:</strong> Checked first from directory specified by <code>#CONFIG_PROP_BASEDIR</code> (defaults to <code>$LOCAL_REPO/.remoteRepositoryFilters</code> )</li> <li><strong>Auto-discovery:</strong> If not found, attempts to download from remote repository and cache locally</li> </ol> <p> <strong>File Naming:</strong> <code>prefixes-$(repository.id).txt</code> <p> <strong>Recommended Setup (Auto-Discovery with Override Capability):</strong> Start with auto-discovery, but prepare for project-specific overrides. Add to <code>.mvn/maven.config</code> : <pre> -Daether.remoteRepositoryFilter.prefixes=true -Daether.remoteRepositoryFilter.prefixes.basedir=${session.rootDirectory}/.mvn/rrf/ </pre> <strong>Initial setup:</strong> Don't provide any files - rely on auto-discovery as repositories are accessed. <strong>Override when needed:</strong> Create <code>prefixes-myrepoId.txt</code> files in <code>.mvn/rrf/</code> and commit to version control. <p> <strong>Caching:</strong> Auto-discovered prefix files are cached in the local repository with unique IDs (using <code>RepositoryIdHelper#remoteRepositoryUniqueId(RemoteRepository)</code> ) to prevent conflicts that could cause build failures. |  `true`  | 1.9.0 |  Yes  | Session Configuration |
+| `"aether.remoteRepositoryFilter.prefixes"` | `Boolean` | Configuration to enable the Prefixes filter (enabled by default). Can be fine-tuned per repository using repository ID suffixes. <strong>Important:</strong> For this filter to take effect, configuration files must be available. Without configuration files, the enabled filter remains dormant and does not interfere with resolution. <strong>Configuration File Resolution:</strong> <ol> <li><strong>User-provided files:</strong> Checked first from directory specified by <code>#CONFIG_PROP_BASEDIR</code> (defaults to <code>$LOCAL_REPO/.remoteRepositoryFilters</code> )</li> <li><strong>Auto-discovery:</strong> If not found, attempts to download from remote repository and cache locally</li> </ol> <strong>File Naming:</strong> <code>prefixes-$(repository.id).txt</code> <strong>Recommended Setup (Auto-Discovery with Override Capability):</strong> Start with auto-discovery, but prepare for project-specific overrides. Add to <code>.mvn/maven.config</code> : <pre> -Daether.remoteRepositoryFilter.prefixes=true -Daether.remoteRepositoryFilter.prefixes.basedir=${session.rootDirectory}/.mvn/rrf/ </pre> <strong>Initial setup:</strong> Don't provide any files - rely on auto-discovery as repositories are accessed. <strong>Override when needed:</strong> Create <code>prefixes-myrepoId.txt</code> files in <code>.mvn/rrf/</code> and commit to version control. <strong>Caching:</strong> Auto-discovered prefix files are cached in the local repository with unique IDs (using <code>RepositoryIdHelper#remoteRepositoryUniqueId(RemoteRepository)</code> ) to prevent conflicts that could cause build failures. |  `true`  | 1.9.0 |  Yes  | Session Configuration |
 | `"aether.remoteRepositoryFilter.prefixes.basedir"` | `String` | The basedir where to store filter files. If path is relative, it is resolved from local repository root. |  `".remoteRepositoryFilters"`  | 1.9.0 |  No  | Session Configuration |
 | `"aether.snapshotFilter"` | `Boolean` | The key in the repository session's <code>RepositorySystemSession#getConfigProperties() configurationproperties</code> used to store a <code>Boolean</code> flag whether this filter should be forced to ban snapshots. By default, snapshots are only filtered if the root artifact is not a snapshot. |  `false`  |  |  No  | Session Configuration |
 | `"aether.syncContext.named.basedir.locksDir"` | `String` | The location of the directory toi use for locks. If relative path, it is resolved from the local repository root. |  `".locks"`  | 1.9.0 |  No  | Session Configuration |