[ 
https://issues.apache.org/jira/browse/NIFI-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321253#comment-15321253
 ] 

Daniel Cave edited comment on NIFI-1987 at 6/8/16 7:07 PM:
-----------------------------------------------------------

I don't have a fix for it yet, it took a while to track down the exact issue.  
My concern with just changing the underlying dependencies to 1123 (really a 
temp fix) is that this is clearly an unstable repository and relying on it will 
create ongoing build risks.  I'm not familiar enough with what's going on in 
there that they're using this for to know how to permanently fix it without 
alot more research and testing.  These all looked like Cloudera specific changes


was (Author: daniel cave):
I don't have a fix for it yet, it took a while to track down the exact issue.  
My concern with just changing the underlying dependencies to 1123 (really a 
temp fix) is that this is clearly an unstable repository and relying on it will 
create ongoing build risks.  I'm not familiar enough with what's going on in 
there that they're using this for to know how to permanently fixing it without 
alot more research and testing.  These all looked like Cloudera specific changes

> Nifi-Spark-Receiver build failure due to orgspark repository change
> -------------------------------------------------------------------
>
>                 Key: NIFI-1987
>                 URL: https://issues.apache.org/jira/browse/NIFI-1987
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 0.6.1
>            Reporter: Daniel Cave
>            Assignee: Oleg Zhurakousky
>            Priority: Critical
>             Fix For: 1.0.0, 0.7.0
>
>
> Builds on machines with no or incomplete local maven repos failing due to 
> nifi-spark-receiver sub-dependency on 
> oss.sonatype.org/content/repositories/orgspark-project-1113 related 
> dependencies.  On 6/7/16 it appears that orgspark-project-1113 was removed 
> from the repo and was replaced with orgspark-project-1123.  This blocks 
> complete NiFi builds where a complete local repo was not available with all 
> 1113 sub-dependencies already in place.  See below:
> [INFO] Scanning for projects...
> [INFO] Inspecting build with total of 1 modules...
> [INFO] Installing Nexus Staging features:
> [INFO]   ... total of 1 executions of maven-deploy-plugin replaced with 
> nexus-staging-maven-plugin
> [INFO]
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Building nifi-spark-receiver 0.7.0-SNAPSHOT
> [INFO] 
> ------------------------------------------------------------------------
> Downloading: 
> https://oss.sonatype.org/content/repositories/orgspark-project-1113/org/apache/avro/avro-mapred/1.7.6-cdh5.7.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/avro/avro-mapred/1.7.6-cdh5.7.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/avro/avro-mapred/1.7.6-cdh5.7.0-SNAPSHOT/avro-mapred-1.7.6-cdh5.7.0-SNAPSHOT.pom
> Downloading: 
> https://oss.sonatype.org/content/repositories/orgspark-project-1113/org/apache/avro/avro-mapred/1.7.6-cdh5.7.0-SNAPSHOT/avro-mapred-1.7.6-cdh5.7.0-SNAPSHOT.pom
> [WARNING] The POM for 
> org.apache.avro:avro-mapred:jar:hadoop2:1.7.6-cdh5.7.0-SNAPSHOT is missing, 
> no dependency information available
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/nifi/nifi-site-to-site-client/0.7.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/nifi/nifi-commons/0.7.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/nifi/nifi/0.7.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/nifi/nifi-api/0.7.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/nifi/nifi-utils/0.7.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/nifi/nifi-security-utils/0.7.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/nifi/nifi-client-dto/0.7.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/nifi/nifi-framework/0.7.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/nifi/nifi-framework-bundle/0.7.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/nifi/nifi-nar-bundles/0.7.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/avro/avro-mapred/1.7.6-cdh5.7.0-SNAPSHOT/avro-mapred-1.7.6-cdh5.7.0-SNAPSHOT-hadoop2.jar
> Downloading: 
> https://oss.sonatype.org/content/repositories/orgspark-project-1113/org/apache/avro/avro-mapred/1.7.6-cdh5.7.0-SNAPSHOT/avro-mapred-1.7.6-cdh5.7.0-SNAPSHOT-hadoop2.jar
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time: 6.771 s
> [INFO] Finished at: 2016-06-08T13:13:41-05:00
> [INFO] Final Memory: 28M/381M
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project nifi-spark-receiver: Could not 
> resolve dependencies for project 
> org.apache.nifi:nifi-spark-receiver:jar:0.7.0-SNAPSHOT: Could not find 
> artifact org.apache.avro:avro-mapred:jar:hadoop2:1.7.6-cdh5.7.0-SNAPSHOT in 
> apache.snapshots (http://repository.apache.org/snapshots) -> [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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to