Android Test Maven插件拋出錯誤：java.lang.NoClassDefFoundError：junitx.util.PrivateAccessor

Question

我創建了一個maven項目來自動化android測試。 在我添加junit-addons以測試私有字段之前，它一直運行良好。 我將以下依賴項添加到pom文件中：

<dependency>
      <artifactId>junit-addons</artifactId>
      <groupId>junit-addons</groupId>
      <version>1.4</version>
      <scope>provided</scope>
</dependency>

然后，它給我每個使用PrivateAccessor的測試用例的錯誤。 錯誤就像下面這樣：

java.lang.NoClassDefFoundError: junitx.util.PrivateAccessor

我刪除了<scope>provided</scope>並運行了項目，但它給了我以下錯誤：

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

任何幫助，將不勝感激。

Answer 1

我自己找到了解決方案。 它給出了錯誤，因為在junit-addons中依賴於其他三個庫。 我只是將這些庫從依賴項中排除。

我應該刪除<scope>privided</scope>並將以下內容添加到junit-addons依賴中：

<dependency>
            <groupId>junit-addons</groupId>
            <artifactId>junit-addons</artifactId>
            <version>1.4</version>
            <exclusions> 
                <exclusion> 
                    <groupId>junit</groupId>
                    <artifactId>junit</artifactId>

                </exclusion>

                <exclusion> 
                    <groupId>xerces</groupId>
                    <artifactId>xercesImpl</artifactId>

                </exclusion>

                <exclusion> 
                    <groupId>xerces</groupId>
                    <artifactId>xmlParserAPIs</artifactId>

                </exclusion>
            </exclusions>
        </dependency>