The way gradle handles dependencies prevents us from doing this. A published artifact is a file, not a folder.
We do hope to improve this in the near future though. On Mon, Feb 9, 2015 at 3:20 AM, 龙小康 <[email protected]> wrote: > I'm currently trying to use gradle-android to build our project, but it > takes 35 minutes to generate a debug apk, too slow to be useful, while buck > takes only about 10 minutes. > > According to gradle output, I found a lot of "prepareXXXXLibrary" task, > each one represents a library dependency, and they extract files from > library aar file to current project's build directory. > > *But library aar file is packaged from buildDir/intermediates/bundles/, I > am wondering why don't just reuse those files, instead of extracting from > aar for every projet that depends on it. *Because our project are > separated into 100 subprojects, and there are 10 subprojects that every > other project depends on them, in this case these several subprojects will > be extracted 90 times, and take up 90x disk space. This is a huge waste of > time and disk space, and in my opinion, slows down the build very much. > > So is there any way to stop gradle from packaging and extracting library > project, and just reuse the files that already there? Thanks in advance. > > -- > 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. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. 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.
