[
https://issues.apache.org/jira/browse/MINIFI-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984808#comment-15984808
]
Kevin Doran commented on MINIFI-233:
------------------------------------
For others coming here in search of a workaround, here is a bit of bash that
will install the current JBCrypt artifacts to your local maven repo and rename
them to use the older capitalization (assuming it is in the default location of
~/.m2):
{code}
rm -rf ~/.m2/repository/de/svenkubiak && \
mvn org.apache.maven.plugins:maven-dependency-plugin:2.1:get \
-DrepoUrl=http://download.java.net/maven/2/ \
-Dartifact=de.svenkubiak:jBCrypt:0.4.1 && \
mv ~/.m2/repository/de/svenkubiak/jBCrypt
~/.m2/repository/de/svenkubiak/jBcrypt && \
find ~/.m2/repository/de/svenkubiak/jBcrypt -name '*jBCrypt*' -exec bash -c 'mv
$0 ${0/jBCrypt/jBcrypt}' {} \;
{code}
Just copy/paste that into your terminal prior to doing a mvn build for MiNiFi.
Unless you clear your local maven repo, it's a one-time step.
> Build does not work if pulling dependencies from a clean environment
> --------------------------------------------------------------------
>
> Key: MINIFI-233
> URL: https://issues.apache.org/jira/browse/MINIFI-233
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Build
> Affects Versions: 0.2.0
> Reporter: Aldrin Piri
> Attachments: jbcrypt-deps.tgz
>
>
> This is a ticket to track the reliance on the fix for NIFI-3554. Given that
> we inherit from NiFi's pom structure, we are currently broken from a clean
> state given the dependency renaming until we can use a new release with the
> adjustments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
