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 2 years ago.
This post was edited and submitted for review 1 year ago and failed to reopen the post:
Original close reason(s) were not resolved
Improve this question
Some developers struggle with the complexity and performance of Gradle:
It can take a long time to build simple app.
It can takes a long time to build simple change in that app again.
It can be very difficult to debug build failures.
It is a large and complex system, with a steep learning curve.
It requires learning Groovy and a family of DSLs.
It is not easy to re-use build scripts across large projects.
So, is there an alternative to gradle for android application development?
Looking for a practical, easy to maintain build system which saves developers time.
I think every Android developer asked him/herself that question more than once.
However, Google puts all efforts into improving Gradle builds for Android. Since they are the inventors/owners of Android and a big big company too, I very much doubt, that there is any different building system that comes close to Gradle.
Additionally to Gradle and Google improving the build process with every new version of Gradle and/or Androidstudio, there are many ways to improve the building speed. Easiest one is to allow gradle to use more RAM.
But you can find a ton of information about that by searching the internet a bit.
You can build Android apps with maven or ant, from a shell. You'd have to create your own build scripts. A few years ago, when Google still supported the Eclipse plugin for Android, they used ant as the build tool.
However, it's my experience that gradle is not slower or faster than either maven or ant. There must be something else that slows your build process.
Related
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 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
I am developing an Android library for interacting with a web service, and I am trying to develop some unit tests to check how well this works.
When I run the specified tests, I get the following error:
[2012-07-19 15:12:09 - MMWebAPI] Could not find MMWebAPI.apk!
[2012-07-19 15:12:10 - MMWebAPITest] Test run failed: Unable to find instrumentation target package: com.webapi.mmwebapi
Where the MMWebAPI is the library, and does not produce a .apk.
I am looking for definitive guide for unit testing Android projects, specifically, what can and can not be tested (in this case, network operations are the core of the library), a step by step tutorial would be a great help also.
Android testing framework doesn't allow to test Android library without application project that depends on that library. Please look at this answer.
You can find good introduction to testing Android project here. If your code doesn't use android-specific method You can use JUnit for tests + some mocking library. Among other testing framework Robotium and Robolectric seems to be most popular.
What this answer mentions in an update is probably what's explained step-by-step here.
Ensure that your instrumentation tag is under manifest tag not application tag
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 6 years ago.
Improve this question
I want a command line tool that works in the following situation:
1) A computer with JDK and Android SDK installed (with the target Android platform).
2) An Android project created using eclipse.
And give me the following output:
1) The signed APK of the given eclipse Android project.
How do I accomplish the above by writing a Java program (By kicking off Ant using the Java Runtime class)? I want to automate the build process, how do I do that?
Thanks.
I've used ant to do this and we use Jenkins for Continuous Integration. I've written a post on how to automate this.
http://www.multunus.com/2011/09/continuous-delivery-for-android-apps-part-1/
I use Maven with the Android plugin. It works well.
See http://simpligility.github.io/android-maven-plugin/.
The Android build process is fairly complex: quite a few tools are invoked one after another: javac to compile, then dx to convert to dex, then aapt to package (I'm sure missing a few). You can run Ant in debug mode to see the exact sequence (it is also documented, somewhere...).
So you can either:
Bundle the Ant jars with your app and invoke Ant programatically
Write a Java 'script' that invokes the tools in the correct order
Write a simple shell script/batch file and be done with it.
I am currently using Fastlane to automate beta and production releases. Fastlane is largely written in Ruby and you can customize releases based on your internal processes. You can watch this Droidcon '16 video to get started.
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 6 years ago.
Improve this question
I am currently using Eclipse 3.5.0 for Android development. But I just wanted to try Android development in some IDE other than Eclipse.
Firstly, am I going on the right track or is Android development possible only on Eclipse? Secondly, if there are options other than eclipse, what are they and in what way are they better or worse than Eclipse? How to install Android SDK on them? A tutorial for working with that IDE with be really helpful.
Stone
Android development possible only on
Eclipse?
No it is possible in other IDE also
IntroAndroidDevNetBeans
IntelliJ IDEA 10
But the way I understood, Eclipse is the Best, because it's plugin and updates are directly given in the android developer sites itself, ADT
Personally I prefer the IntelliJ. I was a big fan of Eclipse but when I started using IntelliJ (with some learning curve), I just love it ! The community edition now offers support for Android SDK. However, unfortunately there is no support for building UIs ! So, my solution for now is to configure IntelliJ projects with Android libraries, use Eclipse as a UI builder tool and then use those XML files in INtellJ. I know its a painful process but that is how I get the best of both worlds !