[
https://issues.apache.org/jira/browse/TINKERPOP-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864245#comment-15864245
]
ASF GitHub Bot commented on TINKERPOP-1633:
-------------------------------------------
GitHub user dysmento opened a pull request:
https://github.com/apache/tinkerpop/pull/556
TINKERPOP-1633 use official jbcrypt 0.4 in maven central
This removes the hurdle of requiring extra steps to get the artifacts of
jbcrypt 0.4, which can now be found in maven central:
https://repo1.maven.org/maven2/org/mindrot/jbcrypt/0.4/
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dysmento/tinkerpop master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tinkerpop/pull/556.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 #556
----
commit 53f05d93cea9d1c277e5ad6ca2b79ad53f319a8a
Author: Zach A. Thomas <zach.tho...@inin.com>
Date: 2017-02-13T19:08:50Z
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)
