Is there more detail around the new `syncOptionsAs...
# eap
z
Is there more detail around the new
syncOptionsAsConvention
impl in KGP? We set some compiler options like
javaParameters
and disallow changes after we set them, but in 1.9.0-Beta we're surprised to see that KGP is setting these values again after we've set them (example in 🧵)
👀 1
Copy code
Caused by: java.lang.IllegalStateException: The value for property 'javaParameters' cannot be changed any further.	
at org.gradle.api.internal.provider.AbstractProperty$NonFinalizedValue.beforeMutate(AbstractProperty.java:395)	
at org.gradle.api.internal.provider.AbstractProperty.assertCanMutate(AbstractProperty.java:272)	
at org.gradle.api.internal.provider.AbstractProperty.setConvention(AbstractProperty.java:226)	
at org.gradle.api.internal.provider.DefaultProperty.convention(DefaultProperty.java:116)	
at org.jetbrains.kotlin.gradle.dsl.KotlinJvmCompilerOptionsHelper.syncOptionsAsConvention$kotlin_gradle_plugin_common(KotlinJvmCompilerOptionsHelper.kt:31)	
at org.jetbrains.kotlin.gradle.plugin.KotlinJvmPlugin$Companion$configureCompilerOptionsForTarget$1.invoke(KotlinJvmPlugin.kt:42)	
at org.jetbrains.kotlin.gradle.plugin.KotlinJvmPlugin$Companion$configureCompilerOptionsForTarget$1.invoke(KotlinJvmPlugin.kt:40)	
at org.jetbrains.kotlin.gradle.plugin.KotlinJvmPluginKt$sam$org_gradle_api_Action$0.execute(KotlinJvmPlugin.kt)
t
Generally this method sets project level options values as a convention values for task compiler options. Is it happening with Kotlin/Android plugin?
z
let me check which project it was
I wondered if that was the case, and suspect what's happening is it's attempting to set the convention after we set
disallowChanges()
because some properties (like this) we set immediately
@tapchicoma should I file a bug?
t
If you have a repro - please file, I will try to check if it is possible to fix