Skip to content

Commit a562d77

Browse files
committed
Clarify Maven reactor usage and update README with improved build instructions.
1 parent bed88c2 commit a562d77

1 file changed

Lines changed: 11 additions & 2 deletions

File tree

README.md

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -91,12 +91,21 @@ Both modules pass the full scenario (`Tests run: 1, Failures: 0, Errors: 0`) aga
9191

9292
## Build & run
9393

94+
Maven modules depend on built artifacts, not directly on sibling source or resource directories. If
95+
you run a single runtime module without `-am`, Maven resolves `spark-test-common` from
96+
`~/.m2/repository`, so stale TOML/resources can be used until `spark-test-common` is installed
97+
again. Prefer `-am` for focused module runs; it adds required reactor modules and uses the freshly
98+
built `spark-test-common` artifact.
99+
94100
```bash
95101
# compile everything and install spark-test-common into the local repo
96102
mvn install -DskipTests
97103

98-
# run the full scenario on each line (requires Docker)
99-
mvn -pl spark-apache test
104+
# run the full scenario on one line and also build required reactor modules
105+
mvn -pl spark-apache -am test
106+
mvn -pl spark-cloudera -am test
107+
108+
# only use this after mvn install has refreshed local SNAPSHOT artifacts
100109
mvn -pl spark-cloudera test
101110

102111
# or both

0 commit comments

Comments
 (0)