[
https://issues.apache.org/jira/browse/TINKERPOP-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864409#comment-15864409
]
ASF GitHub Bot commented on TINKERPOP-1633:
-------------------------------------------
GitHub user dysmento opened a pull request:
https://github.com/apache/tinkerpop/pull/557
TINKERPOP-1633 use official jbcrypt 0.4 in maven central
targeting tp31 branch for this version bump of jbcrypt to 0.4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dysmento/tinkerpop tp31
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tinkerpop/pull/557.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #557
----
commit 0fb51e941cafc733419204a7f80b55c30d5387d4
Author: Zach A. Thomas <zach.tho...@inin.com>
Date: 2017-02-13T21:01:16Z
TINKERPOP-1633 use official jbcrypt 0.4 in maven central
----
> use org.mindrot:jbcrypt v0.4
> ----------------------------
>
> Key: TINKERPOP-1633
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1633
> Project: TinkerPop
> Issue Type: Bug
> Components: build-release
> Reporter: Zach A. Thomas
>
> I have followed Sonatype's guidelines for deploying third party artifacts,
> and jbcrypt v0.4 is now in Maven Central.
> Unlike alternative jbcrypts available, this is Damien Miller's code
> _unmodified_.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
