You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@grails.apache.org by Carl Marcum <cm...@apache.org> on 2025/07/04 15:24:41 UTC
problem with Grails CLI and web plugin
Hi All,
When I create a 7.0.0-M4 web plugin and try to get a Grails CLI with the
Grails installed with sdkman or using the Grails wrapper I get:
| Error Error initializing classpath: Multiple builders are available to
build a model of type 'org.grails.gradle.plugin.model.GrailsClasspath'.
At first I thought it might be due having multiple Grails or Gradle
installed but even after uninstalling all of both and using the wrapper
I still got it.
No issues the the web application.
Any ideas what to check or how to get more output?
BTW, no additional features selected. Gorm Hibernate, Tomcat, Spock, Java 21
Thanks,
Carl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@grails.apache.org
For additional commands, e-mail: users-help@grails.apache.org
Re: problem with Grails CLI and web plugin
Posted by Carl Marcum <cm...@apache.org>.
Hi James,
Thanks for the detailed explanation.
Yes 'grails -t forge' using an installed Grails M4 and './grailsw -t
forge' in a 7.0.0-SNAPSHOT project both provide a forge interactive CLI.
I see a M5 vote has begun with many fixes so I'll test again.
Best regards,
Carl
On 7/8/25 11:04 AM, James Daugherty wrote:
> Thanks Carl. So in 7, we've been reworking our CLIs and are
> experiencing some growing pains.
>
> `grailsw` is the wrapper file that downloads `grails` to ~/.grails/ -
> it's meant to be small so that it can be checked in as a convenience.
> I would expect the same error since it should just be a passthrough
> for the grails-cli (`grails` command). This is good news!
>
> So the real issue is with the `grails` command. The grails command
> was added in 7 as a delegating CLI that can call either forge or the
> legacy shell-cli. Forge was announced in Grails 6.x, but we realized
> that due to tooling limitations that defaulting to forge on the CLI
> can cause functional issues with IntelliJ. For this reason, in 7, we
> reverted the default to the legacy cli. There is a longer term plan
> to add missing features to forge so the legacy & delegating cli can be
> completely dropped.
>
> As to your problem: If you run grails with a first argument of `-t
> forge` I suspect this will work. The web plugin profile (used by the
> legacy shell) was broken in the M4 and we've made changes that may
> fully fix it in the M5. Assuming the forge argument works, let's
> retest this once the M5 is out?
>
> -James
>
>
> On Mon, Jul 7, 2025 at 6:22 PM Carl Marcum <cm...@apache.org> wrote:
>
> Hi James,
>
> grails
> and
> ./grailsw
>
> Best regards,
>
> Carl
>
> On 7/6/25 11:54 AM, James Daugherty wrote:
> > Hi Carl,
> >
> > Can you provide the exact command you're using?
> >
> > Regards,
> > James
> >
> > On 2025/07/04 15:24:41 Carl Marcum wrote:
> >> Hi All,
> >>
> >> When I create a 7.0.0-M4 web plugin and try to get a Grails CLI
> with the
> >> Grails installed with sdkman or using the Grails wrapper I get:
> >> | Error Error initializing classpath: Multiple builders are
> available to
> >> build a model of type
> 'org.grails.gradle.plugin.model.GrailsClasspath'.
> >> At first I thought it might be due having multiple Grails or Gradle
> >> installed but even after uninstalling all of both and using the
> wrapper
> >> I still got it.
> >> No issues the the web application.
> >> Any ideas what to check or how to get more output?
> >>
> >> BTW, no additional features selected. Gorm Hibernate, Tomcat,
> Spock, Java 21
> >>
> >> Thanks,
> >> Carl
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@grails.apache.org
> >> For additional commands, e-mail: users-help@grails.apache.org
> >>
> >>
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@grails.apache.org
> > For additional commands, e-mail: users-help@grails.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@grails.apache.org
> For additional commands, e-mail: users-help@grails.apache.org
>
Re: problem with Grails CLI and web plugin
Posted by James Daugherty <jd...@jdresources.net.INVALID>.
Thanks Carl. So in 7, we've been reworking our CLIs and are
experiencing some growing pains.
`grailsw` is the wrapper file that downloads `grails` to ~/.grails/ - it's
meant to be small so that it can be checked in as a convenience. I would
expect the same error since it should just be a passthrough for the
grails-cli (`grails` command). This is good news!
So the real issue is with the `grails` command. The grails command was
added in 7 as a delegating CLI that can call either forge or the legacy
shell-cli. Forge was announced in Grails 6.x, but we realized that due to
tooling limitations that defaulting to forge on the CLI can cause
functional issues with IntelliJ. For this reason, in 7, we reverted the
default to the legacy cli. There is a longer term plan to add missing
features to forge so the legacy & delegating cli can be completely dropped.
As to your problem: If you run grails with a first argument of `-t forge` I
suspect this will work. The web plugin profile (used by the legacy shell)
was broken in the M4 and we've made changes that may fully fix it in the
M5. Assuming the forge argument works, let's retest this once the M5 is
out?
-James
On Mon, Jul 7, 2025 at 6:22 PM Carl Marcum <cm...@apache.org> wrote:
> Hi James,
>
> grails
> and
> ./grailsw
>
> Best regards,
>
> Carl
>
> On 7/6/25 11:54 AM, James Daugherty wrote:
> > Hi Carl,
> >
> > Can you provide the exact command you're using?
> >
> > Regards,
> > James
> >
> > On 2025/07/04 15:24:41 Carl Marcum wrote:
> >> Hi All,
> >>
> >> When I create a 7.0.0-M4 web plugin and try to get a Grails CLI with the
> >> Grails installed with sdkman or using the Grails wrapper I get:
> >> | Error Error initializing classpath: Multiple builders are available to
> >> build a model of type 'org.grails.gradle.plugin.model.GrailsClasspath'.
> >> At first I thought it might be due having multiple Grails or Gradle
> >> installed but even after uninstalling all of both and using the wrapper
> >> I still got it.
> >> No issues the the web application.
> >> Any ideas what to check or how to get more output?
> >>
> >> BTW, no additional features selected. Gorm Hibernate, Tomcat, Spock,
> Java 21
> >>
> >> Thanks,
> >> Carl
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@grails.apache.org
> >> For additional commands, e-mail: users-help@grails.apache.org
> >>
> >>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@grails.apache.org
> > For additional commands, e-mail: users-help@grails.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@grails.apache.org
> For additional commands, e-mail: users-help@grails.apache.org
>
>
Re: problem with Grails CLI and web plugin
Posted by Carl Marcum <cm...@apache.org>.
Hi James,
grails
and
./grailsw
Best regards,
Carl
On 7/6/25 11:54 AM, James Daugherty wrote:
> Hi Carl,
>
> Can you provide the exact command you're using?
>
> Regards,
> James
>
> On 2025/07/04 15:24:41 Carl Marcum wrote:
>> Hi All,
>>
>> When I create a 7.0.0-M4 web plugin and try to get a Grails CLI with the
>> Grails installed with sdkman or using the Grails wrapper I get:
>> | Error Error initializing classpath: Multiple builders are available to
>> build a model of type 'org.grails.gradle.plugin.model.GrailsClasspath'.
>> At first I thought it might be due having multiple Grails or Gradle
>> installed but even after uninstalling all of both and using the wrapper
>> I still got it.
>> No issues the the web application.
>> Any ideas what to check or how to get more output?
>>
>> BTW, no additional features selected. Gorm Hibernate, Tomcat, Spock, Java 21
>>
>> Thanks,
>> Carl
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@grails.apache.org
>> For additional commands, e-mail: users-help@grails.apache.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@grails.apache.org
> For additional commands, e-mail: users-help@grails.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@grails.apache.org
For additional commands, e-mail: users-help@grails.apache.org
Re: problem with Grails CLI and web plugin
Posted by James Daugherty <jd...@apache.org>.
Hi Carl,
Can you provide the exact command you're using?
Regards,
James
On 2025/07/04 15:24:41 Carl Marcum wrote:
> Hi All,
>
> When I create a 7.0.0-M4 web plugin and try to get a Grails CLI with the
> Grails installed with sdkman or using the Grails wrapper I get:
> | Error Error initializing classpath: Multiple builders are available to
> build a model of type 'org.grails.gradle.plugin.model.GrailsClasspath'.
> At first I thought it might be due having multiple Grails or Gradle
> installed but even after uninstalling all of both and using the wrapper
> I still got it.
> No issues the the web application.
> Any ideas what to check or how to get more output?
>
> BTW, no additional features selected. Gorm Hibernate, Tomcat, Spock, Java 21
>
> Thanks,
> Carl
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@grails.apache.org
> For additional commands, e-mail: users-help@grails.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@grails.apache.org
For additional commands, e-mail: users-help@grails.apache.org