This message was deleted.
# questions
s
This message was deleted.
p
Do you mean that a newly created Grails 6.1.1 do not work with M1 Mac?
s
I think the confusion was when I used the 6.1.1 command line versus using the grails forge website for a new app (grails forge produces the correct config for an M1 on the latest chromedriver and webdriver binaries version)
Creating an app with the command line defaulted the config to chromedriver '2.45.0' and build command error (not it would run fine)
p
Here is an example application created from the CLI on M1 Mac. https://github.com/puneetbehl/helloworld
I believe the Grails Application Forge, and the CLI should generate the same application.
I think one of the challenge of using the Gradle webdriver-binaries plugin is that the
chromeDriverVersion
gets outdated quickly with host updating the Chrome.
👍 1
s
One quick question @puneetbehl: with grails 6.1.1, when I run
grails create-app helloworld
from the command line using Java 11, I don't get the same project as the one you linked in github. The project that gets created locally has an older looking build.gradle and no buildSrc directory and no grails-cli.yml. Did you run the create-app with a different set of options locally? I just want to make sure I'm not missing anything in my local setup switching from 5.2.5 to 6.1.1.
p
That's weird! Can you please verify the output of
grails --version
? It might be that you have an older version of Grails picked up from the classpath.
s
It shows 6.1.1:
| Grails Version: 6.1.1
| JVM Version: 11.0.22
I'll keep looking to see if any older files might be lingering somewhere
p
How did you install the version 6.1.1? SDKMan? If yes, please try to uninstall with cmd
sdk uninstall grails 6.1.1
and then reinstall.
👍 1
s
Wasn't using SDKMan for this, just downloaded the grails-6.1.1.zip directly form the grails website. Will try on a different laptop later this week, but appreciate the help!
p
Thank you, Please feel free to report an issue once you know how we can replicate it.