You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Alex Ott (JIRA)" <ji...@apache.org> on 2019/03/24 12:15:00 UTC
[jira] [Commented] (TINKERPOP-2165) Prefer commons-lang3 to
commons-lang
[ https://issues.apache.org/jira/browse/TINKERPOP-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800006#comment-16800006 ]
Alex Ott commented on TINKERPOP-2165:
-------------------------------------
commons-lang2 2.6 had a vulnerability that is reported by Whitesource checks...
Same for commons-configuration - I'll create a ticket for it.
> Prefer commons-lang3 to commons-lang
> ------------------------------------
>
> Key: TINKERPOP-2165
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2165
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
> Affects Versions: 3.3.5
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Minor
> Fix For: 3.3.6, 3.4.1
>
>
> The {{commons-lang}} dependency is for 2.x and its last release goes back to 2011. I think our code references some of its classes, mostly because the IDE defaulted it that way on auto-import. Unfortunately, we can't lift it out completely without bumping {{commons-configuration}} which still depends on 2.x and that can't be done without a breaking change. I imagine we should consider that for TinkerPop 3.5.x and deprecate the use of that module in favor of the new Configuration 2.x, but I think that's for a different day. Looked into it a bit and it was a small mess.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)