You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@solr.apache.org by md...@apache.org on 2021/04/30 16:04:47 UTC
[solr] branch main updated: Document why we use different output
paths for IntelliJ (#98)
This is an automated email from the ASF dual-hosted git repository.
mdrob pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr.git
The following commit(s) were added to refs/heads/main by this push:
new 838f1f1 Document why we use different output paths for IntelliJ (#98)
838f1f1 is described below
commit 838f1f180abcdcc915fb1c24c5ab38ec7b602ada
Author: Mike Drob <md...@apache.org>
AuthorDate: Fri Apr 30 11:04:38 2021 -0500
Document why we use different output paths for IntelliJ (#98)
---
gradle/ide/intellij-idea.gradle | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/gradle/ide/intellij-idea.gradle b/gradle/ide/intellij-idea.gradle
index 1d5b8d2..bc34fcb 100644
--- a/gradle/ide/intellij-idea.gradle
+++ b/gradle/ide/intellij-idea.gradle
@@ -29,6 +29,11 @@ allprojects {
idea {
module {
+ /* These are intentionally different from the standard Gradle paths.
+ When using the internal IntelliJ compiler instead of delegating to
+ the Gradle compiler, using the same directory can lead to strange
+ locking and staleness issues (esp Windows).
+ */
outputDir file('build/idea/classes/main')
testOutputDir file('build/idea/classes/test')
downloadSources = true