-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
Building fails due to afterEvaluate #275
Comments
I made a new project to reproduce but could not yet actually.
|
We've gotten rid of all the
OTOH, as it only happens with download = true it'd be great if you could see if that scenario also triggers it (although it seems very unlikely) so I suspect I'll have to dig around some and see if I can get it to reproduce
But on the bright side |
Hey, yes, we use I looked deeper and the weird thing is that introducing Jib is not enough but one must also have this kind of code:
Normally that works but now it doesn't with gradle-node-plugin. I'm not sure if removing I'll try to find a workaround, and keep you informed if any progress. Anyway, thank you for the 🏅 plugin! |
Maybe something from https://docs.gradle.org/current/userguide/cross_project_publications.html#sec:simple-sharing-artifacts-between-projects ? There's also https://www.youtube.com/watch?v=XCzyUESaBHQ which is a bit more exhaustive Now that I think of it, this is probably something that should go into the example projects |
Yup, that's the way we are sharing the artifact. Didn't yet watch the video, but thank you for that, happily will deepen my understanding on this front. FWIW:
I'll get back to you if I find it, but now I will treat it as some kind of indeterministic caching issue. |
afterEvaluate
is causing me problems in existing project that works — until I include Google Jib to the build process.Build fails
Gradle configuration in Kotlin
In a gradle project that includes the frontend assets via Jib we have this:
The build fails even without actually referencing to that
frontendBuildArchive
in Jib configuration (not shown here).In frontend gradle project we have this:
Related issue
Perhaps related to this: #39
Environment:
The text was updated successfully, but these errors were encountered: