Android Test Maven Plugin throws and error: java.lang.NoClassDefFoundError: junitx.util.PrivateAccessor

Question

I have created a maven project to automate the android tests. It was working fine until I added junit-addons in order to test the private fields. I added the following dependency to the pom file:

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

Then it gives me the error for each test case that is using PrivateAccessor. The error is like bellow:

java.lang.NoClassDefFoundError: junitx.util.PrivateAccessor

I removed <scope>provided</scope> and run the project but it gives me the following error:

 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.

Any help would be appreciated.

Answer 1

I found the solution by myself. It gave error because in junit-addons depends on three other libraries. I just eclude these libraries from my dependency.

I should remove <scope>privided</scope> and add the following to the junit-addons dependecy:

<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>