Hi guys, We are using OrientDB 1.6.1, and it seems that yesterday Tinkerpop changed the blueprints-orient-graph-2.5.0-snapshot so it points to OrientDB 1.6.3. This causes a java.lang.NoSuchMethod error on com.orientechnologies.orient.core.index.OIndex.getMetadata() when our client tries to open the database.
What is the procedure for avoiding this kind of problem? The circular dependencies between Orient and Blueprints have been discussed here before, but there does not seem to have been a definitive resolution of this issue... From what I've seen there is supposed to be cooperation between the Orient and Tinkerpop teams with regards to releases, but this is not the first time this problem has occurred, and I fear it will not be the last! A definitive word on the procedure we are to follow to ensure a stable build would be much appreciated! Best regards, Stian -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
