Skip to content

Commit 5b418ac

Browse files
committed
Document activating CI profiles
1 parent 9de91b8 commit 5b418ac

File tree

1 file changed

+15
-6
lines changed

1 file changed

+15
-6
lines changed

BUILDING.adoc

Lines changed: 15 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -148,18 +148,27 @@ You can follow below steps for casual development needs:
148148
./mvnw verify -DskipTests -pl :log4j-core,:log4j-core-test
149149
----
150150
151-
[TIP]
152-
====
151+
[#development-ide-debug]
152+
=== Debugging `./mvnw test` with IDE
153+
153154
You can connect your IDE to a `./mvnw test` run by
154155
155156
. Run `./mvnw test -pl :log4j-core-test -Dtest=FooBarTest -Dmaven.surefire.debug`
156157
. Use _"Run > Attach to process"_ in IntelliJ IDEA
157-
====
158158
159-
[#development-faq]
160-
=== F.A.Q
159+
[#development-ci]
160+
=== Activating CI profiles
161+
162+
There are certain Maven profiles activated only for CI.
163+
As a consequence of this, you can observe certain CI failures that you can't reproduce locally.
164+
To work around this, you can activate CI profiles by running Maven commands as follows:
165+
166+
[source,bash]
167+
----
168+
CI=true ./mvnw ...
169+
----
161170
162171
[#development-faq-idea-plugin-not-found]
163-
==== Compilation in IntelliJ IDEA fails with `java: plug-in not found: ErrorProne`
172+
=== Compilation in IntelliJ IDEA fails with `java: plug-in not found: ErrorProne`
164173
165174
Try removing all _"Override compiler parameters per-module"_ entries in _"Settings > Build, Execution, Deployment > Compiler > Java Compiler"_.

0 commit comments

Comments
 (0)