You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2019/04/29 20:48:56 UTC

[maven-studies] branch maven-extension-demo updated: second s_mvn/extensions.xml_.mvn/extensions.xml_

This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a commit to branch maven-extension-demo
in repository https://gitbox.apache.org/repos/asf/maven-studies.git


The following commit(s) were added to refs/heads/maven-extension-demo by this push:
     new 5a2c84b  second s_mvn/extensions.xml_.mvn/extensions.xml_
5a2c84b is described below

commit 5a2c84b0c7908dfcdd84b250f7de932d906bc815
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Mon Apr 29 22:48:52 2019 +0200

    second s_mvn/extensions.xml_.mvn/extensions.xml_
---
 src/site/apt/index.apt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/site/apt/index.apt b/src/site/apt/index.apt
index c773275..aace08c 100644
--- a/src/site/apt/index.apt
+++ b/src/site/apt/index.apt
@@ -62,7 +62,7 @@ Maven Extension Demo Study
   <<<-Dmaven.ext.class.path=[path to files]>>> is a little bit more flexible, but remains not configured into
   the build, which is not suitable to ensure an extension is available at build time.
 
-  <<<mvn/extensions.xml>>> is the ultimate solution for these use cases. Its only drawback is that it has been
+  <<<.mvn/extensions.xml>>> is the ultimate solution for these use cases. Its only drawback is that it has been
   added only in Maven 3.3.1.