You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2019/04/01 13:53:00 UTC

[jira] [Commented] (TINKERPOP-2185) Use commons-configuration2 instead of commns-configuration

    [ https://issues.apache.org/jira/browse/TINKERPOP-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806771#comment-16806771 ] 

stephen mallette commented on TINKERPOP-2185:
---------------------------------------------

Thanks for the suggestion on the redhat version. that might be the best option for now as going to commons2 would be a breaking change in our release lines for the older versions we are supporting. 

> Use commons-configuration2 instead of commns-configuration
> ----------------------------------------------------------
>
>                 Key: TINKERPOP-2185
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2185
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: structure
>    Affects Versions: 3.3.6, 3.4.1
>            Reporter: Alex Ott
>            Priority: Major
>
> Product called Whitesource reports vulnerabilities in the commons-configuration 1.10 that is dependency of the gremlin-core module. As result, some projects couldn't be allowed to production because of the failing check.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)