-
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
Unable to resolve dependencies -- https://repo.grails.org/grails/core returns 404 #11825
Comments
Facing same issue when created a new Grails App with vue profile and try to run up `
Possible solution:
` |
grailsCentral (https://repo.grails.org/grails/core) appears to be down. It simply returns:
|
It seems like somehow artifactory URL is changed to https://repo.grails.org/artifactory/core |
@puneetbehl unfortunately this prevents even basic operations like "help" or just createing a new app from the CLI:
|
Thanks |
Workaround for existing projects:
the problem can be solved. Under linux a simple Workaround for new projects
After creating the new project, you still have to fix the DISCLAIMER:
|
Unfortunately the old URL is hardcoded in the grails wrapper. See |
@cosenmarco We do not intend for this URL change to be permanent. We have reached out to JFrog for assistance with this issue. We'll update here when we have more information. |
@JasonTypesCodes Thank you for looking into this issue. |
We do not yet have a timeline for resolution. We'll update here once we do. |
Alright. I was more for giving the ability to override in case this happens again / one wants to use a caching proxy... I'll be waiting for a resolutions with our pipelines in a broken state... |
Can't even run my projects. This is a blocking issue. Any workaround for existing projects?? Thanks in advance. |
I believe all of the artifacts should be available at https://repo.grails.org/artifactory/core for now. |
@jeffbrown still not able to access some artifacts:
|
@jrAtAustin The dependencies you show there look like app dependencies bu the |
@jeffbrown I was trying to build the Spring Security Oath 2 Okta plugin located here: https://github.com/moksamedia/okta-oauth2-service Below is build.gradle
|
Ah, I think I got it. Thanks @jeffbrown and others!
|
We also had some failures with our CI today and had to make some change outside of the gradle file. We ended up forking grails-wrapper and updating the urls:
We then ran the travis-build.sh and took the jar file from Hopefully this is ok to post here for those experiencing issues beyond the local url change workaround. |
Affects legacy apps also. Grails 2 plugins are missing. Is there a workaround for Grails 2 apps?
|
Using |
it work, thanks |
Grails 2.3 workaround seems to be to do:
Grails 2.5 workaround seems to be to do:
That overrides the defaults supplied by |
Grails 3 projects are building properly for me but I am still unable to build Grails 2 projects. I'm getting the following when trying to run:
One thing I noticed is that 'http://repo.grails.org/grails/plugins' redirects to 'https://repo.grails.org/artifactory/plugins/' when the trailing slash is omitted which it seems to be for Grails 2. |
@danieljoeblack I've been unable to recreate this in Grails 2.5.6 with standard configuration, but I suspect explicitly using |
@JasonTypesCodes I'm running 2.3.9 for the record. When I explicitly set the repo url to
Changing it to
Was the repo URL accessible via http before? It seems to force https now... |
@luiszimmermann We were running into this yesterday and this is the workaround we used #11825 (comment) |
@danieljoeblack I have also faced same issue on Grails 2.3.11 as well. It looks more like SSL related in Java7. I have tried things but didn't get it working yet. Did you get any clue?
|
@danieljoeblack for me adding following repo worked in Grails 2.3.1
and with following command worked using Java7
|
FYI - we're now getting 503 from non-artifactory URLs now, and have had to completely remove those references in order to build our apps:
|
The 503s and the 404s that followed were due to an unrelated and unplanned outage and should no longer be occurring. We are working closely with JFrog on these issues. |
I am having the same issue with grails 4.0.1
Does not help. Works perfectly fine on local, but fails on CI. |
Is that the wrapper already downloaded locally but not on CI? |
In Grails 2.4.4 I am using this: And get this error: |
Nope, the wrapper is committed with the code. |
Will the old |
@jeffbrown now both URL's are not available. So, basically, nothing works. even the workaround. |
@ShurikAg Thank you, we are aware of current issues with the JFrog artifactory and we are in touch with the JFrog team to help us get the artifactory back online. We will share the further updates as soon as we get them. Sorry for the inconvenience. |
Thank you! Is there any workaround for now? Or there is nothing to do? |
The repository is currently back online. Thank you everyone for your patience as we work through these issues. |
@JasonTypesCodes will the old http urls be restored, or do we need to keep the workarounds for Grails 2.x? |
@martin-walsh That is a detail we are still working through. If the repository does revert back to responding to HTTP requests without a redirect, it will likely be for a limited period to allow a more graceful transition to HTTPS. What version of Grails 2 are you running, and have you had to take actions beyond changing your repositories to |
@JasonTypesCodes Running both 2.3.11 & 2.5.4. Taking no action beyond overriding the definition of The workaround is very simple to apply, but I am wondering if we should plan to apply it permanently as the challenge my organisation faces is 100+ grails projects that need updating. It is not a deal breaker, just something that needs to be done if |
@martin-walsh Thank you, that is good information to have. If the HTTP URLs do resume working without a redirect that will be for a limited period. I would not suggest reverting any updates you have already made to the HTTPS repository URLs. I would also strongly consider taking the time to update your remaining applications. |
@jeffbrown @puneetbehl Here is my current
|
@ShurikAg This looks similar to the error we were running into. It's probably because the grails wrapper inside of your repository has the typos. Here are the steps that we took to resolve #11825 (comment) |
Oh wow! Though, I am running Grails 4. Does it make a difference? |
@ShurikAg That wrapper error can be resolved by using an updated grails-wrapper.jar. Please see: https://grails.org/blog/2021-06-10-grails-wrapper-update.html The issue for this bug is here: grails/grails-wrapper#7 |
I think we can close this issue. If additional problems are encountered, please open a new issue. Thank you. |
Hi All, I am observing the similar kind of issue with grails version 2.4.0. I am getting the below error during generation of WAR file: The error is observed immediately after the execution of grails -clean command. I have followed all the suggestions mentioned in various comments and modified the BuildConfig.groovy file, but the result is same and everytime I am getting this issue in downloading the grails dependencies. I even tried adding the maven repos - mavenRepo "https://repo.grails.org/artifactory/core/" and mavenRepo "https://repo.grails.org/artifactory/plugins/" as mentioned in https://github.com/GMOD/Apollo/pull/2624/files; but no luck. Can you please check and help me out with this issue? I am not able to proceed with the WAR file generation. Thanks! |
Go to start.grails.org, download an app.
Unzip it and run
./gradlew help
The text was updated successfully, but these errors were encountered: