Skip to content

Commit 4e08c7f

Browse files
committed
Feedback
1 parent 56f0101 commit 4e08c7f

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

content/markdown/guides/mini/guide-multiple-subprojects-4.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ This part of the Maven core does the following:
3737

3838
### Collecting subprojects
3939

40-
Subprojects collection starts from one aggregator project.
40+
Subproject collection starts from one aggregator project.
4141
That project defines the subprojects of which it consists using the `<subproject>` element.
4242
This is a recursive process, so aggregators can have child subprojects which are aggregators themselves.
4343

@@ -56,7 +56,7 @@ Using the file parameter (`--file` or `-f`), you can point to another POM.
5656

5757
### Sorting subprojects
5858

59-
Because subprojects within a multi-project setup build can depend on each other, it is important that the reactor sorts
59+
Because subprojects within a multi-project build can depend on each other, it is important that the reactor sorts
6060
all the projects in a way that guarantees each project is built before it is required.
6161

6262
The following relationships are honoured when sorting projects:
@@ -112,15 +112,15 @@ Similarly, `--also-make-dependents` lets Maven include all subprojects which dep
112112
#### Dealing with failures
113113

114114
There are several ways to customize how the reactor deals with failures.
115-
`--fail-at-end` fails the build after building as many subprojects as possible.
116-
In this case, subprojects that do not depend on a failed subproject will still be built.
117-
`--fail-fast`, in contrast, fails the build as soon as one subproject has failed.
118-
This is the default behaviour.
119-
`--fail-never` ignores build failures.
115+
116+
* `--fail-at-end` fails the build after building as many subprojects as possible.
117+
In this case, subprojects that do not depend on a failed subproject will still be built.
118+
* `--fail-fast`, in contrast, fails the build as soon as one subproject has failed.
119+
This is the default behaviour.
120+
* `--fail-never` ignores build failures.
120121

121122
When a build has failed, and you want to start it again, you can skip building the subprojects that were previously
122-
built
123-
successfully using `--resume` (or `-r`).
123+
built successfully using `--resume` (or `-r`).
124124
To resume a build from a specific subproject, you can use `--resume-from <selector>`.
125125

126126
#### Bringing it together

0 commit comments

Comments
 (0)