-
Notifications
You must be signed in to change notification settings - Fork 950
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can not create-app using grails 2.5.5 #10011
Comments
I see that i have /Users/sudhir/.sdkman/candidates/grails/2.5.5/lib/org.codehaus.groovy/groovy-all/jars/groovy-all-2.4.5.jar available instead of /Users/sudhir/.sdkman/candidates/grails/2.5.5/lib/org.codehaus.groovy/groovy-all/jars/groovy-all-2.4.4.jar |
I can't reproduce this personally |
i just installed a fresh 2.5.5 copy using sdk man, tried to create a sample app, and it failed with above error, also i dont have groovy-all 2.4.4 jar at the location it is looking for (inside grails-home/lib/xxx) - instead there's 2.4.5 jar available at tht location |
Ok, so i downloaded and manually put the 2.4.4 jar at the location it was expecting and it worked. |
Just a note: before i did create-app - i did grails compile (after changing grails.version to 2.5.5 in application.properties) on one of the old project which was on grails 2.4.4. if that makes any difference. |
I also cannot reproduce this problem. |
Grails 2.5.5 uses Groovy 2.4.5. The errors above indicate that Grails is looking for Groovy 2.4.4. It looks like your environment somehow got confused. |
@jeffbrown i had the issue, i dont know how come i had no groovy 2.4.4 in /Users/sudhir/.sdkman/candidates/grails/2.5.5/lib/org.codehaus.groovy/groovy-all/jars .. (instead i had groovy 2.4.5 jar there) I just manually put the groovy 2.4.4 jar there, and i am good. if you want you can close the issue.. but it was definitely looking for groovy 2.4.4 |
That is expected:
|
Ah okay, so from logs, you can see grails was looking for groovy 2.4.4 - its a freshly installed grails using sdkman |
Yes, I see that. I don't know why that is though and can't reproduce it. |
Can you try this?
And let us know if the problem persists? |
Just tried, and works perfect, no idea what went wrong the first time.. |
Thanks for the feedback. |
I've run into a similar problem installing grails 2.5.5 via sdkman.
Same errors as snimavat
Removing the directory or running sdk rm grails 2.5.5 and trying again doesn't fix the problem.
repeat above Everything works fine with grails 2.5.4. I also have other versions of grails/groovy for other applications I work on. Same OS/versions as snimavat: A coworker can reproduce with Yosemite. |
Third time's the charm, and as soon as I posted this, it started working. The below fixed it for a coworker and me, though the previous suggestion did not: uninstall 2.5.5 with sdk or removing the candidate directory |
I also had the same problem. To work around this I did as @katherinessmith said and created a new app with Grails 2.5.4. If you want to reproduce this I guess a new Linux installation with openjdk should reproduce this. |
I can reproduce this issue on OS X El Capitan, fresh install of 2.5.5 from sdkman. |
Same problem here. The dependency report lists Groovy 2.4.4 as dependency of
So I think @jeffbrown is right with his comment (0ec157d#comments). There should be Groovy 2.4.5 in |
same problem installing with sdkman |
I doubt sdkman has anything to do with it. |
Was setting up a new linux vm, and same problem.. also removing and reinstalling doesnt help |
to follow up: using sdkman to install 2.5.4 first, and then 2.5.5 worked as suggested by @katherinessmith |
I have the same problem with an existing app, |
I'm facing the same issue. Although I haven't got to the bottom of it, I was able to figure out why this odd sequence with using version 2.5.4 and just then 2.5.5 works.
As I'm migrating some legacy app from grails 2.2.1 to 2.5.5 and this app didn't have maven set as dependency resolver, it has happened to me that the same issue manifested itself not only on groovy-all-2.4.4 but on other dependencies as well. Another evidence of the same issue 'fixed' with switching to maven resolver, this time failure was on cglib jar: One more evidence of the issue itself but as well multiple groovy-all versions dependency I mentioned above - here it's failing on groovy-all-2.4.5: |
EDIT: ok. The "fix" is to create a project with 2.5.4 and then you can create a project with 2.5.5 |
@rpalcolea Yes. See my comment at the bottom of 0ec157d |
Oops! didn't see that :( my mistake |
Same Problem here using manually downloaded zip under Windows 7 64bit / Oracle JDK 8. |
Is it going to be fixed in next 2.5.x ? |
if there is another 2.x release yes |
Can we have it fixed plz and a 2.5.6 release.. this is really painful to not to be able to create-app or plugins, or a hot fix or just a patch build.. Whts the use of 2.5.5 if devs cant create app/plugins without doing some hacks... and lots of ppl are facing this issue, there are questions on stackoverflow pointing to this ticket. |
+1 for 2.5.6 release. We shouldn't have to dirty up our grails installation because of a bug. |
|
still the same over here - also using sdkman. |
As a workaround, you can define an environment variable specifying the Groovy version:
|
Same issue on Windows and macOS, fresh install of 2.5.5 and |
Same issue here as well. |
Create a brand new docker container for 2.5.5 and trying to run grails console would fail with same error too. CI_GROOVY_VERSION=2.4.5 worked |
+1 for 2.5.6 ! Please. |
It does look like an old dependency declaration as Jeff noted. There are several workarounds:
FYI, I can reproduce this in docker: https://github.com/ColinHarrington/grails-10011 |
Thanks for the release @graemerocher |
|
@graemerocher
-- Install grails 2.5.5 using sdkman
-- run command
grails create-app
(or just start grails console using> grails
)The text was updated successfully, but these errors were encountered: