Scott Murphy

@jamesfredley there is an issue with that approach, you get 7MB in bonus jars to exclude ``` +--- org.grails:grails-shell:6.1.2 | +--- org.apache.maven:maven-resolver-provider:3.9.6 | | +--- org.apache.maven:maven-model:3.9.6 | | | \---...

@jamesfredley so I am wondering how we can get IntelliJ to resolve grails-shell in 6.2.1 without having to put it in the build path. We probably need to first figure...

> I just tested it against your website project using Grails 6.2.1-SNAPSHOT and grails shell 6.1.2 is available for IntelliJ, but does not get put into the build path. @jamesfredley...

@jamesfredley so my previous comment was in regards to why it has to be added and in a 5.x project it does not. ``` ./gradlew buildEnvironment ``` ``` classpath +---...

Is the Forge shell capable of loading auto completing Application Commands from plugins?

@sdelamo from what James is saying it is not 2 ways of doing the same thing if embracing gradle is not even capable of doing the same thing. The way...

compileOnlyAPI is still not an ideal solution and should be avoided at all costs. The reason for needing the dependency should be addressed first. For instance, servlet api references should...

> The build is failing after the last cleanup commit 80534e7 I guess it doesn't like to resolve bom versions for documentation dependencies ```gradle documentation("org.fusesource.jansi:jansi:$jansiVersion") documentation("jline:jline:$jlineVersion") documentation ("com.github.javaparser:javaparser-core:$javaParserCoreVersion") ``` I...

> Wouldn't `documentation platform(project(':grails-bom'))` add it? @matrei apparently so... done.

> > Wouldn't documentation platform(project(':grails-bom')) add it? > > apparently so... done > > Did you push that change? @matrei yeah, it worked