Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Google introduced repo to manage Android source code. As is said in the document, repo is meant to make it easier to work with Android. I can't see why from the documents at
https://source.android.com/source/developing.html
From what I am seeing in the document, repo just create synonyms from git commands. So how repo makes it easier to work with Android?
I'm assuming you have already read:
Repo is a repository management tool that we built on top of Git. Repo
unifies the many Git repositories when necessary, does the uploads to
our revision control system, and automates parts of the Android
development workflow. Repo is not meant to replace Git, only to make
it easier to work with Git in the context of Android. The repo command
is an executable Python script that you can put anywhere in your path.
In working with the Android source files, you will use Repo for
across-network operations. For example, with a single Repo command you
can download files from multiple repositories into your local working
directory.
Simply put, it meant for managing multiple git repositories.
This is to make the development process more modular as you can have each feature developed in its own repository. That way, each team can contribute to their own separate repository. Each of the repositories often come together to create a larger project.
Repo allows you to pull specific commit points from each git repository to create a collective snapshot for the larger project.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
I am having trouble in using git on android studio. I know there may be many related questions asked on this topic But I could not find any relevant answer.
I can use git normally but with android studio i am facing many problems. I am working on a project with my friend. The main project is on his repository. I have forked his repo. And cloned the project on my machine. Then using imported the project on my Android Studio. Till here things are fine but after this everything messes up when i try to use git.
Do i have to use git in the terminal inside android studio itself, or in normal terminal in file manager?
Can anyone give me a proper guide of how to collaborate on Android Studio using Git.
You can use git just as you wish... Git is a part of the project and hence does not depend on the Git client.
For example, I mostly use SourceTree as my main Git client.
But when I create a new repo, or push an existing project into a new repo, I prefer to use the command line.
Now when it comes to merging, I really appreciate the AndroidStudio merging tool, So I begin my merge with SourceTree and solve conflicts with Android Studio ^^
The best tool is the one you are comfortable with, however note that they are just front-end for the git (command-line) tool.
When you open a Git project in Android Studio, detects by the itself that your project is a Git project.
You will be able to see in the bottom of Android Studio something like this:
You can commit using Control + K
If you can't see it, maybe your git configuration/project is wrong.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I have some Appium testing scripts that needed to be put through a repository for version control, mainly Git.
I looked through Google to figure out what is the best way to go about this if you have an Android App project in Andriod Studio that you're writing the tests for (which happens to be in it's own Git repository), and so far I haven't found anything in my search.
My question is: Would it be better if I include the test scripts inside the Android studio project in it's Git repository, or would it be better if I put the test scripts in their own repository? If putting the scripts in the Android project is better, where in the project's file structure should I include the test scripts?
Any input is greatly appreciated.
I put my autotests in separate repository just to have them safe from deleting from my work computer or something else.
When I'm sure that my tests are stable I clone dev branch of the main project and making a pull request including my tests. When my request is merged we have a project repository with autotests.
Don't know any better ways, but for me it works great and very comfortable.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I am a beginner to Android NDK with Android Studio. While trying to grasp the ideas through tutorials I got my self very confused. Mainly I am confused about the building method of native project.
For example while following this tutorial, when I build the project there is no file created inside libs project. Moreover, there is no need of Android.mk and Application.mk make files also.
However, second tutorial deals with the make file.
Can anyone please explain to me step by step explanation of build steps. I am not sure how hard it is for Android team to make a simple tutorial explanation one version of built.
Not sure, if by the time of this writing (2016/02/01 - Android Studio 2.0 Preview 9) NDK is officially supported yet, but it's surely been under development. That's the reason of using Eclipse+ADT+NDK in the official guide as you can see in the Setup section. I believe, once the process is done, the documentation will be updated.
You're free to choose which approach to use:
Eclipse+ADT+NDK or
Android Studio + Gradle + NDK
With the second approach Gradle generates *.mk files automatically, although you can use your own files by preventing the auto-generation as per The new NDK support in Android Studio by ph0b.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Can anyone recommend a good cloud-based IDE for Android development?
I use Eclipse/ADT on my desktop and AIDE on my Android devices, but it is a hassle to sync the two.
If there is not one available, would anyone recommend using AIDE's premium features to host my application on GIT?
I never found a good cloud-based Android IDE, but here is what I did (an idea for anyone reaching this from Google). This works with Windows, Linux, and (I think) Mac. Please confirm for others if this works for you on a Mac.
Desktop (w/ Eclipse):
Set up Dropbox
Create a new Android application project.
Uncheck the "Create Project in Workspace" option, and change the location to your Dropbox folder
Android (w/ AIDE):
Set up Dropbox sync
That's all there is to it. As long as you make sure you Dropbox before switching from desktop to Android device or vice versa, you essentially have a free, cloud-based Android IDE to develop from a desktop or an Android device.
Here's my workflow for developing for android on android:
Setup a android build server with the android sdk, ant, Ivy Or the new Gradle setup, using
an aws ec2 server or other free/cheap Cloud Server svc.
Setup dropbox Headless Install On That machine.
Setup A Git repo on that machine, put the repo inside Main Dropbox Directory.
---Home
---(User)
---Dropbox
---Repos
---App#1
Setup inotifywait on the dir the app repo Is In....
inotifywait -mr -e ATTRIB /home/user/Dropbox/path/to/repo/ |
while read dir ev file;
do
cd /home/user/Dropbox/path/to/repo;
git pull;
git add .;
git commit -m " something regarding code has changed. check .... for more info";
git push;
buildscript;
Install Dropbox On Your Android Tablet
Install a text/code Editor on Your tab like .....920 Text Editor.
So Now when you Make A code change on your tab dropbox Will Sync It obviously
And That Sync Which Is An attrib event will trigger a Bunch Of Scripts...git Stuff and The Build stuff and any other Scripts You Desire.
The Final apk That The Build Script Created will Be Saved To Your app Project Directory Which is in your Dropbox so Installing/testing on Your Tab is seemless And You Can Have Others Test Your Apk By sharing That folder With them Thru dropbox
Hooking the Code to a Git Repo is Cool B/c you Can Use a service like cloudbees To then build And Test your apk. Aswell As, have the Apk sent To Distributors And other cool services.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
While there seems to be a way to clone the whole repo, described here, I just need just the Java API files, nothing more. (Hint: traffic limit + slow connection)
Now, here is the whole git repo, but where are the plain Java API files? Or are they at a complete different location? Someone an idea? I'm not that much a git expert.
I have no idea what you think "the plain Java API files" are.
The second link is not a git repo. It is a family of git repositories. Each row in that table is one git repo. The first link is for instructions on how to use Android-supplied tools to clone all of those repositories.
If you think "the plain Java API files" refer to the java.* and javax.* classes, they are from the libcore repo.
If you think "the plain Java API files" refer to android.* classes, they are from the frameworks/base repo.
Other repos may be contribute other portions of "the plain Java API files", such as Apache HttpClient.
If all you are trying to do is poke through the code, I recommend Google Code Search. For example, I refer to the Android source code frequently, and I don't have it downloaded.
[Edit]
And if all you want to do is develop android applications, you don't need any of this; just download the SDK
Following worked, with the help of this question:
git clone git://android.git.kernel.org/platform/frameworks/base.git
cd base
git tag -l
git checkout android-2.2.2_r1
And then we get a nice directory: core/java/android
tar cjf android-java-2.2.2.tbz2 core/java/android
And then we get a nice bzip2-ed archive: android-java-2.2.2.tbz2, just 1.8MB ;)
If u just need to see or download a specific JAVA API file from android.. then just refer this site
http://grepcode.com/snapshot/repository.grepcode.com/java/ext/com.google.android/android/2.3.4_r1/
this is has repo of all android release.