Change implementation to api in build.gradle.kts so subdependencies are exposed#78
Merged
Conversation
Contributor
Author
|
CC @lilgallon |
|
Member
|
Thanks for your contribution, I am not sure about exposing ocpp-version specific modules. I will talk with my team about that |
Contributor
Author
|
@lilgallon I'm actually quite sure you need it. |
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For now I changed all of them to use
api, even though for my own use case I don't need all of them to be exposed, but I suspect sooner or later someone else will want to use classes in any of these modules anyway.Thoughts?
Fixes #54