You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately the @Language injection workaround doesn't play well in regular projects. The org.intellij.lang.annotations.Language defined by Parsus 'overrides' the official one provided by java-annotations, and because Parsus' is marked as internal, it causes compilation errors in the project whenever Parsus is present.
The quickest way to reproduce this is in a Gradle build script, although I also encounter the same problem in src/main/kotlin in regular projects:
The result is that whenever I have Parsus as a dependency, my project cannot use @Language at all. And I can't think of a workaround.
Suggestions
I have two suggestions:
Change the visibility of Parsus' @Language from internal to public.
java-annotations has been converted to KMP in v25.0.0, although it is yet to be released. This will provide a valid multiplatform @Language. So, for now, remove Parsus' @Language, and then when java-annotations v25.0.0 is released, switch to use that.
Unfortunately the
@Language
injection workaround doesn't play well in regular projects. Theorg.intellij.lang.annotations.Language
defined by Parsus 'overrides' the official one provided by java-annotations, and because Parsus' is marked asinternal
, it causes compilation errors in the project whenever Parsus is present.The quickest way to reproduce this is in a Gradle build script, although I also encounter the same problem in src/main/kotlin in regular projects:
The result is that whenever I have Parsus as a dependency, my project cannot use
@Language
at all. And I can't think of a workaround.Suggestions
I have two suggestions:
@Language
frominternal
topublic
.@Language
. So, for now, remove Parsus'@Language
, and then when java-annotations v25.0.0 is released, switch to use that.Related
@Language
internal #11The text was updated successfully, but these errors were encountered: