[ https://issues.apache.org/jira/browse/NIFI-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101823#comment-16101823 ]
Mark Allerton commented on NIFI-3554: ------------------------------------- For those having to target NiFi 1.1.1 with their custom processors, place the following in the project POM file and this issue goes away: <dependency> <groupId>de.svenkubiak</groupId> <artifactId>jBCrypt</artifactId> <version>0.4.1</version> </dependency> > Build does not work if pulling dependencies from a clean environment > -------------------------------------------------------------------- > > Key: NIFI-3554 > URL: https://issues.apache.org/jira/browse/NIFI-3554 > Project: Apache NiFi > Issue Type: Bug > Components: Tools and Build > Affects Versions: 0.7.1, 1.2.0 > Environment: tested with a MacOS X 10.11.6 (El Capitan), but this > problem should happen also with linux based machines. > Reporter: Pere Urbon-Bayes > Assignee: Andre F de Miranda > Priority: Minor > Labels: beginner, maven > Fix For: 0.8.0, 1.2.0, 0.7.3 > > Attachments: > 0001-NIFI-3554-Fixing-the-jBCrypt-dependency-name-from.patch > > > When building NIFI from scratch the build process raised this issue to me: > {noformat} > [INFO] --- maven-surefire-plugin:2.18:test (default-test) @ > nifi-site-to-site-reporting-task --- > [INFO] Changes detected - recompiling the module! > [INFO] Nothing to compile - all classes are up to date > [INFO] Surefire report directory: > /Users/purbon/work/nifi/nifi/nifi-nar-bundles/nifi-site-to-site-reporting-bundle/nifi-site-to-site-reporting-task/target/surefire-reports > [INFO] Using configured provider > org.apache.maven.surefire.junit4.JUnit4Provider > ------------------------------------------------------- > [INFO] > [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ > nifi-gcp-processors --- > T E S T S > ------------------------------------------------------- > [ERROR] Failed to execute goal on project nifi-standard-processors: Could not > resolve dependencies for project > org.apache.nifi:nifi-standard-processors:jar:1.2.0-SNAPSHOT: Failure to find > de.svenkubiak:jBcrypt:jar:0.4.1 in https://repo1.maven.org/maven2 was cached > in the local repository, resolution will not be reattempted until the update > interval of central has elapsed or updates are forced -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn <goals> -rf :nifi-standard-processors > {noformat} > showing a problem with a dependency that could not be retrieved. > After a bit of investigation I noticed that the dependency is using a > capitalised name, in contrast from the one currently being in the repository. > {code:xml} > <dependency> > <groupId>de.svenkubiak</groupId> > <artifactId>jBCrypt</artifactId> > <version>0.4.1</version> > </dependency> > {code} > vs the definition now in nifi-standad-processors/pom.xml: > {code:xml} > <dependency> > <groupId>de.svenkubiak</groupId> > <artifactId>jBcrypt</artifactId> > <version>0.4.1</version> > </dependency> > {code} > You can reproduce this issue by forcing maven to retrieve this dependency > from the repository, for example removing it from your .m2/repository > directory. > This is my first issue reported to the NIFI community, accept my apologies > beforehand if I did something not as expected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)