We could really use the community's help by up-vot...
# general
s
We could really use the community's help by up-voting three IntelliJ IDEA issues, where tags from Grails custom tag-libraries (plugins) does not support the
go to
to view the source. There is a tracker issue in the Grails core project: https://github.com/grails/grails-core/issues/13910
👍 8
👍🏼 1
j
Have others seen issues with only tag libs, or any sort of "go to" functionality in multi-module Grails projects with an inline plugin dependency? Our experience has been that once the plugin has been compiled, IntelliJ chooses the
.class
files in
my-plugin/build/libs/my-plugin-0.1-plain.jar
when using the "go to" feature for services, domain classes, etc. The only way we've found to "fix" this is to delete
my-plugin-0.1-plain.jar
.
Ah, this seems to match the behavior we are seeing: https://youtrack.jetbrains.com/issue/IDEA-342753/IDEA-does-not-recognize-dependencies-between-Modules-in-a-Grails-Project Soliciting upvotes on this one as well! 😄 I have IntelliJ 2022.3.3 installed in addition to the latest, which I use for Grails as a workaround for this issue.