Skip to content

Fixed numbered list in Properties section, fix typo. #1622

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ljkGH wants to merge 1 commit into
base: master
Choose a base branch
from
+8 −8
Open

Fixed numbered list in Properties section, fix typo. #1622

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions content/markdown/pom.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -801,16 +801,16 @@ They come in five different styles:
1. `env.X`: Prefixing a variable with "env." will return the shell's environment variable.
For example, `${env.PATH}` contains the PATH environment variable.

*Note*: While environment variables themselves are case-insensitive on Windows, lookup of properties is case-sensitive.
In other words, while the Windows shell returns the same value for `%PATH%` and `%Path%`, Maven distinguishes between `${env.PATH}` and `${env.Path}`.
**The names of environment variables are normalized to all upper-case** for the sake of reliability.
*Note*: While environment variables themselves are case-insensitive on Windows, lookup of properties is case-sensitive.
In other words, while the Windows shell returns the same value for `%PATH%` and `%Path%`, Maven distinguishes between `${env.PATH}` and `${env.Path}`.
**The names of environment variables are normalized to all upper-case** for the sake of reliability.

2. `project.x`: A dot (`.`) notated path in the POM will contain the corresponding element's value.
1. `project.x`: A dot (`.`) notated path in the POM will contain the corresponding element's value.
For example: `<project><version>1.0</version></project`> is accessible via `${project.version}`.
3. `settings.x`: A dot (`.`) notated path in the `settings.xml` will contain the corresponding element's value.
1. `settings.x`: A dot (`.`) notated path in the `settings.xml` will contain the corresponding element's value.
For example: `<settings><offline>false</offline></settings`> is accessible via `${settings.offline}`.
4. Java System Properties: All properties accessible via `java.lang.System.getProperties()` are available as POM properties, such as `${java.home}`.
5. `x`: Set within a `<properties /`> element in the POM. The value of `<properties><someVar>value</someVar></properties`> may be used as `${someVar}`.
1. Java System Properties: All properties accessible via `java.lang.System.getProperties()` are available as POM properties, such as `${java.home}`.
1. `x`: Set within a `<properties /`> element in the POM. The value of `<properties><someVar>value</someVar></properties`> may be used as `${someVar}`.

## Build Settings

Expand Down Expand Up @@ -1489,7 +1489,7 @@ should not be contacted about the project, they do not need to be listed here.
developer's name and email address.

* `<organization>`, `<organizationUrl>`:
As you probably guessed, these are the developer's organization name and it's URL, respectively.
As you probably guessed, these are the developer's organization name and its URL, respectively.

* `<roles>`:
A `role` should specify the standard actions that the person is responsible for. Like a single person
Expand Down