-
Notifications
You must be signed in to change notification settings - Fork 153
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
Gradle plugin 4.4.0 breaks with Gradle > 2.5 #86
Comments
Fails to find artifacts on 4.4, see jfrog/build-info#86
Has there been any progress on a longer term solution other than just downgrading the plugin? |
FYI, through much experimentation, I found that I get this error when any subproject (A) depends on another subproject (B) if B.name sorts alphabetically after A.name. I.e. I have been able to consistently show this by doing nothing other than renaming subprojects. Seems to be an issue in 4.4.0 and above. 4.3.0 does not appear to have this problem. |
This is an issue in 4.7.1 as well |
👍 |
Is someone looking at this issue? |
Hi @mpapirkovskyy |
Configuration on demand + the JFrog plugin seems to cause Gradle sync issues in Android Studio. Disabling this option and disabling the Configure on Demand setting in Android Studio preferences fixes the issue. This project doesn't need Configure on Demand anyway, so there's no downside to disabling this option, even if Gradle and JFrog come up with a different workaround later. For more details, see: jfrog/build-info#86
Configuration on demand + the JFrog plugin seems to cause Gradle sync issues in Android Studio. Disabling this option and disabling the Configure on Demand setting in Android Studio preferences fixes the issue. This project doesn't need Configure on Demand anyway, so there's no downside to disabling this option, even if Gradle and JFrog come up with a different workaround later. For more details, see: jfrog/build-info#86
Configuration on demand + the JFrog plugin seems to cause Gradle sync issues in Android Studio. Disabling this option and disabling the Configure on Demand setting in Android Studio preferences fixes the issue. This project doesn't need Configure on Demand anyway, so there's no downside to disabling this option, even if Gradle and JFrog come up with a different workaround later. For more details, see: jfrog/build-info#86
Hi @mpapirkovskyy Thanks, |
I still see the same error using 4.7.3 in combination with org.gradle.configureondemand=true. |
@d1ss0nanz thank you for reproting this. I think that this is related to a known issue with configure on demand that we have asked assistance from Gradle team. The issue can be found here: gradle/gradle#4783 |
@AlexeiVainshtein thanks, seems to work, I will update plugin and test other configurations now. |
Thanks @mpapirkovskyy |
4.7.3 seems to fix it for me after reproducing with 4.7.2 |
@AlexeiVainshtein Did you see the comment from the Gradle guys: |
Jenkins Pipeline - New declarative-example and examples improvements.
Using
org.jfrog.buildinfo:build-info-extractor-gradle:4.4.0
, starting with Gradle 2.6 up to 2.14 and 3.0-milestone-2, we get the following error:Cannot notify listeners of type ProjectEvaluationListener as these listeners are already being notified.
It works well using
org.jfrog.buildinfo:build-info-extractor-gradle:4.3.0
.This issue was originally reported in the Gradle forums.
One of the reporter kindly put up a reproducer project.
Here is the complete stacktrace with Gradle 2.14:
The text was updated successfully, but these errors were encountered: