2015-12-02 12 views
13

私はRetrofit 2.0に変換中です。しかし、単純なXMLコンバータをbuild.gradleに追加しようとすると、もはやコンパイルされなくなります。ここでエラーコンパイルcom.squareup.retrofit:converter-simplexml:2.0.0-beta2

私の依存関係が

dependencies { 
    compile fileTree(dir: 'libs', include: ['*.jar']) 
    testCompile 'junit:junit:4.12' 
    compile 'com.android.support:appcompat-v7:23.1.1' 
    compile 'com.android.support:design:23.1.1' 
    compile 'com.squareup.retrofit:retrofit:2.0.0-beta2' 
    compile 'com.squareup.okhttp:logging-interceptor:2.6.0' 
    compile 'com.squareup.retrofit:converter-simplexml:2.0.0-beta2' //THIS LINE 
    compile 'com.google.code.gson:gson:2.3' 
    compile 'org.parceler:parceler:0.2.13' 
    compile 'com.jakewharton:butterknife:7.0.1' 
} 

であり、私は私のコードをコンパイルするために行くとき、私は次のエラーを取得する:

trouble processing "javax/xml/XMLConstants.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. 

このエラーは、コミュニティに新しいものではありません、私はしないでくださいそれが私のプロジェクトにどのように適用されるかを理解する。私はまだコードを書いていないし、基本的な依存関係をコンパイルできない。この行をコメントアウトすると

compile 'com.squareup.retrofit:converter-simplexml:2.0.0-beta2' 

コードがコンパイルされます。だから、これは間違いなく犯人です。

答えて

36

私はそれを修正しました。どうやらあなたはいくつかのものを除外しなければなりません。

compile ('com.squareup.retrofit:converter-simplexml:2.0.0-beta2') { 
     exclude group: 'xpp3', module: 'xpp3' 
     exclude group: 'stax', module: 'stax-api' 
     exclude group: 'stax', module: 'stax' 
} 

希望これは他の誰か

+0

グレート!感謝を助け!!!) – voronnenok

+0

それは動作します!しかし、なぜsimlexmlがコアのJavaライブラリを置き換えたいのですか? – Ninja

+0

この行をgradleファイルに貼り付けて再コンパイルすると、プロジェクトが壊れ、このすべての改造ファイルがなくなります。 –

関連する問題