did anybody meet this before? it looks so simple but i just can not get rid of it:

the simplest junit:

@Test

public void findOne() {

Assert.assertNotNull("aaa");

}

the almost simplest POM:

    <dependencies>

        <dependency>

            <groupId>junit</groupId>

            <artifactId>junit</artifactId>

            <version>4.8.2</version>

            <type>jar</type>

            <scope>compile</scope>

        </dependency>

        <dependency>

            <groupId>org.hibernate</groupId>

            <artifactId>hibernate-entitymanager</artifactId>

            <version>3.6.3.Final</version>

            <scope>compile</scope>

        </dependency>

    </dependencies>

the junit test even has nothing to do with the hibernate. but once i add the dependence and run as>junit test, i got this in eclipse:

but if i pom.xml>run as>maven test, everything is fine

or if i remove the hibernate dependency, both "run as" are fine.

how can this happen???