You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Eric Chang (JIRA)" <ji...@apache.org> on 2018/07/27 17:01:00 UTC
[jira] [Comment Edited] (SPARK-24895) Spark 2.4.0 Snapshot
artifacts has broken metadata due to mismatched filenames
[ https://issues.apache.org/jira/browse/SPARK-24895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559996#comment-16559996 ]
Eric Chang edited comment on SPARK-24895 at 7/27/18 5:00 PM:
-------------------------------------------------------------
[~kiszk] for maven, you may need 3.5.2 which includes this fix: https://issues.apache.org/jira/browse/MNG-6240. It seems others have mentioned upgrading maven alone doesn't always work so I suspect you may need to upgrade spotbugs too as [~yhuai] suggested.
I think the spotbugs error [https://github.com/spotbugs/spotbugs-maven-plugin/issues/21] mentioned some errors on the aether resolver.
I think maven install will give you an error that looks like the first error in the bug description. Regarding verification of apache repo artifacts, you can check the maven-metadata.xml file by going to a link like this one (this is for spark-core):
[https://repository.apache.org/content/groups/snapshots/org/apache/spark/spark-core_2.11/2.4.0-SNAPSHOT/maven-metadata.xml]
was (Author: ericfchang):
[~kiszk] for maven, you may need 3.5.2 which includes this fix: https://issues.apache.org/jira/browse/MNG-6240
I think the spotbugs error [https://github.com/spotbugs/spotbugs-maven-plugin/issues/21] mentioned some errors on the aether resolver.
I think maven install will give you an error that looks like the first error in the bug description. Regarding verification of apache repo artifacts, you can check the maven-metadata.xml file by going to a link like this one (this is for spark-core):
https://repository.apache.org/content/groups/snapshots/org/apache/spark/spark-core_2.11/2.4.0-SNAPSHOT/maven-metadata.xml
> Spark 2.4.0 Snapshot artifacts has broken metadata due to mismatched filenames
> ------------------------------------------------------------------------------
>
> Key: SPARK-24895
> URL: https://issues.apache.org/jira/browse/SPARK-24895
> Project: Spark
> Issue Type: Bug
> Components: Build
> Affects Versions: 2.4.0
> Reporter: Eric Chang
> Assignee: Eric Chang
> Priority: Major
> Fix For: 2.4.0
>
>
> Spark 2.4.0 has Maven build errors because artifacts uploaded to apache maven repo has mismatched filenames:
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-banned-dependencies) on project spark_2.4: Execution enforce-banned-dependencies of goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce failed: org.apache.maven.shared.dependency.graph.DependencyGraphBuilderException: Could not resolve following dependencies: [org.apache.spark:spark-mllib-local_2.11:jar:2.4.0-SNAPSHOT (compile), org.apache.spark:spark-network-shuffle_2.11:jar:2.4.0-SNAPSHOT (compile), org.apache.spark:spark-sketch_2.11:jar:2.4.0-SNAPSHOT (compile)]: Could not resolve dependencies for project com.databricks:spark_2.4:pom:1: The following artifacts could not be resolved: org.apache.spark:spark-mllib-local_2.11:jar:2.4.0-SNAPSHOT, org.apache.spark:spark-network-shuffle_2.11:jar:2.4.0-SNAPSHOT, org.apache.spark:spark-sketch_2.11:jar:2.4.0-SNAPSHOT: Could not find artifact org.apache.spark:spark-mllib-local_2.11:jar:2.4.0-20180723.232411-177 in apache-snapshots ([https://repository.apache.org/snapshots/]) -> [Help 1]
> {noformat}
>
> If you check the artifact metadata you will see the pom and jar files are 2.4.0-20180723.232411-177 instead of 2.4.0-20180723.232410-177:
> {code:xml}
> <metadata modelVersion="1.1.0">
> <groupId>org.apache.spark</groupId>
> <artifactId>spark-mllib-local_2.11</artifactId>
> <version>2.4.0-SNAPSHOT</version>
> <versioning>
> <snapshot>
> <timestamp>20180723.232411</timestamp>
> <buildNumber>177</buildNumber>
> </snapshot>
> <lastUpdated>20180723232411</lastUpdated>
> <snapshotVersions>
> <snapshotVersion>
> <extension>jar</extension>
> <value>2.4.0-20180723.232411-177</value>
> <updated>20180723232411</updated>
> </snapshotVersion>
> <snapshotVersion>
> <extension>pom</extension>
> <value>2.4.0-20180723.232411-177</value>
> <updated>20180723232411</updated>
> </snapshotVersion>
> <snapshotVersion>
> <classifier>tests</classifier>
> <extension>jar</extension>
> <value>2.4.0-20180723.232410-177</value>
> <updated>20180723232411</updated>
> </snapshotVersion>
> <snapshotVersion>
> <classifier>sources</classifier>
> <extension>jar</extension>
> <value>2.4.0-20180723.232410-177</value>
> <updated>20180723232411</updated>
> </snapshotVersion>
> <snapshotVersion>
> <classifier>test-sources</classifier>
> <extension>jar</extension>
> <value>2.4.0-20180723.232410-177</value>
> <updated>20180723232411</updated>
> </snapshotVersion>
> </snapshotVersions>
> </versioning>
> </metadata>
> {code}
>
> This behavior is very similar to this issue: https://issues.apache.org/jira/browse/MDEPLOY-221
> Since 2.3.0 snapshots work with the same maven 3.3.9 version and maven deploy 2.8.2 plugin, it is highly possible that we introduced a new plugin that causes this.
> The most recent addition is the spot-bugs plugin, which is known to have incompatibilities with other plugins: [https://github.com/spotbugs/spotbugs-maven-plugin/issues/21]
> We may want to try building without it to sanity check.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org