You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by sl...@apache.org on 2023/02/18 20:40:15 UTC
[maven-site] 12/14: Revert "[MNGSITE-507] [DOXIA-692] Improve conversion results - part2"
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit 10d6f9d9a1985862c407950ff0830afc82aec2eb
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Sat Feb 18 21:35:01 2023 +0100
Revert "[MNGSITE-507] [DOXIA-692] Improve conversion results - part2"
This reverts commit df48f659351cff7e71f0e46fabc4617db6ac451f.
---
content/markdown/developers/committer-settings.md | 2 +-
content/markdown/faq-unoffical.md | 22 +++++++++++-----------
.../guide-testing-development-plugins.md | 2 +-
content/markdown/guides/getting-started/index.md | 18 +++++++++---------
.../getting-started/windows-prerequisites.md | 4 ++--
.../introduction-to-dependency-mechanism.md | 2 +-
.../introduction-to-plugin-prefix-mapping.md | 10 +++++-----
.../guides/introduction/introduction-to-plugins.md | 2 +-
.../introduction/introduction-to-profiles.md | 6 +++---
.../guides/introduction/introduction-to-the-pom.md | 2 +-
.../guides/mini/guide-3rd-party-jars-remote.md | 2 +-
content/markdown/guides/mini/guide-assemblies.md | 2 +-
.../markdown/guides/mini/guide-attached-tests.md | 2 +-
.../guides/mini/guide-configuring-maven.md | 4 ++--
.../guides/mini/guide-creating-archetypes.md | 2 +-
content/markdown/guides/mini/guide-encryption.md | 10 +++++-----
.../guides/mini/guide-maven-classloading.md | 8 ++++----
.../markdown/guides/mini/guide-mirror-settings.md | 2 +-
.../guides/mini/guide-multiple-repositories.md | 2 +-
content/markdown/guides/mini/guide-proxies.md | 2 +-
.../guides/mini/guide-reproducible-builds.md | 2 +-
content/markdown/guides/mini/guide-site.md | 2 +-
.../markdown/guides/mini/guide-snippet-macro.md | 2 +-
.../markdown/guides/mini/guide-using-extensions.md | 2 +-
.../markdown/guides/mini/guide-using-toolchains.md | 2 +-
.../guides/plugin/guide-java-plugin-development.md | 6 +++---
content/markdown/plugin-developers/common-bugs.md | 4 ++--
.../cookbook/plexus-plugin-upgrade.md | 2 +-
28 files changed, 64 insertions(+), 64 deletions(-)
diff --git a/content/markdown/developers/committer-settings.md b/content/markdown/developers/committer-settings.md
index d979a678..b5d3ef74 100644
--- a/content/markdown/developers/committer-settings.md
+++ b/content/markdown/developers/committer-settings.md
@@ -24,7 +24,7 @@ under the License.
## Introduction
- This document is intended to set up the Maven committer settings, i.e. the `${user.home}/.m2/settings.xml`.
+ This document is intended to set up the Maven committer settings, i.e. the `$\{user.home\}/.m2/settings.xml`.
### Enable Apache Servers
diff --git a/content/markdown/faq-unoffical.md b/content/markdown/faq-unoffical.md
index 4adb12de..b4d3f0bd 100644
--- a/content/markdown/faq-unoffical.md
+++ b/content/markdown/faq-unoffical.md
@@ -234,7 +234,7 @@ NOTE: I fixed this behavior in Maven's trunk; previously, it had been putting th
So, to recap:
parent:
-```xml
+```
<configuration>
<items>
<item>one</item>
@@ -608,8 +608,8 @@ _Plugins and Lifecycle, Sites & Reporting_
### How do I integrate static (x)html into my Maven site?
You can integrate your static pages in this several steps,
-* Put your static pages in the resources directory, ${basedir}/src/site/resources.
-* Create your site.xml and put it in `${basedir}/src/site`. An example below:
+* Put your static pages in the resources directory, $\{basedir\}/src/site/resources.
+* Create your site.xml and put it in $\{basedir\}/src/site. An example below:
```
<project name="Maven War Plugin">
<bannerLeft>
@@ -935,7 +935,7 @@ _Sites & Reporting, General_
### How do I create a command line parameter (i.e., \-Dname=value ) in my mojo?
-In your mojo, put `expression=${<exp>}` in your parameter field
+In your mojo, put `expression=$\{<exp>\}` in your parameter field
```
/**
@@ -1084,7 +1084,7 @@ To do so, simply add the following fragment to your pom:
Now, to specify a different output directory at runtime simply use the directory property as a mvn command line parameter;
{code}mvn -Ddirectory=tmp package
```
-This will send the build's output files to the ${basedir}/tmp directory.
+This will send the build's output files to the $\{basedir}/tmp directory.
_POM, Command Line_
@@ -1213,7 +1213,7 @@ _Plugins and Lifecycle, IDEs_
### What does aggregator mean in mojo?
-When a Mojo has a `@aggregator` expression, it means that It can only build the parent project of your multi-module-project, the one who has the packaging of pom. It can also give you values for the expression `${reactorProjects}` where reactorProjects are the MavenProject references to the parent pom modules.
+When a Mojo has a `@aggregator` expression, it means that It can only build the parent project of your multi-module-project, the one who has the packaging of pom. It can also give you values for the expression $\{reactorProjects\} where reactorProjects are the MavenProject references to the parent pom modules.
### Why there are no dependency properties in Maven?
@@ -1382,8 +1382,8 @@ Use the `inherited` property. Set it to `false` in the plugin configuration. So
### How can I reference windows or unix environment variables in my POM?
Starting in maven *2.0.1*, you can reference windows and unix environment variables inside your pom.xml or settings.xml using an expression of the form:
-`${env.VARNAME}`
-So, if you wanted to reference your home directory environment variable, you might use: `${env.HOME}`
+`$\{env.VARNAME\}`
+So, if you wanted to reference your home directory environment variable, you might use: `$\{env.HOME\}`
### How do I know which phase a plug-in is associated with?
@@ -1456,7 +1456,7 @@ When specifying a war as dependency, make sure that you have set the `<type>` to
### How can I change the default location of the generated jar when I command "mvn package"?
-By default, the location of the generated jar is in `${project.build.directory}` or in your target directory.
+By default, the location of the generated jar is in $\{project.build.directory\} or in your target directory.
We can change this by configuring the outputDirectory of maven-jar-plugin.
```
<plugin>
@@ -1595,7 +1595,7 @@ Note: You don't have to define the central repo (i.e. ibiblio).
### Is it possible to exclude a package from the generated jar file?
-You can configure maven-compiler-plugin to exclude your unwanted packages or files to be compiled in the first place. But you will not be able to prevent javac to compile those files if they are referenced by other packages within the source tree. To prevent that, you will need to use antrun plugin ( or write your own custom plugin), bind it to compile phase, and remove unwanted classes in `${project.build.directory}/classes`. If possible, just move those pacakges/files to another source [...]
+You can configure maven-compiler-plugin to exclude your unwanted packages or files to be compiled in the first place. But you will not be able to prevent javac to compile those files if they are referenced by other packages within the source tree. To prevent that, you will need to use antrun plugin ( or write your own custom plugin), bind it to compile phase, and remove unwanted classes in $\{project.build.directory\}/classes. If possible, just move those pacakges/files to another source [...]
### How should I point a path for Maven to use a certain version of JDK when I have different versions of JDK installed on my PC and my JAVA_HOME already set?
@@ -1770,7 +1770,7 @@ pom.xml > project scope
```
### What is reactorProjects? executedProject?
-`${reactorProjects}` are the projects that the current mvn command are going to be built. This will include the parent project and all its children while `${executedProject}` is the project where you typed your mvn command.
+$\{reactorProjects} are the projects that the current mvn command are going to be built. This will include the parent project and all its children while $\{executedProject} is the project where you typed your mvn command.
### What is a Snapshot?
diff --git a/content/markdown/guides/development/guide-testing-development-plugins.md b/content/markdown/guides/development/guide-testing-development-plugins.md
index 5dfe52be..e1b5a95e 100644
--- a/content/markdown/guides/development/guide-testing-development-plugins.md
+++ b/content/markdown/guides/development/guide-testing-development-plugins.md
@@ -103,7 +103,7 @@ under the License.
If you are using the goals from the command line on a number of projects, you should include this in your `settings.xml` file instead.
- You need to modify your `${user.home}/.m2/settings.xml` file to include two new profiles and then when you need access to the plugin snapshots use `-Papache`. The profile only needs to be enabled once so that the plugins can be downloaded into you local repository. Once in your local repository Maven can successfully resolve the dependencies and the profile no longer needs to be activated.
+ You need to modify your `$\{user.home\}/.m2/settings.xml` file to include two new profiles and then when you need access to the plugin snapshots use `-Papache`. The profile only needs to be enabled once so that the plugins can be downloaded into you local repository. Once in your local repository Maven can successfully resolve the dependencies and the profile no longer needs to be activated.
diff --git a/content/markdown/guides/getting-started/index.md b/content/markdown/guides/getting-started/index.md
index 443ed0e1..8e215169 100644
--- a/content/markdown/guides/getting-started/index.md
+++ b/content/markdown/guides/getting-started/index.md
@@ -217,7 +217,7 @@ my-app
`-- AppTest.java
```
- As you can see, the project created from the archetype has a POM, a source tree for your application's sources and a source tree for your test sources. This is the standard layout for Maven projects (the application sources reside in `${basedir}/src/main/java` and test sources reside in `${basedir}/src/test/java`, where `${basedir}` represents the directory containing `pom.xml`).
+ As you can see, the project created from the archetype has a POM, a source tree for your application's sources and a source tree for your test sources. This is the standard layout for Maven projects (the application sources reside in `$\{basedir\}/src/main/java` and test sources reside in `$\{basedir\}/src/test/java`, where $\{basedir\} represents the directory containing `pom.xml`).
If you were to create a Maven project by hand this is the directory structure that we recommend using. This is a Maven convention and to learn more about it you can read our [Introduction to the Standard Directory Layout](../introduction/introduction-to-the-standard-directory-layout.html).
@@ -267,7 +267,7 @@ mvn compile
The first time you execute this (or any other) command, Maven will need to download all the plugins and related dependencies it needs to fulfill the command. From a clean installation of Maven, this can take quite a while (in the output above, it took almost 4 minutes). If you execute the command again, Maven will now have what it needs, so it won't need to download anything new and will be able to execute the command much more quickly.
- As you can see from the output, the compiled classes were placed in `${basedir}/target/classes`, which is another standard convention employed by Maven. So, if you're a keen observer, you'll notice that by using the standard conventions, the POM above is very small and you haven't had to tell Maven explicitly where any of your sources are or where the output should go. By following the standard Maven conventions, you can get a lot done with very little effort! Just as a casual compariso [...]
+ As you can see from the output, the compiled classes were placed in `$\{basedir\}/target/classes`, which is another standard convention employed by Maven. So, if you're a keen observer, you'll notice that by using the standard conventions, the POM above is very small and you haven't had to tell Maven explicitly where any of your sources are or where the output should go. By following the standard Maven conventions, you can get a lot done with very little effort! Just as a casual compari [...]
Now, this is simply to compile a single tree of application sources and the Ant script shown is pretty much the same size as the POM shown above. But we'll see how much more we can do with just that simple POM!
@@ -367,10 +367,10 @@ mvn test
mvn package
```
- You can now take a look in the `${basedir}/target` directory and you will see the generated JAR file.
+ You can now take a look in the `$\{basedir\}/target` directory and you will see the generated JAR file.
- Now you'll want to install the artifact you've generated (the JAR file) in your local repository (`${user.home}/.m2/repository` is the default location). For more information on repositories you can refer to our [Introduction to Repositories](../introduction/introduction-to-repositories.html) but let's move on to installing our artifact! To do so execute the following command:
+ Now you'll want to install the artifact you've generated (the JAR file) in your local repository (`$\{user.home\}/.m2/repository` is the default location). For more information on repositories you can refer to our [Introduction to Repositories](../introduction/introduction-to-repositories.html) but let's move on to installing our artifact! To do so execute the following command:
@@ -541,7 +541,7 @@ mvn clean
Another common use case that can be satisfied which requires no changes to the POM that we have above is packaging resources in the JAR file. For this common task, Maven again relies on the [Standard Directory Layout](../introduction/introduction-to-the-standard-directory-layout.html), which means by using standard Maven conventions you can package resources within JARs simply by placing those resources in a standard directory structure.
- You see below in our example we have added the directory `${basedir}/src/main/resources` into which we place any resources we wish to package in our JAR. The simple rule employed by Maven is this: any directories or files placed within the `${basedir}/src/main/resources` directory are packaged in your JAR with the exact same structure starting at the base of the JAR.
+ You see below in our example we have added the directory `$\{basedir\}/src/main/resources` into which we place any resources we wish to package in our JAR. The simple rule employed by Maven is this: any directories or files placed within the `$\{basedir\}/src/main/resources` directory are packaged in your JAR with the exact same structure starting at the base of the JAR.
@@ -585,7 +585,7 @@ my-app
`-- App.class
```
- As you can see, the contents of `${basedir}/src/main/resources` can be found starting at the base of the JAR and our `application.properties` file is there in the `META-INF` directory. You will also notice some other files there like `META-INF/MANIFEST.MF` as well as a `pom.xml` and `pom.properties` file. These come standard with generation of a JAR in Maven. You can create your own manifest if you choose, but Maven will generate one by default if you don't. (You can also modify the ent [...]
+ As you can see, the contents of `$\{basedir\}/src/main/resources` can be found starting at the base of the JAR and our `application.properties` file is there in the `META-INF` directory. You will also notice some other files there like `META-INF/MANIFEST.MF` as well as a `pom.xml` and `pom.properties` file. These come standard with generation of a JAR in Maven. You can create your own manifest if you choose, but Maven will generate one by default if you don't. (You can also modify the e [...]
@@ -597,7 +597,7 @@ groupId=com.mycompany.app
artifactId=my-app
```
- To add resources to the classpath for your unit tests, you follow the same pattern as you do for adding resources to the JAR except the directory you place resources in is `${basedir}/src/test/resources`. At this point you would have a project directory structure that would look like the following:
+ To add resources to the classpath for your unit tests, you follow the same pattern as you do for adding resources to the JAR except the directory you place resources in is $\{basedir\}/src/test/resources. At this point you would have a project directory structure that would look like the following:
@@ -686,7 +686,7 @@ InputStream is = getClass().getResourceAsStream( "/test.properties" );
You'll notice that we had to add the `build`, `resources`, and `resource` elements which weren't there before. In addition, we had to explicitly state that the resources are located in the src/main/resources directory. All of this information was provided as default values previously, but because the default value for `filtering` is false, we had to add this to our pom.xml in order to override that default value and set `filtering` to true.
- To reference a property defined in your pom.xml, the property name uses the names of the XML elements that define the value, with "pom" being allowed as an alias for the project (root) element. So `${project.name}` refers to the name of the project, `${project.version}` refers to the version of the project, `${project.build.finalName}` refers to the final name of the file created when the built project is packaged, etc. Note that some elements of the POM have default values, so don't ne [...]
+ To reference a property defined in your pom.xml, the property name uses the names of the XML elements that define the value, with "pom" being allowed as an alias for the project (root) element. So `$\{project.name\}` refers to the name of the project, `$\{project.version\}` refers to the version of the project, `$\{project.build.finalName\}` refers to the final name of the file created when the built project is packaged, etc. Note that some elements of the POM have default values, so do [...]
To continue our example, let's add a couple of properties to the `application.properties` file (which we put in the `src/main/resources` directory) whose values will be supplied when the resource is filtered:
@@ -878,7 +878,7 @@ mvn process-resources "-Dcommand.line.prop=hello again"
For more information about the dependency mechanism as a whole, see [Introduction to Dependency Mechanism](../introduction/introduction-to-dependency-mechanism.html).
- With this information about a dependency, Maven will be able to reference the dependency when it builds the project. Where does Maven reference the dependency from? Maven looks in your local repository (`${user.home}/.m2/repository` is the default location) to find all dependencies. In a [previous section](How_do_I_create_a_JAR_and_install_it_in_my_local_repository), we installed the artifact from our project (my-app-1.0-SNAPSHOT.jar) into the local repository. Once it's installed there [...]
+ With this information about a dependency, Maven will be able to reference the dependency when it builds the project. Where does Maven reference the dependency from? Maven looks in your local repository (`$\{user.home\}/.m2/repository` is the default location) to find all dependencies. In a [previous section](How_do_I_create_a_JAR_and_install_it_in_my_local_repository), we installed the artifact from our project (my-app-1.0-SNAPSHOT.jar) into the local repository. Once it's installed the [...]
diff --git a/content/markdown/guides/getting-started/windows-prerequisites.md b/content/markdown/guides/getting-started/windows-prerequisites.md
index 2f970aea..35e8086a 100644
--- a/content/markdown/guides/getting-started/windows-prerequisites.md
+++ b/content/markdown/guides/getting-started/windows-prerequisites.md
@@ -47,14 +47,14 @@ java -version
### Maven Unpacked
- You need to unpack the Maven distribution. Don't unpack it in the middle of your source code; pick some location and unpack it there. Let's assume that the path is `${maven.home}`.
+ You need to unpack the Maven distribution. Don't unpack it in the middle of your source code; pick some location and unpack it there. Let's assume that the path is `$\{maven.home\}`.
### Maven in PATH
- You run Maven by invoking a command-line tool: `mvn.cmd` from the `bin` directory of the Maven. To do this conveniently, `${maven.home}/bin` must be in your PATH, just like the Java SDK commands. You can add directories to your `PATH` in the control panel; the details vary by Windows version.
+ You run Maven by invoking a command-line tool: `mvn.cmd` from the `bin` directory of the Maven. To do this conveniently, `$\{maven.home\}\\bin` must be in your PATH, just like the Java SDK commands. You can add directories to your `PATH` in the control panel; the details vary by Windows version.
diff --git a/content/markdown/guides/introduction/introduction-to-dependency-mechanism.md b/content/markdown/guides/introduction/introduction-to-dependency-mechanism.md
index 459a8d98..c7b2b476 100644
--- a/content/markdown/guides/introduction/introduction-to-dependency-mechanism.md
+++ b/content/markdown/guides/introduction/introduction-to-dependency-mechanism.md
@@ -322,7 +322,7 @@ This scope is only supported on a dependency of type `pom` in the `<dependencyMa
```
- **NOTE:** In two of these dependency references, we had to specify the `<type>` element. This is because the minimal set of information for matching a dependency reference against a dependencyManagement section is actually **{groupId, artifactId, type, classifier}**. In many cases, these dependencies will refer to jar artifacts with no classifier. This allows us to shorthand the identity set to **{groupId, artifactId}**, since the default for the type field is `jar`, and the default cla [...]
+ **NOTE:** In two of these dependency references, we had to specify the `<type>` element. This is because the minimal set of information for matching a dependency reference against a dependencyManagement section is actually **\{groupId, artifactId, type, classifier\}**. In many cases, these dependencies will refer to jar artifacts with no classifier. This allows us to shorthand the identity set to **\{groupId, artifactId\}**, since the default for the type field is `jar`, and the default [...]
A second, and very important use of the dependency management section is to control the versions of artifacts used in transitive dependencies. As an example consider these projects:
diff --git a/content/markdown/guides/introduction/introduction-to-plugin-prefix-mapping.md b/content/markdown/guides/introduction/introduction-to-plugin-prefix-mapping.md
index da041f44..a531a61a 100644
--- a/content/markdown/guides/introduction/introduction-to-plugin-prefix-mapping.md
+++ b/content/markdown/guides/introduction/introduction-to-plugin-prefix-mapping.md
@@ -39,9 +39,9 @@ under the License.
- - `maven-${prefix}-plugin` - for official plugins maintained by the Apache Maven team itself (you **must not** use this naming pattern for your plugin, see [this note for more informations](../plugin/guide-java-plugin-development.html#Plugin_Naming_Convention_and_Apache_Maven_Trademark))
+ - `maven-$\{prefix\}-plugin` - for official plugins maintained by the Apache Maven team itself (you **must not** use this naming pattern for your plugin, see [this note for more informations](../plugin/guide-java-plugin-development.html#Plugin_Naming_Convention_and_Apache_Maven_Trademark))
- - `${prefix}-maven-plugin` - for plugins from other sources
+ - `$\{prefix\}-maven-plugin` - for plugins from other sources
If your plugin's artifactId fits this pattern, Maven will automatically map your plugin to the correct prefix in the metadata stored within your plugin's groupId path on the repository. However, if you want to customize the prefix used to reference your plugin, you can specify the prefix directly through a configuration parameter on the `maven-plugin-plugin` in your plugin's POM:
@@ -84,9 +84,9 @@ mvn somePrefix:goal
- 1 Download `maven-metadata.xml` from each remote repository into the local repository, and name it `maven-metadata-${repoId}.xml` within the path of `${groupId}`.
+ 1 Download `maven-metadata.xml` from each remote repository into the local repository, and name it `maven-metadata-$\{repoId\}.xml` within the path of $\{groupId\}.
- 1 Load these metadata files, along with `maven-metadata-local.xml` (if it exists), within the path of `${groupId}`. Merge them.
+ 1 Load these metadata files, along with `maven-metadata-local.xml` (if it exists), within the path of $\{groupId\}. Merge them.
1 Lookup the plugin prefix in the merged metadata. If it's mapped, it should refer to a concrete groupId-artifactId pair. Otherwise, go on to #1 for the next groupId in the user's plugin-groups.
@@ -101,7 +101,7 @@ mvn somePrefix:goal
By default, Maven will search the groupId **org.apache.maven.plugins** for prefix-to-artifactId mappings for the plugins it needs to perform a given build. However, as previously mentioned, the user may have a need for third-party plugins. Since the Maven project is assumed to have control over the default plugin groupId, this means configuring Maven to search other groupId locations for plugin-prefix mappings.
- As it turns out, this is simple. In the Maven settings file (per-user: `${user.home}/.m2/settings.xml`; global: `${maven.home}/conf/settings.xml`), you can provide a custom **pluginGroups** section, listing the plugin groupIds you want to search (each groupId goes in its own **pluginGroup** sub-element). For example, if my project uses a Modello model file, I might have the following in my settings:
+ As it turns out, this is simple. In the Maven settings file (per-user: `$\{user.home\}/.m2/settings.xml`; global: `$\{maven.home\}/conf/settings.xml`), you can provide a custom **pluginGroups** section, listing the plugin groupIds you want to search (each groupId goes in its own **pluginGroup** sub-element). For example, if my project uses a Modello model file, I might have the following in my settings:
diff --git a/content/markdown/guides/introduction/introduction-to-plugins.md b/content/markdown/guides/introduction/introduction-to-plugins.md
index 2b3ef553..8fee0356 100644
--- a/content/markdown/guides/introduction/introduction-to-plugins.md
+++ b/content/markdown/guides/introduction/introduction-to-plugins.md
@@ -36,7 +36,7 @@ under the License.
Plugins are the central feature of Maven that allow for the reuse of common build logic across multiple projects. They do this by executing an "action" (i.e. creating a WAR file or compiling unit tests) in the context of a project's description - the Project Object Model (POM). Plugin behavior can be customized through a set of unique parameters which are exposed by a description of each plugin goal (or Mojo).
- One of the simplest plugins in Maven is the Clean Plugin. The [Maven Clean plugin](../../plugins/maven-clean-plugin/) (maven-clean-plugin) is responsible for removing the target directory of a Maven project. When you run "mvn clean", Maven executes the "clean" goal as defined in the Clean plug-in, and the target directory is removed. The Clean plugin [defines a parameter](../../plugins/maven-clean-plugin/clean-mojo.html) which can be used to customize plugin behavior, this parameter is [...]
+ One of the simplest plugins in Maven is the Clean Plugin. The [Maven Clean plugin](../../plugins/maven-clean-plugin/) (maven-clean-plugin) is responsible for removing the target directory of a Maven project. When you run "mvn clean", Maven executes the "clean" goal as defined in the Clean plug-in, and the target directory is removed. The Clean plugin [defines a parameter](../../plugins/maven-clean-plugin/clean-mojo.html) which can be used to customize plugin behavior, this parameter is [...]
diff --git a/content/markdown/guides/introduction/introduction-to-profiles.md b/content/markdown/guides/introduction/introduction-to-profiles.md
index 920c4327..5239e22f 100644
--- a/content/markdown/guides/introduction/introduction-to-profiles.md
+++ b/content/markdown/guides/introduction/introduction-to-profiles.md
@@ -103,7 +103,7 @@ under the License.
- Global
- - Defined in the [ global Maven-settings](/ref/current/maven-settings/settings.html) `(${maven.home}/conf/settings.xml)`.
+ - Defined in the [ global Maven-settings](/ref/current/maven-settings/settings.html) `($\{maven.home\}/conf/settings.xml)`.
@@ -595,7 +595,7 @@ mvn groupId:artifactId:goal -P -profile-1,-profile-2,-?profile-3
</project>
```
- Now, in your local `${user.home}/.m2/settings.xml`, you have:
+ Now, in your local `$\{user.home\}/.m2/settings.xml`, you have:
@@ -720,7 +720,7 @@ mvn -Denv=dev integration-test
mvn -Denv=production integration-test
```
- will not do a successful build. Why? Because, the resulting non-interpolated literal value of `${appserver.home}` will not be a valid path for deploying and testing your web application. We haven't considered the case for the production environment when writing our profiles. The "production" environment (env=production), along with "test" and possibly even "local" constitute a natural set of target environments for which we may want to build the integration-test lifecycle phase. The inc [...]
+ will not do a successful build. Why? Because, the resulting non-interpolated literal value of `$\{appserver.home\}` will not be a valid path for deploying and testing your web application. We haven't considered the case for the production environment when writing our profiles. The "production" environment (env=production), along with "test" and possibly even "local" constitute a natural set of target environments for which we may want to build the integration-test lifecycle phase. The i [...]
As a quick aside, it's possible for user-specific profiles to act in a similar way. This means that profiles for handling different environments which are keyed to the user can act up when the team adds a new developer. While I suppose this _could_ act as useful training for the newbie, it just wouldn't be nice to throw them to the wolves in this way. Again, be sure to think of the _whole_ set of profiles.
diff --git a/content/markdown/guides/introduction/introduction-to-the-pom.md b/content/markdown/guides/introduction/introduction-to-the-pom.md
index 4554ee0d..6ec1cf88 100644
--- a/content/markdown/guides/introduction/introduction-to-the-pom.md
+++ b/content/markdown/guides/introduction/introduction-to-the-pom.md
@@ -589,7 +589,7 @@ under the License.
##### Project Model Variables
- Any field of the model that is a single value element can be referenced as a variable. For example, `${project.groupId}`, `${project.version}`, `${project.build.sourceDirectory}` and so on. Refer to the POM reference to see a full list of properties.
+ Any field of the model that is a single value element can be referenced as a variable. For example, `$\{project.groupId\}`, `$\{project.version\}`, `$\{project.build.sourceDirectory\}` and so on. Refer to the POM reference to see a full list of properties.
These variables are all referenced by the prefix "`project.`". You may also see references with `pom.` as the prefix, or the prefix omitted entirely - these forms are now deprecated and should not be used.
diff --git a/content/markdown/guides/mini/guide-3rd-party-jars-remote.md b/content/markdown/guides/mini/guide-3rd-party-jars-remote.md
index ee5a77d5..0abd480f 100644
--- a/content/markdown/guides/mini/guide-3rd-party-jars-remote.md
+++ b/content/markdown/guides/mini/guide-3rd-party-jars-remote.md
@@ -30,7 +30,7 @@ under the License.
To deploy a 3rd party JAR use the deploy:deploy-file goal under maven-deploy-plugin.
- First, the wagon-provider(wagon-ftp, wagon-file, etc..) must be placed to your `${maven.home}/lib`.
+ First, the wagon-provider(wagon-ftp, wagon-file, etc..) must be placed to your `$\{maven.home\}/lib`.
Then execute the command:
diff --git a/content/markdown/guides/mini/guide-assemblies.md b/content/markdown/guides/mini/guide-assemblies.md
index edc291f4..efc5a943 100644
--- a/content/markdown/guides/mini/guide-assemblies.md
+++ b/content/markdown/guides/mini/guide-assemblies.md
@@ -66,7 +66,7 @@ under the License.
</project>
```
- You'll notice that the assembly descriptor is located in `${project.basedir}/src/assembly` which is the [standard](../introduction/introduction-to-the-standard-directory-layout.html) location for assembly descriptors.
+ You'll notice that the assembly descriptor is located in `$\{project.basedir\}/src/assembly` which is the [standard](../introduction/introduction-to-the-standard-directory-layout.html) location for assembly descriptors.
### Creating a binary assembly
diff --git a/content/markdown/guides/mini/guide-attached-tests.md b/content/markdown/guides/mini/guide-attached-tests.md
index 20d03c51..3a363676 100644
--- a/content/markdown/guides/mini/guide-attached-tests.md
+++ b/content/markdown/guides/mini/guide-attached-tests.md
@@ -24,7 +24,7 @@ under the License.
## Guide to using attached tests
- You can reuse the tests that you have created for one project in another. For example, suppose `foo-core` contains test code in the `${basedir}/src/test/java`. To package up those compiled tests in a JAR and deploy them for general reuse, configure the `maven-jar-plugin` as follows:
+ You can reuse the tests that you have created for one project in another. For example, suppose `foo-core` contains test code in the `$\{basedir\}/src/test/java`. To package up those compiled tests in a JAR and deploy them for general reuse, configure the `maven-jar-plugin` as follows:
diff --git a/content/markdown/guides/mini/guide-configuring-maven.md b/content/markdown/guides/mini/guide-configuring-maven.md
index ff81ef20..d390f9e2 100644
--- a/content/markdown/guides/mini/guide-configuring-maven.md
+++ b/content/markdown/guides/mini/guide-configuring-maven.md
@@ -45,13 +45,13 @@ under the License.
<!-- TODO: versioning doc that discusses this -->
- You can specify your user configuration in `${user.home}/.m2/settings.xml`. A [full reference](../../maven-settings/settings.html) to the configuration file is available. This section will show how to make some common configurations. Note that the file is not required - defaults will be used if it is not found.
+ You can specify your user configuration in `$\{user.home\}/.m2/settings.xml`. A [full reference](../../maven-settings/settings.html) to the configuration file is available. This section will show how to make some common configurations. Note that the file is not required - defaults will be used if it is not found.
### Configuring your Local Repository
- The location of your local repository can be changed in your user configuration. The default value is `${user.home}/.m2/repository/`.
+ The location of your local repository can be changed in your user configuration. The default value is `$\{user.home\}/.m2/repository/`.
diff --git a/content/markdown/guides/mini/guide-creating-archetypes.md b/content/markdown/guides/mini/guide-creating-archetypes.md
index ef1eb92a..9bd1233f 100644
--- a/content/markdown/guides/mini/guide-creating-archetypes.md
+++ b/content/markdown/guides/mini/guide-creating-archetypes.md
@@ -150,7 +150,7 @@ archetype
### 3. Create the prototype files and the prototype pom.xml
- The next component of the archetype to be created is the prototype `pom.xml`. Any `pom.xml` will do, just don't forget to the set `artifactId` and `groupId` as variables ( `${artifactId}` / `${groupId}` ). Both variables will be initialized from the commandline when calling `archetype:generate`.
+ The next component of the archetype to be created is the prototype `pom.xml`. Any `pom.xml` will do, just don't forget to the set `artifactId` and `groupId` as variables ( `$\{artifactId\}` / `$\{groupId\}` ). Both variables will be initialized from the commandline when calling `archetype:generate`.
An example for a prototype `pom.xml` is:
diff --git a/content/markdown/guides/mini/guide-encryption.md b/content/markdown/guides/mini/guide-encryption.md
index 4dc3e2d2..81a5ee42 100644
--- a/content/markdown/guides/mini/guide-encryption.md
+++ b/content/markdown/guides/mini/guide-encryption.md
@@ -58,7 +58,7 @@ under the License.
- - authorized users have an additional `settings-security.xml` file in their `${user.home}/.m2` folder
+ - authorized users have an additional `settings-security.xml` file in their `$\{user.home\}/.m2` folder
- this file either contains encrypted **master password**, used to encrypt other passwords
@@ -98,7 +98,7 @@ mvn --encrypt-master-password <password>
{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}
```
- Store this password in the `${user.home}/.m2/settings-security.xml`; it should look like
+ Store this password in the `$\{user.home\}/.m2/settings-security.xml`; it should look like
@@ -201,7 +201,7 @@ mvn deploy:deploy-file -Durl=https://maven.corp.com/repo \
in the file `/Volumes/mySecureUsb/secure/settings-security.xml`
- And then I create `${user.home}/.m2/settings-security.xml` with the following content:
+ And then I create `$\{user.home\}/.m2/settings-security.xml` with the following content:
@@ -221,7 +221,7 @@ mvn deploy:deploy-file -Durl=https://maven.corp.com/repo \
#### Escaping curly-brace literals in your password _(Since: Maven 2.2.0)_
- At times, you might find that your password (or the encrypted form of it) contains '{' or '}' as a literal value. If you added such a password as-is to your settings.xml file, you would find that Maven does strange things with it. Specifically, Maven treats all the characters preceding the '{' literal, and all the characters after the '}' literal, as comments. Obviously, this is not the behavior you want. What you really need is a way of **escaping** the curly-brace literals in your password.
+ At times, you might find that your password (or the encrypted form of it) contains '\{' or '\}' as a literal value. If you added such a password as-is to your settings.xml file, you would find that Maven does strange things with it. Specifically, Maven treats all the characters preceding the '\{' literal, and all the characters after the '\}' literal, as comments. Obviously, this is not the behavior you want. What you really need is a way of **escaping** the curly-brace literals in your [...]
You can do this with the widely used '\\' escape character. If your password looks like this:
@@ -237,7 +237,7 @@ jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+{EF1iFQyJQ=
```
-{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+{EF1iFQyJQ=}
+{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+\{EF1iFQyJQ=}
```
diff --git a/content/markdown/guides/mini/guide-maven-classloading.md b/content/markdown/guides/mini/guide-maven-classloading.md
index e4d7cd0a..f2d14366 100644
--- a/content/markdown/guides/mini/guide-maven-classloading.md
+++ b/content/markdown/guides/mini/guide-maven-classloading.md
@@ -49,7 +49,7 @@ under the License.
### Overview
- Maven uses the [Plexus Classworlds](https://codehaus-plexus.github.io/plexus-classworlds/) classloading framework to create the classloader graph. If you look in your `${maven.home}/boot` directory, you will see a single JAR which is the Classworlds JAR we use to boot the classloader graph. The Classworlds JAR is the only element of the Java `CLASSPATH`. The other classloaders are built by Classworlds ("realms" in Classworlds terminology).
+ Maven uses the [Plexus Classworlds](https://codehaus-plexus.github.io/plexus-classworlds/) classloading framework to create the classloader graph. If you look in your `$\{maven.home\}/boot` directory, you will see a single JAR which is the Classworlds JAR we use to boot the classloader graph. The Classworlds JAR is the only element of the Java `CLASSPATH`. The other classloaders are built by Classworlds ("realms" in Classworlds terminology).
Each realm exposes
@@ -84,10 +84,10 @@ under the License.
### Core Classloader
- The second classloader down the graph contains the core requirements of Maven. **It is used by Maven internally but not by plugins**. The core classloader has the libraries in `${maven.home}/lib`. In general these are just Maven libraries. For example instances of `[MavenProject](/ref/current/apidocs/org/apache/maven/project/MavenProject.html)` belong to this classloader.
+ The second classloader down the graph contains the core requirements of Maven. **It is used by Maven internally but not by plugins**. The core classloader has the libraries in `$\{maven.home\}/lib`. In general these are just Maven libraries. For example instances of `[MavenProject](/ref/current/apidocs/org/apache/maven/project/MavenProject.html)` belong to this classloader.
- You can add elements to this classloader by [extensions](/ref/current/maven-model/maven.html#class_extension). These are loaded through the same classloader as `${maven.home}/lib` and hence are available to the Maven core and all plugins for the current project (through the API classloader). More information is available in [Core Extension](./guide-using-extensions.html).
+ You can add elements to this classloader by [extensions](/ref/current/maven-model/maven.html#class_extension). These are loaded through the same classloader as `$\{maven.home\}/lib` and hence are available to the Maven core and all plugins for the current project (through the API classloader). More information is available in [Core Extension](./guide-using-extensions.html).
@@ -146,7 +146,7 @@ under the License.
</plugin>
```
- Plugins can inspect their effective runtime class path via the expressions `${plugin.artifacts}` or `${plugin.artifactMap}` to have a list or map, respectively, of resolved artifacts injected from the `[PluginDescriptor](/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/descriptor/PluginDescriptor.html)`.
+ Plugins can inspect their effective runtime class path via the expressions `$\{plugin.artifacts\}` or `$\{plugin.artifactMap\}` to have a list or map, respectively, of resolved artifacts injected from the `[PluginDescriptor](/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/descriptor/PluginDescriptor.html)`.
Please note that the plugin classloader does neither contain the [dependencies](/ref/current/maven-model/maven.html#class_dependency) of the current project nor its build output. Instead, plugins can query the project's compile, runtime and test class path from the `[MavenProject](/ref/current/apidocs/org/apache/maven/project/MavenProject.html)` in combination with the mojo annotation `requiresDependencyResolution` from the [Mojo API Specification](/developers/mojo-api-specification.htm [...]
diff --git a/content/markdown/guides/mini/guide-mirror-settings.md b/content/markdown/guides/mini/guide-mirror-settings.md
index c43b83a4..3fc4d46d 100644
--- a/content/markdown/guides/mini/guide-mirror-settings.md
+++ b/content/markdown/guides/mini/guide-mirror-settings.md
@@ -37,7 +37,7 @@ under the License.
- You want to run a [repository manager](../../repository-management.html) to provide a local cache to a mirror and need to use its URL instead
- To configure a mirror of a given repository, you provide it in your settings file (`${user.home}/.m2/settings.xml`), giving the new repository its own `id` and `url`, and specify the `mirrorOf` setting that is the ID of the repository you are using a mirror of. For example, the ID of the main Maven Central repository included by default is `central`, so to use the different mirror instance, you would configure the following:
+ To configure a mirror of a given repository, you provide it in your settings file (`$\{user.home\}/.m2/settings.xml`), giving the new repository its own `id` and `url`, and specify the `mirrorOf` setting that is the ID of the repository you are using a mirror of. For example, the ID of the main Maven Central repository included by default is `central`, so to use the different mirror instance, you would configure the following:
diff --git a/content/markdown/guides/mini/guide-multiple-repositories.md b/content/markdown/guides/mini/guide-multiple-repositories.md
index 13c4d1c9..c4f00b41 100644
--- a/content/markdown/guides/mini/guide-multiple-repositories.md
+++ b/content/markdown/guides/mini/guide-multiple-repositories.md
@@ -51,7 +51,7 @@ under the License.
**NOTE:** You will also get the standard set of repositories as defined in the [Super POM](../introduction/introduction-to-the-pom.html#Super_POM).
- The other way you can specify multiple repositories is by creating a profile in the `${user.home}/.m2/settings.xml` or `${maven.home}/conf/settings.xml` file like the following:
+ The other way you can specify multiple repositories is by creating a profile in the `$\{user.home\}/.m2/settings.xml` or `$\{maven.home\}/conf/settings.xml` file like the following:
diff --git a/content/markdown/guides/mini/guide-proxies.md b/content/markdown/guides/mini/guide-proxies.md
index abd03693..016915ce 100644
--- a/content/markdown/guides/mini/guide-proxies.md
+++ b/content/markdown/guides/mini/guide-proxies.md
@@ -23,7 +23,7 @@ under the License.
## Configuring a proxy
- You can configure a proxy to use for some or all of your HTTP requests with Maven. The username and password are only required if your proxy requires basic authentication (note that later releases may support storing your passwords in a secured keystore - in the mean time, please ensure your settings.xml file (usually `${user.home}/.m2/settings.xml`) is secured with permissions appropriate for your operating system).
+ You can configure a proxy to use for some or all of your HTTP requests with Maven. The username and password are only required if your proxy requires basic authentication (note that later releases may support storing your passwords in a secured keystore - in the mean time, please ensure your settings.xml file (usually $\{user.home\}/.m2/settings.xml) is secured with permissions appropriate for your operating system).
The `nonProxyHosts` setting accepts wild cards, and each host not to proxy is separated by the | character. This matches the JDK configuration equivalent.
diff --git a/content/markdown/guides/mini/guide-reproducible-builds.md b/content/markdown/guides/mini/guide-reproducible-builds.md
index 5500614d..5dfb89b0 100644
--- a/content/markdown/guides/mini/guide-reproducible-builds.md
+++ b/content/markdown/guides/mini/guide-reproducible-builds.md
@@ -135,7 +135,7 @@ mvn clean verify artifact:compare
- if you have a custom release process tooling, you'll need to add the feature to your release tooling. Notice that if you're using `versions-maven-plugin` in custom release scripts, starting with release 2.9.0, [`versions:set` goal updates the property](https://github.com/mojohaus/versions-maven-plugin/issues/453).
- - instead of explicitely writing a timestamp in their `pom.xml`, some people tend to prefer using last Git commit timestamp, like `${git.commit.time}` from [git-commit-id-maven-plugin](https://github.com/git-commit-id/git-commit-id-maven-plugin).
+ - instead of explicitely writing a timestamp in their `pom.xml`, some people tend to prefer using last Git commit timestamp, like `$\{git.commit.time\}` from [git-commit-id-maven-plugin](https://github.com/git-commit-id/git-commit-id-maven-plugin).
diff --git a/content/markdown/guides/mini/guide-site.md b/content/markdown/guides/mini/guide-site.md
index 6216b6bc..7a8df717 100644
--- a/content/markdown/guides/mini/guide-site.md
+++ b/content/markdown/guides/mini/guide-site.md
@@ -49,7 +49,7 @@ under the License.
+- site.xml
```
- You will notice there is now a `${basedir}/src/site` directory within which is contained a `site.xml` site descriptor along with various directories corresponding to the supported document types.
+ You will notice there is now a `$\{basedir\}/src/site` directory within which is contained a `site.xml` site descriptor along with various directories corresponding to the supported document types.
Let's take a look at the examples of the various document types:
diff --git a/content/markdown/guides/mini/guide-snippet-macro.md b/content/markdown/guides/mini/guide-snippet-macro.md
index 17d8297a..bd60f296 100644
--- a/content/markdown/guides/mini/guide-snippet-macro.md
+++ b/content/markdown/guides/mini/guide-snippet-macro.md
@@ -104,7 +104,7 @@ under the License.
%{snippet|id=snip-id|url=file:///path/to/Sample.java}
```
- As of doxia-core version 1.0-alpha-9, a 'file' parameter is also available. If a full path is not specified, the location is assumed to be relative to `${basedir}`.
+ As of doxia-core version 1.0-alpha-9, a 'file' parameter is also available. If a full path is not specified, the location is assumed to be relative to $\{basedir\}.
diff --git a/content/markdown/guides/mini/guide-using-extensions.md b/content/markdown/guides/mini/guide-using-extensions.md
index cacfd532..0493b852 100644
--- a/content/markdown/guides/mini/guide-using-extensions.md
+++ b/content/markdown/guides/mini/guide-using-extensions.md
@@ -42,7 +42,7 @@ under the License.
- - Registered via extension jar in `${maven.home}/lib/ext`
+ - Registered via extension jar in `$\{maven.home\}/lib/ext`
- Registered via CLI argument `mvn -Dmaven.ext.class.path=extension.jar`
diff --git a/content/markdown/guides/mini/guide-using-toolchains.md b/content/markdown/guides/mini/guide-using-toolchains.md
index 828ec636..66b6034f 100644
--- a/content/markdown/guides/mini/guide-using-toolchains.md
+++ b/content/markdown/guides/mini/guide-using-toolchains.md
@@ -114,7 +114,7 @@ under the License.
The `toolchains.xml` file (see below) is the configuration file where you set the installation paths of your toolchains. This file should be put in your `${user.home}/.m2` directory. When the `maven-toolchains-plugin` executes, it looks for the `toolchains.xml` file, reads it and looks for a toolchain matching the toolchains requirements configured in the plugin. In our example, that would be a JDK toolchain with `<version>` "1.5" and `<vendor>` "sun". Once a match is found, the plugin [...]
- Starting with [Maven 3.3.1](/docs/3.3.1/release-notes.html) you can put the `toolchains.xml` file wherever you like by using the `--global-toolchains file` option but it is recommended to locate it into `${user.home}/.m2/`.
+ Starting with [Maven 3.3.1](/docs/3.3.1/release-notes.html) you can put the `toolchains.xml` file wherever you like by using the `--global-toolchains file` option but it is recommended to locate it into `$\{user.home\}/.m2/`.
diff --git a/content/markdown/guides/plugin/guide-java-plugin-development.md b/content/markdown/guides/plugin/guide-java-plugin-development.md
index 725cbd36..e818f88f 100644
--- a/content/markdown/guides/plugin/guide-java-plugin-development.md
+++ b/content/markdown/guides/plugin/guide-java-plugin-development.md
@@ -252,9 +252,9 @@ mvn groupId:artifactId:version:goal
- If you need to run the latest version of a plugin installed in your local repository, you can omit its version number. So just use "`mvn sample.plugin:hello-maven-plugin:sayhi`" to run your plugin.
- - You can assign a shortened prefix to your plugin, such as `mvn hello:sayhi`. This is done automatically if you follow the convention of using `${prefix}-maven-plugin` (or `maven-${prefix}-plugin` if the plugin is part of the Apache Maven project). You may also assign one through additional configuration - for more information see [ Introduction to Plugin Prefix Mapping](../introduction/introduction-to-plugin-prefix-mapping.html).
+ - You can assign a shortened prefix to your plugin, such as `mvn hello:sayhi`. This is done automatically if you follow the convention of using `$\{prefix\}-maven-plugin` (or `maven-$\{prefix\}-plugin` if the plugin is part of the Apache Maven project). You may also assign one through additional configuration - for more information see [ Introduction to Plugin Prefix Mapping](../introduction/introduction-to-plugin-prefix-mapping.html).
- - Finally, you can also add your plugin's groupId to the list of groupIds searched by default. To do this, you need to add the following to your `${user.home}/.m2/settings.xml` file:
+ - Finally, you can also add your plugin's groupId to the list of groupIds searched by default. To do this, you need to add the following to your `$\{user.home\}/.m2/settings.xml` file:
```
<pluginGroups>
@@ -352,7 +352,7 @@ mvn archetype:generate \
private String greeting;
```
- The portion before the annotations is the description of the parameter. The `parameter` annotation identifies the variable as a mojo parameter. The `defaultValue` parameter of the annotation defines the default value for the variable. This value can include expressions which reference the project, such as "`${project.version}`" (more can be found in the ["Parameter Expressions" document](/ref/current/maven-core/apidocs/org/apache/maven/plugin/PluginParameterExpressionEvaluator.html)). T [...]
+ The portion before the annotations is the description of the parameter. The `parameter` annotation identifies the variable as a mojo parameter. The `defaultValue` parameter of the annotation defines the default value for the variable. This value can include expressions which reference the project, such as "`$\{project.version\}`" (more can be found in the ["Parameter Expressions" document](/ref/current/maven-core/apidocs/org/apache/maven/plugin/PluginParameterExpressionEvaluator.html)). [...]
diff --git a/content/markdown/plugin-developers/common-bugs.md b/content/markdown/plugin-developers/common-bugs.md
index 947be36d..95d21d2c 100644
--- a/content/markdown/plugin-developers/common-bugs.md
+++ b/content/markdown/plugin-developers/common-bugs.md
@@ -269,7 +269,7 @@ public MyMojo extends AbstractMojo
### Resolving Relative Paths
- It is common practice for users of Maven to specify relative paths in the POM, not to mention that the Super POM does so, too. The intention is to resolve such relative paths against the base directory of the current project. In other words, the paths `target/classes` and `${basedir}/target/classes` should resolve to the same directory for a given POM.
+ It is common practice for users of Maven to specify relative paths in the POM, not to mention that the Super POM does so, too. The intention is to resolve such relative paths against the base directory of the current project. In other words, the paths `target/classes` and `$\{basedir\}/target/classes` should resolve to the same directory for a given POM.
Unfortunately, the class `[java.io.File](http://java.sun.com/javase/6/docs/api/java/io/File.html)` does not resolve relative paths against the project's base directory. As mentioned in its class javadoc, it resolves relative paths against the current working directory. In plain English: Unless a Maven component has complete control over the current working directory, any usage of `java.io.File` in combination with a relative path is a bug.
@@ -343,7 +343,7 @@ if ( !file.isAbsolute() )
Most reporting plugins inherit from `AbstractMavenReport`. In doing so, they need to implement the inherited but abstract method `getOutputDirectory()`. To implement this method, plugins usually declare a field named `outputDirectory` which they return in the method. Nothing wrong so far.
- Now, some plugins need to create additional files in the report output directory that accompany the report generated via the sink interface. While it is tempting to use either the method `getOutputDirectory()` or the field `outputDirectory` directly in order to setup a path for the output files, this leads most likely to a bug. More precisely, those plugins will not properly output files when run by the Maven Site Plugin as part of the site lifecycle. This is best noticed when the outpu [...]
+ Now, some plugins need to create additional files in the report output directory that accompany the report generated via the sink interface. While it is tempting to use either the method `getOutputDirectory()` or the field `outputDirectory` directly in order to setup a path for the output files, this leads most likely to a bug. More precisely, those plugins will not properly output files when run by the Maven Site Plugin as part of the site lifecycle. This is best noticed when the outpu [...]
diff --git a/content/markdown/plugin-developers/cookbook/plexus-plugin-upgrade.md b/content/markdown/plugin-developers/cookbook/plexus-plugin-upgrade.md
index d3e506ad..3a0436c3 100644
--- a/content/markdown/plugin-developers/cookbook/plexus-plugin-upgrade.md
+++ b/content/markdown/plugin-developers/cookbook/plexus-plugin-upgrade.md
@@ -128,7 +128,7 @@ default: `${basedir}/src/test/resources/META-INF/plexus`|
</project>
```
- If `merge-descriptors` is used, move the handwritten xml file to `${basedir}/src/main/resources/META-INF/plexus`.
+ If `merge-descriptors` is used, move the handwritten xml file to `$\{basedir\}/src/main/resources/META-INF/plexus`.