AbstractMethodError using gradle 4.5 #177
Comments
|
Any chance of this being looked at soon ? |
|
We are aware of that issue.
But unfortunately I haven't found a good solution yet.
I really don't want to add a new workaround for that again. But it seems we
have to...
…On Mar 2, 2018 9:14 AM, "jsalerno" ***@***.***> wrote:
Any chance of this being looked at soon ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#177 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJwYewmUh-f8OFKqXMihay5GDZWpEZbEks5taP9ygaJpZM4R0qyf>
.
|
|
Gradle 4.6 is also affected. |
|
Thanks for the heads-up @YuriDenison, I will try to spend sometime this weekend to find a workaround for this issue, as we definitely don't want to stay behind in terms of Gradle versions supported. |
|
Gradle 4.8 should also be supported, it is a requirement for upcoming Android Gradle plugin 3.3.0. |
|
Hey guys 👋 |
|
+1 had to downgrade from Gradle 4.8 to 4.4 to get around this |
|
You could try this plugin:
https://github.com/StefMa/bintray-release
Its not a simple fork but a new implementation.
Give it a try with a higher Gradle version...
…On Fri, Jul 20, 2018, 10:58 PM Aidan Follestad ***@***.***> wrote:
+1 had to downgrade from Gradle 4.8 to 4.4 to get around this
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#177 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJwYe-yQwa5kAjYngf6w0bTSS3GL9Pjiks5uIkRhgaJpZM4R0qyf>
.
|
|
Any updates on this particular plugin? |
|
Would also like to know of any updates as this stops the use of the latest android plugins. I did try the other plugin suggested but got a whole host of other issues instead. |
|
I switched to https://github.com/bintray/gradle-bintray-plugin and it works great, but it's hard to configure. |
Hey @mattmook can you create an issue at https://github.com/StefMa/bintray-release and describe the issues your faced? That would help me!
These bintray-release Plugins uses these internally. But also streamline the process of set the artifacts up. So of course you could do that. But you blow up your build script files a lot! |
|
I switched to https://github.com/bintray/gradle-bintray-plugin and it works great, but it's hard to configure. |
|
I'm not sure what the cause is but for some reason, when we add the plugin first before the library plugin, it seems to work. if work for you visit my page :-) |
|
@RurioLuca you are the second user raising the same thing, I will take a look today and try to understand what is really happening. Could you confirm that you can actually upload the artifacts to bintray just fine? Because I would expect the POM file won't be generated correctly (ie: it will be missing the dependencies of your library, which is the whole reason why this plugin exists in the first place). Which of your projects can we look at to reproduce what you stated above? |
|
BTW I can confirm that the issue is that the POM file in my tests is basically missing the @RurioLuca it would be great if you could confirm the above or if you could provide more detailed info for your usecase. |
|
I'm out for the weekend, on monday I send you the link of my repository(i need to pusher), you'll see that reversing the dependencies you get this error.also I have another repositories that works correctly with dependencies in the correct order, I do not understand why on one I needed to reverse the plugins and on the other not |
|
I'm having several problems upload on bintrat. inverting the order of the plugins you get the error in question. Now however I could not upload bintrat, the library has about 7 versions published, I get an error which at the moment I have not found a solution: Bintray-uplopad: Could not find publication: release I have some other repositories that I updated last week and your library worked perfectly. I hope it helps you. |
|
@RurioLuca thanks. If your project has no external dependencies apart from the Android framework then you should be fine, but that is just coincidence, as the plugin unfortunately is still broken when used on Android libraries while building with Gradle 4.5+ The problem about having correct support for android libraries is that the plugin needs to generate the right POM file in order to allow consumers to automatically resolve dependencies as needed (eg: https://bintray.com/novoda/snapshots/download_file?file_path=com%2Fnovoda%2Fdownload-manager%2FSNAPSHOT-18%2Fdownload-manager-SNAPSHOT-18.pom). The issue lives within the missing support for Android in the I have spent some time yesterday to work out on an alternative, scalable solution (as working on #232 unfortunately highlighted other breaking changes in Gradle internal API in 4.8 and 4.10). I am waiting for GH to get back to a normal stage and have the other pending PRs reviewed before starting pushing this solution. |
|
Fixed in |
After updating gradle to version 4.5 the plugin doesn't work anymore. Error:
Stacktrace:
Interface
UsageContexthas been changed.The text was updated successfully, but these errors were encountered: