Create android project with multiple modules (libraries) and use different git repo for each module
i'm building android SDK (library) which should be divided into 2 parts (core functionality and core-extensions) also need to create sample app to demonstrate basic usage of the library, sample app should usage both libraries.
The question is how to organize git project for such structure?
I tried to push each module to different repository but this cause 1 problem, the Project build.gradle file and gradle-wrapper.properties is outside any of those modules and not pushed to git, and if i later try to clone any of this modules it will not build correctly.
Do i miss something ?
I use local gitlab server for git .
android git 
android-studio gradle gitlab asked Nov 14 '18 at 7:19
Maksim NovikovMaksim Novikov
405311
add a comment |
i'm building android SDK (library) which should be divided into 2 parts (core functionality and core-extensions) also need to create sample app to demonstrate basic usage of the library, sample app should usage both libraries.
The question is how to organize git project for such structure?
I tried to push each module to different repository but this cause 1 problem, the Project build.gradle file and gradle-wrapper.properties is outside any of those modules and not pushed to git, and if i later try to clone any of this modules it will not build correctly.
Do i miss something ?
I use local gitlab server for git .
android git android-studio gradle gitlab asked Nov 14 '18 at 7:19
Maksim NovikovMaksim Novikov
405311
I would propose you to think carefully about folder/git structure of your projects AND if there is no other option write setup script. You will run it right after checkout project from git. For example it can create symlinks to provide correct project structure before you will run build script or open project in IDE. Symlinks is better than copying files because you still will see changes of files in git.
– oss
Nov 14 '18 at 9:03
add a comment |
i'm building android SDK (library) which should be divided into 2 parts (core functionality and core-extensions) also need to create sample app to demonstrate basic usage of the library, sample app should usage both libraries.
The question is how to organize git project for such structure?
I tried to push each module to different repository but this cause 1 problem, the Project build.gradle file and gradle-wrapper.properties is outside any of those modules and not pushed to git, and if i later try to clone any of this modules it will not build correctly.
Do i miss something ?
I use local gitlab server for git .
android git android-studio gradle gitlab asked Nov 14 '18 at 7:19
Maksim NovikovMaksim Novikov
405311
i'm building android SDK (library) which should be divided into 2 parts (core functionality and core-extensions) also need to create sample app to demonstrate basic usage of the library, sample app should usage both libraries.
The question is how to organize git project for such structure?
I tried to push each module to different repository but this cause 1 problem, the Project build.gradle file and gradle-wrapper.properties is outside any of those modules and not pushed to git, and if i later try to clone any of this modules it will not build correctly.
Do i miss something ?
I use local gitlab server for git .
android git android-studio gradle gitlab android git android-studio gradle gitlab asked Nov 14 '18 at 7:19
Maksim NovikovMaksim Novikov
405311
asked Nov 14 '18 at 7:19
Maksim NovikovMaksim Novikov
405311
asked Nov 14 '18 at 7:19
Maksim NovikovMaksim Novikov
405311
asked Nov 14 '18 at 7:19
Maksim NovikovMaksim Novikov
405311
asked Nov 14 '18 at 7:19
Maksim NovikovMaksim Novikov
405311
405311
I would propose you to think carefully about folder/git structure of your projects AND if there is no other option write setup script. You will run it right after checkout project from git. For example it can create symlinks to provide correct project structure before you will run build script or open project in IDE. Symlinks is better than copying files because you still will see changes of files in git.
– oss
Nov 14 '18 at 9:03
add a comment |
I would propose you to think carefully about folder/git structure of your projects AND if there is no other option write setup script. You will run it right after checkout project from git. For example it can create symlinks to provide correct project structure before you will run build script or open project in IDE. Symlinks is better than copying files because you still will see changes of files in git.
– oss
Nov 14 '18 at 9:03
I would propose you to think carefully about folder/git structure of your projects AND if there is no other option write setup script. You will run it right after checkout project from git. For example it can create symlinks to provide correct project structure before you will run build script or open project in IDE. Symlinks is better than copying files because you still will see changes of files in git.
– oss
Nov 14 '18 at 9:03
I would propose you to think carefully about folder/git structure of your projects AND if there is no other option write setup script. You will run it right after checkout project from git. For example it can create symlinks to provide correct project structure before you will run build script or open project in IDE. Symlinks is better than copying files because you still will see changes of files in git.
– oss
Nov 14 '18 at 9:03
add a comment |
0
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',
autoActivateHeartbeat: false,
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%2f53294952%2fcreate-android-project-with-multiple-modules-libraries-and-use-different-git-r%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
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.
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%2f53294952%2fcreate-android-project-with-multiple-modules-libraries-and-use-different-git-r%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
I would propose you to think carefully about folder/git structure of your projects AND if there is no other option write setup script. You will run it right after checkout project from git. For example it can create symlinks to provide correct project structure before you will run build script or open project in IDE. Symlinks is better than copying files because you still will see changes of files in git.
– oss
Nov 14 '18 at 9:03