You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by ol...@apache.org on 2023/03/10 04:23:57 UTC
[maven-site] branch master updated: update section title (#394)
This is an automated email from the ASF dual-hosted git repository.
olamy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new d7cc8cec update section title (#394)
d7cc8cec is described below
commit d7cc8cecbbaae0001be09f3bb95571ca8eeb8b38
Author: Olivier Lamy <ol...@apache.org>
AuthorDate: Fri Mar 10 14:23:50 2023 +1000
update section title (#394)
---
content/markdown/guides/mini/guide-resolver-transport.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/markdown/guides/mini/guide-resolver-transport.md b/content/markdown/guides/mini/guide-resolver-transport.md
index 2381cb15..fa49c31c 100644
--- a/content/markdown/guides/mini/guide-resolver-transport.md
+++ b/content/markdown/guides/mini/guide-resolver-transport.md
@@ -85,7 +85,7 @@ If your build environment uses Wagon specific configuration (in `settings.xml` o
configuration first. You can still upgrade and use latest Maven, with use `-Dmaven.resolver.transport=wagon` user property
to stick with Wagon, but migration to new transport is warmly recommended.
-## The Devil Is In Details
+## Per Transport configuration details
Depending on which transport you use (`native`, `wagon` or something else), you will want to refer to the corresponding
page(s) for detailed configuration options: