Ошибка: выполнение выполнено для задачи ': TMessagesProj: dexDebug'. Process 'command' jdk1.8.0_66 \ bin \ java.exe '' закончил с ненулевым значением выхода 1

Question

Я импортировал проект Telegram в андроид-студию, после 4-часовых расходов на необходимые библиотеки импорта я получил ошибку ниже. Что мне делать?

Ошибка: выполнение выполнено для задачи ': TMessagesProj: dexDebug'.

com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'C:\Program Files\Java\jdk1.8.0_66\bin\java.exe'' finished with non-zero exit value 1

trouble processing "java/awt/BorderLayout.class": 
Ill-advised or mistaken usage of a core class (java.* or javax.*) 
when not building a core library. 
This is often due to inadvertently including a core library file 
in your application's project, when using an IDE (such as 
Eclipse). If you are sure you're not intentionally defining a 
core class, then this is the most likely explanation of what's 
going on. 
However, you might actually be trying to define a class in a core 
namespace, the source of which you may have taken, for example, 
from a non-Android virtual machine project. This will most 
assuredly not work. At a minimum, it jeopardizes the 
compatibility of your app with future versions of the platform. 
It is also often of questionable legality. 
If you really intend to build a core library -- which is only 
appropriate as part of creating a full virtual machine 
distribution, as opposed to compiling an application -- then use 
the "--core-library" option to suppress this error message. 
If you go ahead and use "--core-library" but are in fact 
building an application, then be forewarned that your application 
will still fail to build or run, at some point. Please be 
prepared for angry customers who find, for example, that your 
application ceases to function once they upgrade their operating 
system. You will be to blame for this problem. 
If you are legitimately using some code that happens to be in a 
core package, then the easiest safe alternative you have is to 
repackage that code. That is, move the classes in question into 
your own package namespace. This means that they will never be in 
conflict with core system classes. JarJar is a tool that may help 
you in this endeavor. If you find that you cannot do this, then 
that is an indication that the path you are on will ultimately 
lead to pain, suffering, grief, and lamentation. 

Gradle

apply plugin: 'com.android.application' 

repositories { 
    mavenCentral() 
} 

dependencies { 
    compile 'com.android.support:support-v4:23.1.+' 
    compile 'com.google.android.gms:play-services:3.2.+' 
    compile 'net.hockeyapp.android:HockeySDK:3.5.+' 
    compile 'org.apache.httpcomponents:httpmime:4.2.1' 
    compile files('libs/aspectjrt.jar') 
    compile files('libs/javax.jar') 

} 


android { 
    compileSdkVersion 23 
    buildToolsVersion '23.0.1' 

    useLibrary 'org.apache.http.legacy' 

    packagingOptions { 
     exclude 'META-INF/NOTICE.txt' 
     exclude 'META-INF/LICENSE.txt' 
    } 

    compileOptions { 
     sourceCompatibility JavaVersion.VERSION_1_7 
     targetCompatibility JavaVersion.VERSION_1_7 
    } 

    signingConfigs { 
     debug { 
      storeFile file("config/debug.keystore") 
     } 

     release { 
      storeFile file("config/release.keystore") 
      storePassword RELEASE_STORE_PASSWORD 
      keyAlias RELEASE_KEY_ALIAS 
      keyPassword RELEASE_KEY_PASSWORD 
     } 
    } 

    buildTypes { 
     debug { 
      debuggable true 
      jniDebuggable true 
      multiDexEnabled true 
      signingConfig signingConfigs.debug 
     } 

     release { 
      debuggable false 
      jniDebuggable false 
      multiDexEnabled true 
      signingConfig signingConfigs.release 
     } 

     foss { 
      debuggable false 
      jniDebuggable false 
      multiDexEnabled true 
      signingConfig signingConfigs.release 
     } 
    } 

    sourceSets.main { 
     jniLibs.srcDir 'libs' 
     jni.srcDirs = [] //disable automatic ndk-build call 
    } 

    sourceSets.debug { 
     manifest.srcFile 'config/debug/AndroidManifest.xml' 
    } 

    sourceSets.release { 
     manifest.srcFile 'config/release/AndroidManifest.xml' 
    } 

    sourceSets.foss { 
     manifest.srcFile 'config/foss/AndroidManifest.xml' 
    } 

    defaultConfig { 
     minSdkVersion 8 
     targetSdkVersion 23 
     versionCode 654 
     versionName "3.2.6" 
     multiDexEnabled true 

    } 
} 

Answer 1

проблема из-за добавление библиотеки вручную.

Выполните следующие шаги:
. Немедленно удалите текущий проект и повторно импортируйте проект.
. Подключитесь к Интернету, чтобы автоматически загружать зависимости из Интернета во время работы градиента.
. Все проблемы будут решены.