【问题标题】:Why am I still able to use support-v4 library without importing it on gradle?为什么我仍然可以使用 support-v4 库而不在 gradle 上导入它?
【发布时间】:2018-07-07 01:24:07
【问题描述】:

我很困惑,在我的 gradle 中我没有导入 support-v4,但我似乎能够使用该库,support-v4 默认包含为依赖项吗?见下文?同样在我的项目文件夹中,每次创建项目和各个模块时,我都可以看到 jars 支持 v4?

项目等级:

// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:2.3.3'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        jcenter()
        maven{
            url "https://maven.google.com"
        }
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

我的应用程序:

apply plugin: 'com.android.application'

android {
    compileSdkVersion 26
    buildToolsVersion "26.0.1"
    defaultConfig {
        applicationId "com.example.ok.applicationtest_v4lib"
        minSdkVersion 19
        targetSdkVersion 26
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}

dependencies {
    compile fileTree(include: ['*.jar'], dir: 'libs')
    androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {
        exclude group: 'com.android.support', module: 'support-annotations'
    })
    compile 'com.android.support:appcompat-v7:26.0.1'
    compile 'com.android.support.constraint:constraint-layout:1.0.2'
    compile 'com.android.support:design:26.0.1'
    testCompile 'junit:junit:4.12'
}

-activity 下面可以导入 support-v4 而无需在 gradle 中导入 support-v4:

package com.example.ok.applicationtest_v4lib;

import android.os.Bundle;
import android.support.design.widget.FloatingActionButton;
import android.support.design.widget.Snackbar;
import android.support.v4.app.ActivityCompat;
import android.support.v7.app.AppCompatActivity;
import android.support.v7.widget.Toolbar;
import android.view.View;
import android.view.Menu;
import android.view.MenuItem;

public class MainActivity extends AppCompatActivity {

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);
        Toolbar toolbar = (Toolbar) findViewById(R.id.toolbar);
        setSupportActionBar(toolbar);

        FloatingActionButton fab = (FloatingActionButton) findViewById(R.id.fab);
        fab.setOnClickListener(new View.OnClickListener() {
            @Override
            public void onClick(View view) {
                Snackbar.make(view, "Replace with your own action", Snackbar.LENGTH_LONG)
                        .setAction("Action", null).show();
            }
        });
        //I am able to use below class yet I have not imported v4 library.
        ActivityCompat
    }

    @Override
    public boolean onCreateOptionsMenu(Menu menu) {
        // Inflate the menu; this adds items to the action bar if it is present.
        getMenuInflater().inflate(R.menu.menu_main, menu);
        return true;
    }

    @Override
    public boolean onOptionsItemSelected(MenuItem item) {
        // Handle action bar item clicks here. The action bar will
        // automatically handle clicks on the Home/Up button, so long
        // as you specify a parent activity in AndroidManifest.xml.
        int id = item.getItemId();

        //noinspection SimplifiableIfStatement
        if (id == R.id.action_settings) {
            return true;
        }

        return super.onOptionsItemSelected(item);
    }
}

【问题讨论】:

    标签: java android android-studio gradle support-v4


    【解决方案1】:

    如果你有appcompat-v7,你就有appcompat-v4

    运行./gradlew app:dependencies,你会看到

    +--- com.android.support:appcompat-v7:25.4.0
    |    +--- com.android.support:support-annotations:25.4.0
    |    +--- com.android.support:support-v4:25.4.0 (*)
    |    +--- com.android.support:support-vector-drawable:25.4.0
    |    |    +--- com.android.support:support-annotations:25.4.0
    |    |    \--- com.android.support:support-compat:25.4.0 (*)
    |    \--- com.android.support:animated-vector-drawable:25.4.0
    |         +--- com.android.support:support-vector-drawable:25.4.0 (*)
    |         \--- com.android.support:support-core-ui:25.4.0 (*)
    

    【讨论】:

    • support:design 包括v7,所以即使那个也不是必需的
    • 那么,按照这个逻辑,如果我在我的 gradle 中包含依赖支持设计,我不需要 appcompat-v7 或 appcompat-v4 对吗?
    • 你不应该那样“优化”。如果您的代码需要某些库,请在您的 gradle 中设置适当的依赖项。任何其他库是否依赖于同一个库都没有关系。满足您的依赖关系不是该库的任务。一个它可能会停止取决于该库或更喜欢其他给你带来麻烦的版本。你注定要失败 - 这很容易避免 - 只需管理自己的依赖关系
    • 如果我已经拥有 support-design,删除 support-v4 和 appcompat-v7 是否安全?还是它们之间存在循环依赖关系?
    • 即使有循环依赖。这不是问题,因为 gradle 知道如何处理它。离开吧。
    猜你喜欢
    • 2013-08-12
    • 1970-01-01
    • 2016-02-11
    • 1970-01-01
    • 2013-01-17
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多