[
https://issues.apache.org/jira/browse/TINKERPOP-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433821#comment-17433821
]
Stephen Mallette commented on TINKERPOP-2629:
---------------------------------------------
hmm - i see. i wonder why i wrote it that way. i can envision why that might
have confused you. we definitely just disabled it with that change - there
really shouldn't be ambiguity there. i removed that word:
https://github.com/apache/tinkerpop/commit/df85d45c65691c53b2f36077a9e6cfc208174d22
thanks for pointing that out.
> Breaking change in configurations in GraphFactory
> -------------------------------------------------
>
> Key: TINKERPOP-2629
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2629
> Project: TinkerPop
> Issue Type: Bug
> Reporter: Boxuan Li
> Priority: Major
>
> I am not sure but it seems that TinkerPop 3.5 introduces a breaking change to
> the usage of configuration in GraphFactory.java.
> [https://github.com/apache/tinkerpop/commit/607224a92e443f712ca86b4b38e2fe9f92e405dc#diff-2f4c8c53541834027edea65ccf67a67c7d2f7cce1576963eab401838cae58f0eR123]
> It seems that TinkerPop was using the default list delimiter in the
> `commons-configuration` library, and is using the default disabled list
> delimiter in the `commons-configuration2` library now.
> If my observation is true, then shouldn't this be a breaking change and needs
> to be documented in the upgrade doc?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
