Skip to content
This repository has been archived by the owner on Oct 24, 2022. It is now read-only.

Investigate issues with local dependency jars not being picked up #286

Open
jkinkead opened this issue Apr 4, 2017 · 3 comments
Open

Investigate issues with local dependency jars not being picked up #286

jkinkead opened this issue Apr 4, 2017 · 3 comments
Assignees

Comments

@jkinkead
Copy link
Contributor

jkinkead commented Apr 4, 2017

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 .

@jkinkead jkinkead self-assigned this Apr 4, 2017
@jkinkead
Copy link
Contributor Author

jkinkead commented Apr 5, 2017

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.

@splittingfield
Copy link

splittingfield commented Apr 5, 2017 via email

@jkinkead
Copy link
Contributor Author

jkinkead commented Apr 5, 2017

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants