[
https://issues.apache.org/jira/browse/MINIFI-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966112#comment-15966112
]
Aldrin Piri commented on MINIFI-233:
------------------------------------
Hey [~jzemerick],
It is woefully unfortunate, but the best option at this point would be to
recreate structure of jBcrypt before it was renamed in the maven repository. I
will attach an archive that contains this structure and currently "works on my
machine." The archive should be extracted to your m2 repo.
NiFi 1.2.0 is due for a release in the near future at which point we can
quickly remedy in MiNiFi but are currently a bit stuck given the release
procedures.
> 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
>
> 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)
