-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
cordova build android : Could not find intellij-core.jar #521
Comments
I also got the same issue today :/ |
I got the same error but with the support-v4-27.1.1.jar. I was able to build a few days ago. |
Hi, There is a fix for it that should be implemented in cordovalib: Replace the order of repositories from: to: I think this fix should be also implemented in cordova |
working after an platform remove and add |
@mccob nope, not for me. The url of package is still broken. |
android target : cordova default cordova -v cordova platform list |
@mccob there is nothing changed in version 7.1.1 regarding this issue. You currently have cached gradle, therfore it working for you. On clean server or environment it won't work because the file doesn't exist (it was removed today, probably by mistake) |
it's working because I have updated build.gradle as you explain (after platform rm / add) |
@mccob this is temporary solution. Usually you shouldn't save the platform as part of you project and add it according to environment you running on. |
Part of the proposed change to move the Google Maven repo ahead of jcentre has already been made and released in cordova-android 7.1.1. However, the build.gradle file in the CordovaLib project did not get updated. We'll be doing further gradle updates in the next major version for compatibility with updated Android SDKs, so I'll make sure it gets fixed there. |
@dpogue can't it be a hotfix for current major version? I think it's very important to fix this issue |
It sounds like the root issue here is that stuff got published to bintray with broken dependencies. Changing the Cordova dependencies is working around the problem, but not actually fixing it (because it's entirely outside the scope of anything we can control). We can make the gradle file change and try to do a 7.1.2 release, but it's going to take at least a few days before that can be published. Speaking for myself, I won't be able to even start the release process and submit it to the list for voting until mid-next week at the earliest. |
thank you
see also another recent report of same issue : https://forum.ionicframework.com/t/ionic-pro-package-failed-after-successful-deploy/145355
The text was updated successfully, but these errors were encountered: