Hi Igor, one other thing to mention is that the Java resources contained in classes.jar need to be extracted into a folder and made available to aapt when it is constructing an APK.
So ideas on how we should properly deal with this requirement using an ArtrifactHandler or other mechanism? William On Fri, Feb 7, 2014 at 1:58 PM, William Ferguson < william.fergu...@xandar.com.au> wrote: > :-) well unless you are doing Android dev there really isn't any need to > know what the AAR structure is. > > An AAR contains the following: > > - assets folder - Contains any number of text or binary assets. > - res folder - Contains zero or more other folders which contains text > or binary resources for different densities/sizes and views. > - AndroidManifest.xml which defines the application > - classes.jar (what all the fuss has been about) > - R.txt text file declaring the resources from the res folder with a > unique identifier for each. > > All of the resources are consumed by the aapt application to generate an > APK (Android application package file) which contains a dex file (byte code > representation) plus the resources (assets, res, AndroidManifest.xml). > > We need to make several passes with aapt to generate several intermediate > artefacts before finally generating the APK. > > So at the moment extracting the AAR works well, as long as we can add > classes.jar to the classpath. > > > > > On Thu, Feb 6, 2014 at 2:50 PM, Igor Fedorenko <i...@ifedorenko.com>wrote: > >> I don't have all the answers, but I think it is relatively common to >> have dependency on something available inside an archive deployed to a >> repository and I am interested to figure out how to express such >> dependencies in maven. >> >> First, however, I need to apologize for my ignorance about Android >> development (really have no excuse here) and ask for more info about use >> of AAR during the build. Does the build need any other AAR entries or >> classes.jar is the only entry needed by the build? >> >> -- >> Regards, >> Igor >> >> >> >> On 2/5/2014, 20:56, William Ferguson wrote: >> >>> Wrt to the ArtifactHandler for AAR artifacts. Could you expand on that. >>> Would this be the correct approach to handling artifacts that potentially >>> contain other artifacts/resources? Where should I start in going down >>> this >>> path? >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> >
