The ant based build and eclipse worked with standard android project
tree, worked together to a degree via referencing project.properties and
such.
Gradle sure is a great path going forward.
I was wondering about some documentation from earlier on in the process
that explains the default
The new structure allows us a lot more flexibility with tests inside the
main project, and different code/resources for different variants).
The big thing though is that Gradle will allow you to use whatever
structure you want in a way that's understood by the IDEs. This was never
possible.
I was baffled to find that a new Android Project created via Android
Studio creates a project tree (on the file system) which shows
significant divergence from the standard android project tree defined in
the Android sdk documentation.
One of the greatest attributes of the Android project
This is done as part of the new build system -- here's the talk from Google
I/O last week:
http://www.youtube.com/watch?v=LCJAgPkpmR0
On Tue, May 21, 2013 at 11:56 AM, Sanjay Mishra smit...@gmail.com wrote:
I was baffled to find that a new Android Project created via Android
Studio creates
I certainly agree with the concepts in this video IO/session, and
appreciate the feature of the new build system
However, my question is about :
1) the standard android project tree (and changes or abandonment thereof) ,
which this presentation does not mention...
2) the project tree
Android Studio, and the new build system, are both previews only (the
version number for Studio is 0.1, the build system is at version 0.4). When
it gets closer to release, both the documentation, and command line tools,
will be brought up to date.
On Tue, May 21, 2013 at 12:56 PM, Sanjay Mishra
6 matches
Mail list logo
