grails-core: Fresh Grails 3.3.2 grails run-app does not start
Task List
- Steps to reproduce provided
- Stacktrace (if present) provided
- Example that reproduces the problem uploaded to Github
- Full description of the issue provided (see below)
Steps to Reproduce
$ sdk use grails 3.3.2
Using grails version 3.3.2 in this shell.
$ grails create-app foobar
| Application created at /Users/erichelgeson/source/foobar
$ cd foobar
$ grails run-app
| Resolving Dependencies. Please wait...
Cannot resolve reloading agent JAR: Could not resolve all dependencies for configuration ':agent'.
FAILURE: Build failed with an exception.
* Where:
Build file '/Users/erichelgeson/source/foobar/build.gradle' line: 22
* What went wrong:
A problem occurred evaluating root project 'foobar'.
> Failed to apply plugin [id 'com.energizedwork.webdriver-binaries']
> No signature of method: java.lang.String.uncapitalize() is applicable for argument types: () values: []
Possible solutions: capitalize()
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
CONFIGURE FAILED
Total time: 5.535 secs
| Error Error initializing classpath: No signature of method: java.lang.String.uncapitalize() is applicable for argument types: () values: []
Possible solutions: capitalize() (Use --stacktrace to see the full trace)
Expected Behaviour
App should run
Actual Behaviour
App exits with exception
Work around
Note bootRun
does work.
Remove new gradle plugin causing issues com.energizedwork.webdriver-binaries
Environment Information
- Operating System:
MacOS 10.12.6
- Grails Version: 3.3.2
- JDK Version: 8u111
- Container Version (If Applicable): n/a
Example Application
n/a
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 15 (12 by maintainers)
Commits related to this issue
- Update webdriver-binaries version to 1.2 Compatible with Gradle 3.3.0 See: https://github.com/grails/grails-core/issues/10877 — committed to grails-profiles/base by sdelamo 7 years ago
This error to due to maven was installed in you system…
follow the below steps
try to above step… it will work fine
After talking to @jameskleeh at G3Summit this should probably be re-opened as the behavior is odd and provides indication of whats happening to the user. I actually saw 2 people at the conference have this issue, and have seen a few people in slack have it as well.
Check your current installed version of Gradle via SDKman. It may be the version you have is incompatible.