That does sound like a pretty cool feature, a lot like Maven Modules.
Although it might actually resolve the multi-lib project, it is not really
the same thing.
Having the server code, the mobile code and all my other projects for
reference is a big deal.
e.g.
I've even had a single project that contained server components in Java,
PHP and Ruby along with Android and Blackberry mobile components. Eclipse
is a master at that kind of workflow, and I'll miss it in IDEA.
I do have some catching-up to do with IDEA, so hopefully I'll find some
satisfactory workflows I can use.
On Friday, November 22, 2013 4:57:41 PM UTC-5, Tor Norbye wrote:
>
> With the new gradle build system you shouldn't have to have different
> projects for different versions (free, paid, etc.); you should be able to
> set everything up in a single project, with separate resources and classes
> (as necessary) for your variations. This is now handled by the build
> system in Android Studio directly ("flavors"); see
> http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants.
> We're working on better UI support for this so you don't need to
> configure it in Gradle config files.
>
> -- Tor
>
>
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
