-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Multimodule project dependencies in a different layer #1724
Comments
Both make sense to me. Slight preference for (2). I vaguely remember someone was saying along the line snapshot dependencies and module dependencies may not be at the same level, but I may be wrong. This is to fix #1436. |
Okay so I guess here are my proposals for updating the JavaImageBuilder api, given that we're probably going with style (2) from above. JavaContainerBuilder.addDependencies(List<Path> dependencies) will become
or
|
I like (1). Hopefully this covers most of the use cases. |
Yeah this is opinionated, so I think it'll be fine. |
Yeah, I like 1 as well. |
For the purpose of this bug, we will call maven module and gradle sub-project dependencies "modules".
Current Layers
SNAPSHOT
)SNAPSHOT
)Proposed Layers (1): All module deps should be considered snapshots
But this can just be achieved by versioning any module as SNAPSHOT, so maybe there's no value in (1)
Proposed Layers (2): Module deps are their own layer
@GoogleContainerTools/java-tools-build What do you think? (2) sounds good to me
The text was updated successfully, but these errors were encountered: