You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 24, 2022. It is now read-only.
I'm unable to reproduce trivially, and I don't see any code that would produce missing jars. If you could provide a reproduction case, that would help.
On Apr 4, 2017, at 6:00 PM, Jesse Kinkead ***@***.***> wrote:
I'm unable to reproduce trivially, and I don't see any code that would produce missing jars. If you could provide a reproduction case, that would help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Pointers to specific subprojects where this occurs (especially with the relevant commit triggering it, and the missing jar name) would also be quite helpful.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sometimes local dependency jars are not getting built into a Docker image.
@aimichal / @OyvindTafjord for any concrete examples.
I suspect this might happen deterministically when adding new local dependencies, but I'll confirm upon investigation.
FYI @splittingfield .
The text was updated successfully, but these errors were encountered: