Implementation vs API using maven dependency
up vote
1
down vote
favorite
I have a utility library that I have pushed to a JFrog artifactory.
Now I am able to include that library in another project through gradle implementation (Not including it as a submodule, but getting it from local maven repo).
My question is the utility library uses some other libraries which my main project also requires.
Now, in my understanding using "api" with internal dependencies of my utility library, should have allowed those dependencies to be available to my main project, but it's not happening.
I wanted some clarification on this as to how I can allow my library internal dependencies to be available to my main project. Because, otherwise I will just be importing them again in my main project, which I do not want to do.
android maven gradle asked Nov 12 at 5:55
Farooq Arshed
1,17821222
add a comment |
up vote
1
down vote
favorite
I have a utility library that I have pushed to a JFrog artifactory.
Now I am able to include that library in another project through gradle implementation (Not including it as a submodule, but getting it from local maven repo).
My question is the utility library uses some other libraries which my main project also requires.
Now, in my understanding using "api" with internal dependencies of my utility library, should have allowed those dependencies to be available to my main project, but it's not happening.
I wanted some clarification on this as to how I can allow my library internal dependencies to be available to my main project. Because, otherwise I will just be importing them again in my main project, which I do not want to do.
android maven gradle asked Nov 12 at 5:55
Farooq Arshed
1,17821222
2
If your module directly depends on a library it is better to add it as a dependency in the module. Don't rely that some other library will bring it in.
– Henry
Nov 12 at 6:12
@Henry Yes, this can be done. But since it's my internal library I can control when to update it.
– Farooq Arshed
Nov 12 at 6:15
are you using Gradle Java library plugin ? in this case, difference between API and Implementation dependencies is well explained here : docs.gradle.org/current/userguide/… . You should check in the generated pom.xml file of your library (after publishing it to a maven repo): the "scope" of each dependency will depend on the type of dependency defined in gradle script.
– M.Ricciuti
Nov 12 at 6:37
@FarooqArshed No matter if it is your internal library or not. Your are asking a question an Henry told you the only correct answer: a (sub)project should define all its direct dependencies needed, in the matching scope.
– Frito
Nov 12 at 8:27
hmmm. Thanks guys.
– Farooq Arshed
Nov 12 at 9:28
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have a utility library that I have pushed to a JFrog artifactory.
Now I am able to include that library in another project through gradle implementation (Not including it as a submodule, but getting it from local maven repo).
My question is the utility library uses some other libraries which my main project also requires.
Now, in my understanding using "api" with internal dependencies of my utility library, should have allowed those dependencies to be available to my main project, but it's not happening.
I wanted some clarification on this as to how I can allow my library internal dependencies to be available to my main project. Because, otherwise I will just be importing them again in my main project, which I do not want to do.
android maven gradle asked Nov 12 at 5:55
Farooq Arshed
1,17821222
I have a utility library that I have pushed to a JFrog artifactory.
Now I am able to include that library in another project through gradle implementation (Not including it as a submodule, but getting it from local maven repo).
My question is the utility library uses some other libraries which my main project also requires.
Now, in my understanding using "api" with internal dependencies of my utility library, should have allowed those dependencies to be available to my main project, but it's not happening.
I wanted some clarification on this as to how I can allow my library internal dependencies to be available to my main project. Because, otherwise I will just be importing them again in my main project, which I do not want to do.
android maven gradle android maven gradle asked Nov 12 at 5:55
Farooq Arshed
1,17821222
asked Nov 12 at 5:55
Farooq Arshed
1,17821222
asked Nov 12 at 5:55
Farooq Arshed
1,17821222
asked Nov 12 at 5:55
Farooq Arshed
1,17821222
asked Nov 12 at 5:55
Farooq Arshed
1,17821222
1,17821222
2
If your module directly depends on a library it is better to add it as a dependency in the module. Don't rely that some other library will bring it in.
– Henry
Nov 12 at 6:12
@Henry Yes, this can be done. But since it's my internal library I can control when to update it.
– Farooq Arshed
Nov 12 at 6:15
are you using Gradle Java library plugin ? in this case, difference between API and Implementation dependencies is well explained here : docs.gradle.org/current/userguide/… . You should check in the generated pom.xml file of your library (after publishing it to a maven repo): the "scope" of each dependency will depend on the type of dependency defined in gradle script.
– M.Ricciuti
Nov 12 at 6:37
@FarooqArshed No matter if it is your internal library or not. Your are asking a question an Henry told you the only correct answer: a (sub)project should define all its direct dependencies needed, in the matching scope.
– Frito
Nov 12 at 8:27
hmmm. Thanks guys.
– Farooq Arshed
Nov 12 at 9:28
add a comment |
2
If your module directly depends on a library it is better to add it as a dependency in the module. Don't rely that some other library will bring it in.
– Henry
Nov 12 at 6:12
@Henry Yes, this can be done. But since it's my internal library I can control when to update it.
– Farooq Arshed
Nov 12 at 6:15
are you using Gradle Java library plugin ? in this case, difference between API and Implementation dependencies is well explained here : docs.gradle.org/current/userguide/… . You should check in the generated pom.xml file of your library (after publishing it to a maven repo): the "scope" of each dependency will depend on the type of dependency defined in gradle script.
– M.Ricciuti
Nov 12 at 6:37
@FarooqArshed No matter if it is your internal library or not. Your are asking a question an Henry told you the only correct answer: a (sub)project should define all its direct dependencies needed, in the matching scope.
– Frito
Nov 12 at 8:27
hmmm. Thanks guys.
– Farooq Arshed
Nov 12 at 9:28
2
2
If your module directly depends on a library it is better to add it as a dependency in the module. Don't rely that some other library will bring it in.
– Henry
Nov 12 at 6:12
If your module directly depends on a library it is better to add it as a dependency in the module. Don't rely that some other library will bring it in.
– Henry
Nov 12 at 6:12
@Henry Yes, this can be done. But since it's my internal library I can control when to update it.
– Farooq Arshed
Nov 12 at 6:15
@Henry Yes, this can be done. But since it's my internal library I can control when to update it.
– Farooq Arshed
Nov 12 at 6:15
are you using Gradle Java library plugin ? in this case, difference between API and Implementation dependencies is well explained here : docs.gradle.org/current/userguide/… . You should check in the generated pom.xml file of your library (after publishing it to a maven repo): the "scope" of each dependency will depend on the type of dependency defined in gradle script.
– M.Ricciuti
Nov 12 at 6:37
are you using Gradle Java library plugin ? in this case, difference between API and Implementation dependencies is well explained here : docs.gradle.org/current/userguide/… . You should check in the generated pom.xml file of your library (after publishing it to a maven repo): the "scope" of each dependency will depend on the type of dependency defined in gradle script.
– M.Ricciuti
Nov 12 at 6:37
@FarooqArshed No matter if it is your internal library or not. Your are asking a question an Henry told you the only correct answer: a (sub)project should define all its direct dependencies needed, in the matching scope.
– Frito
Nov 12 at 8:27
@FarooqArshed No matter if it is your internal library or not. Your are asking a question an Henry told you the only correct answer: a (sub)project should define all its direct dependencies needed, in the matching scope.
– Frito
Nov 12 at 8:27
hmmm. Thanks guys.
– Farooq Arshed
Nov 12 at 9:28
hmmm. Thanks guys.
– Farooq Arshed
Nov 12 at 9:28
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53256559%2fimplementation-vs-api-using-maven-dependency%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53256559%2fimplementation-vs-api-using-maven-dependency%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
If your module directly depends on a library it is better to add it as a dependency in the module. Don't rely that some other library will bring it in.
– Henry
Nov 12 at 6:12
@Henry Yes, this can be done. But since it's my internal library I can control when to update it.
– Farooq Arshed
Nov 12 at 6:15
are you using Gradle Java library plugin ? in this case, difference between API and Implementation dependencies is well explained here : docs.gradle.org/current/userguide/… . You should check in the generated pom.xml file of your library (after publishing it to a maven repo): the "scope" of each dependency will depend on the type of dependency defined in gradle script.
– M.Ricciuti
Nov 12 at 6:37
@FarooqArshed No matter if it is your internal library or not. Your are asking a question an Henry told you the only correct answer: a (sub)project should define all its direct dependencies needed, in the matching scope.
– Frito
Nov 12 at 8:27
hmmm. Thanks guys.
– Farooq Arshed
Nov 12 at 9:28