BeeHome从2.3迁移到3.0需要修改的地方

最新推荐文章于 2019-05-30 16:52:31 发布

麦晓宇

最新推荐文章于 2019-05-30 16:52:31 发布

阅读量571

点赞数

分类专栏： android studio

本文链接：https://blog.csdn.net/fishmai/article/details/78841267

版权

android studio 专栏收录该内容

10 篇文章 0 订阅

订阅专栏

1

down vote favorite

Error:android-apt plugin is incompatible with the Android Gradle plugin. Please use 'annotationProcessor' configuration instead.

After upgrading from 2.2 to 2.3 I see this warning

and when I try to compile the project I see this compilation error

How can i solve this issue without downgrading to a previous gradle version? Is there any update of android-apt that can solve this issue?

解决方案

52 down vote favorite

After upgrading from 2.2 to 2.3 I see this warning

and when I try to compile the project I see this compilation error

How can i solve this issue without downgrading to a previous gradle version? Is there any update of android-apt that can solve this issue?

The android-apt plugin has been deprecated.
Check here for the migration guide:

As of the Android Gradle plugin version 2.2, all functionality that was previously provided by android-apt is now available in the Android plugin.

You can remove android-apt by following the migration guide to get the equivalent functionalities.

The important parts from the migration guide:

Make sure you are on the Android Gradle 2.2 plugin or newer.
Remove the android-apt plugin from your build scripts
Change all apt, androidTestApt and testApt dependencies to their new format:

dependencies {
   compile 'com.google.dagger:dagger:2.0'
   annotationProcessor 'com.google.dagger:dagger-compiler:2.0'
}

Also in the Android Gradle plugin there is an explicit check for this, which is what you are seeing:

using incompatible plugins for the annotation processing android-apt

Future Android Gradle plugin versions will not be compatible with the way android-aptworks, which is the reason for that check.

52 down vote favorite

After upgrading from 2.2 to 2.3 I see this warning

and when I try to compile the project I see this compilation error

How can i solve this issue without downgrading to a previous gradle version? Is there any update of android-apt that can solve this issue?

2 Error:All flavors must now belong to a named flavor dimension. Learn more at https://d.android.com/r/tools/flavorDimensions-missing-error-message.html

If you don't really need the mechanism, just specify a random flavor dimension:

android { 
    ...
    flavorDimensions "default"
    ...
}

For more information, check the migration guide

3. Android Studio 3.0 Compile Issue (Cannot choose between Configurations)

Issue with latest 3.0 build (Beta 2) My project has 1 sub module by a 3rd party so I only have access to their build.gradle.

My project has 3 flavours, snap, uat, production. Each has 2 build types, debug and release. When I try build I get this.

Error:Cannot choose between the following configurations of project :lp_messaging_sdk:
  - debugApiElements
  - debugRuntimeElements
  - releaseApiElements
  - releaseRuntimeElements
All of them match the consumer attributes:
  - Configuration 'debugApiElements':
      - Found com.android.build.api.attributes.BuildTypeAttr 'debug' but wasn't required.
      - Found com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' but wasn't required.
      - Found com.android.build.gradle.internal.dependency.VariantAttr 'debug' but wasn't required.
      - Found org.gradle.api.attributes.Usage 'java-api' but wasn't required.
  - Configuration 'debugRuntimeElements':
      - Found com.android.build.api.attributes.BuildTypeAttr 'debug' but wasn't required.
      - Found com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' but wasn't required.
      - Found com.android.build.gradle.internal.dependency.VariantAttr 'debug' but wasn't required.
      - Found org.gradle.api.attributes.Usage 'java-runtime' but wasn't required.
  - Configuration 'releaseApiElements':
      - Found com.android.build.api.attributes.BuildTypeAttr 'release' but wasn't required.
      - Found com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' but wasn't required.
      - Found com.android.build.gradle.internal.dependency.VariantAttr 'release' but wasn't required.
      - Found org.gradle.api.attributes.Usage 'java-api' but wasn't required.
  - Configuration 'releaseRuntimeElements':
      - Found com.android.build.api.attributes.BuildTypeAttr 'release' but wasn't required.
      - Found com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' but wasn't required.
      - Found com.android.build.gradle.internal.dependency.VariantAttr 'release' but wasn't required.
      - Found org.gradle.api.attributes.Usage 'java-runtime' but wasn't required.

解决方案

dependencies {
  // If the library configures multiple build variants using product flavors,
  // you must target one of the library's variants using its full configuration name.

compile project(':lp_messaging_sdk')
改为  demoDebugCompile project(path: ':lp_messaging_sdk', configuration: 'demoDebug')  fullReleaseCompile project(path: ':lp_messaging_sdk', configuration: 'fullRelease')  ...}