amanda.hinchman-dominguez
12/16/2024, 2:11 PMjava.lang.illegalstateexception: system property "compose.compiler.hosted.jar.path" is not found
- how should I get past this error?dmitriy.novozhilov
12/16/2024, 2:13 PMamanda.hinchman-dominguez
12/16/2024, 4:27 PM./gradlew clean build :compiler
does allow the tests to run... even if the build itself seems to fail
➜ ./gradlew build :compiler
...
> Configure project :plugins:compose-compiler-plugin:compiler-hosted:integration-tests
w: ⚠️ The Default Kotlin Hierarchy Template was not applied to 'project ':plugins:compose-compiler-plugin:compiler-hosted:integration-tests'':
Explicit .dependsOn() edges were configured for the following source sets:
[jvmTest]
Consider removing dependsOn-calls or disabling the default template by adding
'kotlin.mpp.applyDefaultHierarchyTemplate=false'
to your gradle.properties
Learn more about hierarchy templates: <https://kotl.in/hierarchy-template>
[Incubating] Problems report is available at: file:///Users/amandahinchman-dominguez/Documents/repositories/kotlin/build/reports/problems/problems-report.html
FAILURE: Build failed with an exception.
* What went wrong:
Cannot locate tasks that match ':compiler' as task 'compiler' is ambiguous in root project 'kotlin'. Candidates are: 'compilerPluginTest', 'compilerTest'.
dmitriy.novozhilov
12/16/2024, 4:30 PMbuild
task for building the project, use dist
.
For running tests it's better to call the :test
task of the specific module (:plugins:compose-compiler-plugin:compiler-hosted:integration-tests:jvmTest
in your case).
But the recommended way it to run test from the IDE, it will automatically pick the needed task for you.amanda.hinchman-dominguez
12/16/2024, 4:32 PMdist
from now on. It's so nice to see how portable the compiler is now 🙂dmitriy.novozhilov
12/16/2024, 4:32 PMamanda.hinchman-dominguez
12/16/2024, 4:35 PMamanda.hinchman-dominguez
12/16/2024, 4:37 PMdmitriy.novozhilov
12/16/2024, 4:37 PMamanda.hinchman-dominguez
12/16/2024, 4:42 PMamanda.hinchman-dominguez
12/16/2024, 4:48 PM