Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Maven build: Some tests fail in orientdb-core due to missing objenesis classes #6661

Closed
diegomtassis opened this issue Sep 6, 2016 · 1 comment
Closed

Maven build: Some tests fail in orientdb-core due to missing objenesis classes #6661

diegomtassis opened this issue Sep 6, 2016 · 1 comment
Milestone
2.2.10

Comments

@diegomtassis
Copy link
Contributor

OrientDB Version.

  • v2.2.8

Operating System

  • Windows

Expected behavior and actual behavior

The maven build breaks when building orientdb-core.

java.lang.NoClassDefFoundError: org/objenesis/ObjenesisStd
    at com.orientechnologies.orient.core.storage.impl.local.statistic.PerformanceStatisticManagerMBeanTest.testCacheHits(PerformanceStatisticManagerMBeanTest.java:59)
Caused by: java.lang.ClassNotFoundException: org.objenesis.ObjenesisStd

And some other tests also fail, all raising a java.lang.ClassNotFoundException

Fixed adding objenesis as a runtime dependency to orientdb-test-commons.

        <dependency>
            <groupId>org.objenesis</groupId>
            <artifactId>objenesis</artifactId>
            <version>2.4</version>
        </dependency>
@diegomtassis diegomtassis changed the title Maven build: Some tests fail in destiny-core due to missing objenesis classes Maven build: Some tests fail in orientdb-core due to missing objenesis classes Sep 6, 2016
@laa laa added this to the 2.2.x (next hotfix) milestone Sep 6, 2016
laa added a commit that referenced this issue Sep 13, 2016
@laa
Issue #6661 was fixed.
5276cce 
(cherry picked from commit 68b18f1)
@laa laa closed this as completed Sep 13, 2016
@laa
Copy link
Member

laa commented Sep 13, 2016

Fixed

@robfrank robfrank modified the milestones: 2.2.x (next hotfix), 2.2.10 Sep 13, 2016
laa added a commit that referenced this issue Sep 16, 2016
@laa
Issue #6661 was fixed.
68b18f1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
2.2.10
Development

No branches or pull requests
3 participants
@laa @robfrank @diegomtassis