>>Would it be possible to remove the flavors from the libraries and split each flavor into a separate project
Can you mention a couple of the biggest specific issues you encountered with eclipse? We don't use flavors for sub-projects because they are not supported; in fact, no part of BuildVariant is passed down to sub-projects. The app module is built as requested, but all sub-projects are built as flavor main target release. We were trying to use flavors to segregate production (CI), integration and developer tests. Ended up using sourceSets to effectively move all tests to the app project, which at least worked - except of course assets and resources. Maybe separate projects. All the doc I'm finding looks to have bee updated to only suggest using flavors instead of separate projects - I need to find how I relate a test project to a particular app project. thanks, greg On Wed, Feb 11, 2015 at 6:01 AM, <[email protected]> wrote: > Would it be possible to remove the flavors from the libraries and split > each flavor into a separate project, and then tie up your dependencies like > that? A flavor does seem like it's just a way to have separate projects > without having to make separate directories and build scripts, but it also > comes with some limitations. I ran into these limitations myself when using > multiple flavor dimensions, so I kept separate projects for the main > dimension. > > My POV is similar to Kiran's. I actually recently converted all of my > builds to gradle due to increasing frustration with Eclipse, ADT, and ant. > The Android tools team is focusing on Android Studio going forward and this > is where the future lies. > > From the viewpoint of a team, I would recommend keeping the build system > as modern and as simple as possible, even if at the expense of some short > term pain, because one day you're going to have new heads looking at that > and the more complex it is, the more they won't understand it and the more > afraid they'll be to touch it, let alone bring it over into a new build > system. I still have some horrible memories of the several thousand-line > ant build script we used at one of the places I worked at. :P > > > On Tuesday, February 10, 2015 at 7:42:44 PM UTC-5, Greg Macdonald wrote: >> >> There seem to be an awful lot of issues yet with Android Studio and we >> are considering switching tools to eclipse/ant until AS/gradle is really >> really ready for production use. Things like not propagating build variant >> (flavor and target) to sub-projects is very fundamental and I really didn't >> want to waste time writing custom groovy code to get around build >> limitations. >> >> Anybody got any good, factual type input on why a team should or should >> not make this move? I know that one day AS will be ready for prime time >> and we will have to migrate back, but I don't know how long we would have >> to live with things before we get there, or if ready will happen sort of >> all at once in a month or there will be a steady stream of improvements >> that culminate in ready at some time in the future. >> >> thanks >> > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" 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/d/optout. > -- You received this message because you are subscribed to the Google Groups "adt-dev" 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/d/optout.
