[
https://issues.apache.org/jira/browse/HBASE-17192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15704860#comment-15704860
]
Sean Busbey commented on HBASE-17192:
-------------------------------------
For the curious on how I found this error:
# Searching for the odd {{null:null:null:jar}} string led to [a stack overflow
question that suggested clearing maven repository would
fix|http://stackoverflow.com/questions/21183418/i-cant-solve-maven-building-error-failure].
it didn't in this case. It also led to another [stackoverlow question that
suggested a corrupt pom in the maven repository would give the same
error|http://stackoverflow.com/questions/13648472/failure-in-maven-site-plugin-version-3]
# After clearing my local repository so that only things downloaded in the
{{mvn install && mvn site}} would be present, I looked at first lines that
weren't xml declarations and one line stood out.
{code}
$ find ~/.m2/repository/ -name '*.pom' -exec head -n 1 {} \; | grep -v "<?xml"
…
<a
href="https://blog.goodstuff.im/repo-releases/org/apache/maven/plugins/maven-assembly-plugin/2.4/maven-assembly-plugin-2.4.pom";>Moved
Permanently</a>.
…
{code}
# Grepping for that moved string showed the impacted pom
{code}
$ find ~/.m2/repository/ -name '*.pom' -exec grep -l "Moved Permanently" {} \;
/Users/busbey/.m2/repository//org/apache/maven/plugins/maven-assembly-plugin/2.4/maven-assembly-plugin-2.4.pom
{code}
# That's a core maven plugin, so it's an odd failure. Maven tracks what
repository things came from:
{code}
$ cat
/Users/busbey/.m2/repository//org/apache/maven/plugins/maven-assembly-plugin/2.4/_remote.repositories
#NOTE: This is an Aether internal implementation file, its format can be
changed without prior notice.
#Tue Nov 29 03:23:40 CST 2016
maven-assembly-plugin-2.4.pom>scala-tools.org=
{code}
# That's not the right place to get the assembly plugin. Checking the domain
confirms:
{code}
$ curl
http://scala-tools.org/repo-releases/org/apache/maven/plugins/maven-assembly-plugin/2.4/maven-assembly-plugin-2.4.pom
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a
href="http://blog.goodstuff.im/repo-releases/org/apache/maven/plugins/maven-assembly-plugin/2.4/maven-assembly-plugin-2.4.pom";>here</a>.</p>
<hr>
<address>Apache Server at scala-tools.org Port 8080</address>
</body></html>
$ curl --location
http://scala-tools.org/repo-releases/org/apache/maven/plugins/maven-assembly-plugin/2.4/maven-assembly-plugin-2.4.pom
... (html webpage that indicated 404 not found)...
{code}
# From what I can tell through old blog posts, scala-tools.org transitioned
everything to sonatype in 2012. The domain was expected to stop working in that
year, but I guess it must have just happened now.
testing fix locally now.
> remove use of scala-tools.org from pom
> --------------------------------------
>
> Key: HBASE-17192
> URL: https://issues.apache.org/jira/browse/HBASE-17192
> Project: HBase
> Issue Type: Bug
> Components: spark, website
> Affects Versions: 2.0.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Blocker
> Fix For: 2.0.0
>
>
> our pom makes use of scala-tools.org for a repository. That domain currently
> issues redirects for all URLs; for maven coordinates those redirects lead to
> 'not found' and the 'permantenly moved' HTML gets saved. this corrupts the
> local maven repository in a way that cause the mvn:site goal to give an
> opaque error:
> {code}
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 01:46 min
> [INFO] Finished at: 2016-11-28T14:17:10+00:00
> [INFO] Final Memory: 292M/6583M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project
> hbase: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed: For artifact
> {null:null:null:jar}: The groupId cannot be empty. -> [Help 1]
> [ERROR]
> {code}
> Rerunning in debug mode with {{mvn -X}} gives no additional useful
> information.
> All artifacts from scala-tools.org are now found in maven central.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
