Hi,
We come up with the solution.
We will add classifier to the maven dependency so for example blueprints
for 1.6.3 version of OrientDB we will have blueprints with classifier
orientdb163 for 1.7 classifier will be  orientdb17 and so on.
So your dependency in maven will be
        <dependency>
            <groupId>com.tinkerpop.blueprints</groupId>
            <artifactId>blueprints-core</artifactId>
            <version>2.5.0-SNAPSHOT</version>
            <classifier>orientdb163</classifier>
       </dependency>

and you will not have problems with version incompatibility.

Is it good enough for you till we will support our own blueprints version
since blueprints 3.0 ?



On Mon, Jan 13, 2014 at 2:20 PM, Andrey Lomakin <[email protected]>wrote:

> I'm back to my original question of how we are supposed to have any kind
>> of predictability in our builds?
>
>
> That is what I meant when wrote that we come up with something till
> tomorrow.
> We will provide solution for this question till tomorrow.
>
>
>
> On Mon, Jan 13, 2014 at 1:02 PM, Stian Seeberg <[email protected]>wrote:
>
>> Hi Andrey,
>>
>> I'm back to my original question of how we are supposed to have any kind
>> of predictability in our builds? The root cause here seems to be the
>> orient-graphdb pom.xml pointing to a snapshot release of blueprints... Can
>> this not be handled differently so that there can be a release version of
>> both packages so we don't get unexpected updates to packages that we rely
>> on?
>>
>> Best regards,
>> Stian
>>
>>
>> On Monday, January 13, 2014 11:02:20 AM UTC+1, Andrey Lomakin wrote:
>>
>>> Hi,
>>> 1.6 JDK compatibility was fixed at Friday. Could you try on develop
>>> branch ?
>>> About snapshots I think we will come out with something till tomorrow.
>>>
>>>
>>>
>>> On Mon, Jan 13, 2014 at 11:58 AM, Damian Bronecki 
>>> <[email protected]>wrote:
>>>
>>>>  We even tried to migrate to OrientDB 1.6.3 but we can't do ANYTHING
>>>> in console!
>>>> This is exception
>>>>
>>>> Exception in thread "main" java.lang.NoSuchMethodError: java.nio.
>>>> CharBuffer.subSequence(II)Ljava/nio/CharBuffer;
>>>>     at com.orientechnologies.common.console.ODFACommandStream.nextC
>>>> ommand(ODFACommandStream.java:112)
>>>>     at com.orientechnologies.common.console.OConsoleApplication.exe
>>>> cuteCommands(OConsoleApplication.java:129)
>>>>     at com.orientechnologies.common.console.OConsoleApplication.run(
>>>> OConsoleApplication.java:94)
>>>>     at com.orientechnologies.orient.graph.console.OGremlinConsole.main(
>>>> OGremlinConsole.java:53)
>>>>
>>>>
>>>>  --
>>>>
>>>> ---
>>>> 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.
>>>>
>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Andrey Lomakin.
>>>
>>> Orient Technologies
>>> the Company behind OrientDB
>>>
>>>   --
>>
>> ---
>> 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.
>>
>
>
>
> --
> Best regards,
> Andrey Lomakin.
>
> Orient Technologies
> the Company behind OrientDB
>
>


-- 
Best regards,
Andrey Lomakin.

Orient Technologies
the Company behind OrientDB

-- 

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

Reply via email to