Skip to content

Commit 116cc47

Browse files
committed
Document activating CI profiles
1 parent b6101b3 commit 116cc47

File tree

1 file changed

+16
-7
lines changed

1 file changed

+16
-7
lines changed

BUILDING.adoc

Lines changed: 16 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -115,23 +115,32 @@ You can follow below steps for casual development needs:
115115
./mvnw verify -DskipTests -pl :log4j-core,:log4j-core-test
116116
----
117117
118-
[TIP]
119-
====
118+
[#development-ide-debug]
119+
=== Debugging `./mvnw test` with IDE
120+
120121
You can connect your IDE to a `./mvnw test` run by
121122
122123
. Run `./mvnw test -pl :log4j-core-test -Dtest=FooBarTest -Dmaven.surefire.debug`
123124
. Use _"Run > Attach to process"_ in IntelliJ IDEA
124-
====
125125
126-
[#development-faq]
127-
=== F.A.Q
126+
[#development-ci]
127+
=== Activating CI profiles
128+
129+
There are certain Maven profiles activated only for CI.
130+
As a consequence of this, you can observe certain CI failures that you can't reproduce locally.
131+
To work around this, you can activate CI profiles by running Maven commands as follows:
132+
133+
[source,bash]
134+
----
135+
CI=true ./mvnw ...
136+
----
128137
129138
[#development-faq-idea-plugin-not-found]
130-
==== Compilation in IntelliJ IDEA fails with `java: plug-in not found: ErrorProne`
139+
=== Compilation in IntelliJ IDEA fails with `java: plug-in not found: ErrorProne`
131140
132141
Try removing all _"Override compiler parameters per-module"_ entries in _"Settings > Build, Execution, Deployment > Compiler > Java Compiler"_.
133142
134143
[#development-faq-idea-package-plugins]
135-
==== Compilation in IntelliJ IDEA fails with `java: package org.apache.logging.log4j.plugins.test.validation.plugins does not exist`
144+
=== Compilation in IntelliJ IDEA fails with `java: package org.apache.logging.log4j.plugins.test.validation.plugins does not exist`
136145
137146
We don't know how to fix this.

0 commit comments

Comments
 (0)