Skip to content

Commit 37edf36

Browse files
Update development_guidelines.md
ninja: fix link to IntelliJ docs
1 parent 043a39e commit 37edf36

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docsite/docs/development_guidelines.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,8 +21,8 @@ not run properly on newer versions of the JVM.
2121

2222
As soon as you clone the project you should verify that you are able to build and test locally, to do so you need to
2323
run the `check` command of Gradle, you can achieve that using either `gradlew` script in the project root (`.
24-
/gradlew check`) or run the same [gradle task from intellij](https://www.jetbrains.com/help/idea/work-with-gradle-tasks.
25-
html). If you're default jvm is not version 11, you can run `gradlew` passing another java home as follows:
24+
/gradlew check`) or run the same [gradle task from intellij](https://www.jetbrains.com/help/idea/work-with-gradle-tasks.html).
25+
If you're default jvm is not version 11, you can run `gradlew` passing another java home as follows:
2626
`./gradlew -Dorg.gradle.java.home=<PATH_TO_JAVA_HOME> build`.
2727

2828
Sometimes IntelliJ will tell you have build errors, especially when moving from one branch to the other. The problem

0 commit comments

Comments
 (0)