grails 3: Error occurred running Grails CLI: No profile found for name [web] about grails-docker

[klausszilvas]

Have had the same Problem after working on the project for one year. Deleting the build/.dependencies file is the solution.

[puwanatfx]

https://www.malcontentboffin.com/2016/12/Grails-Error-Error-occurred-running-Grails-CLI-No-profile-found-for-name-web-.html

Sometimes after upgrading the version of Intelli-J that I'm using for development, when I try to run the command-line grails program, I receive the following error message:

Error occurred running Grails CLI: No profile found for name [web].

After searching around the web, I found that this was due to a problem with the build/.dependencies file located within your Grails project root. If you delete or rename this file, then run grails again, the dependencies will be corrected and you can run your app.

[slackboxster]

Hey, @ortimanu, I just had the same issue trying to run this image locally with a grails application. It runs fine if I check out a clean instance of the repo for my grails app, but subsequent runs cause the issue. I fixed the issue by doing an rm -rf on the build directory in my grails repository.
I'm running the following command:
docker run -v /Users/ryan/build/complete-sso-api/:/app:rw -p 8080:8080 --name grails mozart/grails:3.1.0.RC2 run-app

[erichmx]

@c256985 it is the default error you get when you run grails run-app in an empty (or non grails) folder.

Try sudo rm -R .gradle and sudo rm -R build

[erichmx]

To improve the situation you can set the GRADLE_USER_HOME env var, with that you don't have to rm you build directory everytime you run docker, just before the first time, actually with deleting the build/.dependencies file does the trick

VOLUME ["/gradle"]
ENV GRADLE_USER_HOME /gradle

[acrive82]

This is problem depends from this grails/grails-core#10877. If you try the workaround in build.gradle, grails starts.

This is the workaround:

String.metaClass.uncapitalize = {
    if (delegate.length() <= 1) return delegate.toLowerCase()
    return delegate[0].toLowerCase() + delegate[1..-1]
}

[mortizbey]

Hi @edwardotis ! Will check this ASAP and let you know! Thanks!

[edwardotis]

Here you go:
http://stackoverflow.com/a/36512629/258896

[mortizbey]

@edwardotis please can you send us the full command you are using to run this image?

[edwardotis]

It's really a grails 3.1.x issue. It's more different than 3.0 than I had realized. Especially regarding the profiles. Your image is fine for 3.0. But I believe a separate image has to be made to support 3.1.

[mortizbey]

It works for me with 3.1.x, that's why I am asking for the command so I can see if there is any problems with it.

[mortizbey]

Hi @edwardotis may I close this issue? Does it need any more work or clarification?

[Pereitor]

Just had the same problem. Moved from a Linux-based machine with Grails 3.2.1 to a Grails 3.2.2 Windows 7 x64.

[c256985]

I've tried cleaning, and re-running but the problem still occurs.

The stacktrace points to GrailsCli:519.

What I don't understand is where it got the idea that I'm running a web profile. I'm actually running a rest-api profile. So this should never happen.

[c256985]

@erichmx I moved these directories, but had the same problem.

[lalitvchau]

This error to due to maven was installed in you system..

follow the below steps

1. delete the c:\Users.m2 or related directory in windows (Not sure about Unix or Mac but you can find the local cache of maven. Delete .m2 directory)
2. delete maven related environment variable.
3. delete ./gradlew
4. delete environment variable related to groovy also

try to above step.. it will work fine