I have to say I'm getting rather frustrated with m...
# questions
j
I have to say I'm getting rather frustrated with my attempts to test out Grails 7.0.0-M5 with the conversion of a pretty simple Grails 6 app. I've got it to compile but I can't get it to run - I've run into error after error, which I'll post about in another message. I wondered whether my problems might be caused by using Application Forge - I generated the shell of the app (build.gradle, etc.) with that and then copied over the actual source code of my app and added dependencies to build.gradle. So I thought I'd try another approach, simply using 'grails create-app', and even this generates a bunch of errors (although the app does get created). Can anyone explain what's going on here? $ grails create-app newapp Resolving dependencies............... Error | [main] INFO org.eclipse.aether.internal.impl.DefaultArtifactResolver - Artifact org.fusesource.jansijansipom:1.18 is present in the local repository, but cached from a remote repository ID that is unavailable in current build context, verifying that is downloadable from [apacheRepository (https://repository.apache.org/content/groups/public, default, releases+snapshots), grailsRepo (https://repo.grails.org/grails/restricted, default, releases+snapshots), central (https://repo.maven.apache.org/maven2, default, releases)] Error | [main] INFO org.eclipse.aether.internal.impl.DefaultArtifactResolver - Artifact org.fusesource.jansijansipom:1.18 is present in the local repository, but cached from a remote repository ID that is unavailable in current build context, verifying that is downloadable from [apacheRepository (https://repository.apache.org/content/groups/public, default, releases+snapshots), grailsRepo (https://repo.grails.org/grails/restricted, default, releases+snapshots), central (https://repo.maven.apache.org/maven2, default, releases)] .maven.apache.org/maven2, default, releases)] ...and a bunch of similar messages
👍 1
j
These "is present in the local repository, but cached from a remote repository ID that is unavailable in current build context, verifying that is downloadable from" messages are benign and only appear once, although we did not expect to see to see them at all with M5. https://github.com/apache/grails-core/issues/14854 If you rerun grails in the newapp directory, you will not see them again.
j
OK, thanks!
j
@James Fredley Because we switched and switched back I think we were expecting possibly one more round of these messages
if this happens in the rc1 we will have to reevaluate
👍 1