This is an automated email from the ASF dual-hosted git repository. elharo pushed a commit to branch elharo-patch-1 in repository https://gitbox.apache.org/repos/asf/maven-resolver.git
commit 78fb7dcc8eeb5f6970a3152d2b5efa82be6c6ffd Author: Elliotte Rusty Harold <elh...@users.noreply.github.com> AuthorDate: Sat Nov 16 02:18:39 2024 +0000 Update to 1.9.22 --- src/site/markdown/using-resolver-in-maven-plugins.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/site/markdown/using-resolver-in-maven-plugins.md b/src/site/markdown/using-resolver-in-maven-plugins.md index 7c254464..a6eda28f 100644 --- a/src/site/markdown/using-resolver-in-maven-plugins.md +++ b/src/site/markdown/using-resolver-in-maven-plugins.md @@ -36,14 +36,14 @@ POM: <!-- required in all cases --> <groupId>org.apache.maven.resolver</groupId> <artifactId>maven-resolver-api</artifactId> - <version>1.9.20</version> + <version>1.9.22</version> <scope>provided</scope> </dependency> <dependency> <!-- optional helpers, might be superfluous depending on your use case --> <groupId>org.apache.maven.resolver</groupId> <artifactId>maven-resolver-util</artifactId> - <version>1.9.20</version> + <version>1.9.22</version> <!-- Scope: use compile to make plugin work in Maven 3.8 and earlier --> <scope>compile</scope> </dependency> @@ -58,7 +58,7 @@ enforced by the Maven core, just like other Maven APIs. So be sure to compile/test your plugin against the version of `maven-resolver-api` that is used by the minimum version of Maven that your plugin wants to support. -Next, in your mojo source, you would need to grab the repository related +Next, in your mojo source, you need to grab the repository related components and parameters: ```java @@ -71,7 +71,7 @@ public class MyMojo extends AbstractMojo { /** - * The entry point to resolver (fka. Aether), i.e. the component doing all the work. + * The entry point to resolver (a.k.a. Aether), i.e. the component doing all the work. */ @Component private RepositorySystem repoSystem;