gradle's transform api defines number of scopes. however, there little documentation regarding each scope means. know?
/** * scope of content. * * <p/> * indicates content represents, transforms can apply part(s) * of classes or resources build manipulates. */ enum scope { /** project content */ project(0x01), /** project's local dependencies (local jars) */ project_local_deps(0x02), /** sub-projects. */ sub_projects(0x04), /** sub-projects's local dependencies (local jars). */ sub_projects_local_deps(0x08), /** external libraries */ external_libraries(0x10), /** code being tested current variant, including dependencies */ tested_code(0x20), /** local or remote dependencies provided-only */ provided_only(0x40); private final int value; scope(int value) { this.value = value; } public int getvalue() { return value; } }
given android n source code hasn't been released yet, there aren't lot of examples read over. best i've found far realm-java contains couple transformers.
tried out number of different combinations of scopes. , determined following;
- project: scope represents targeted gradle module.
- project_local_deps: dependencies inside target module's "libs" folder
- sub_projects: dependencies inside same android studio project, such other gradle modules. example, does not allow analyze picasso's class files.
- sub_projects_local_deps: local "libs" files dependencies inside same android studio project.
- external_libraries: libraries pulled maven. example, does allow analyze picasso's class files.
Comments
Post a Comment