Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-207025582
Hi, All.
The original code is made by me, so I feel guilty. :)
I think Jenkins build does not show additional information for this PR
since our Jenkins build on master branches works fine.
- https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/
(JDK8 + Scala 2.11)
-
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Compile/job/spark-master-compile-maven-scala-2.10/
(JDK8 + Scala 2.10).
And, we know the JDK7 does not have this issue according to the Spark
mailing list. So, I ran the following command and found the current master
branch compiles without problem. This seems not a Scala compilation problem.
```
spark:master$ git clean -fdx
spark:master$ java -version
java version "1.8.0_77"
Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)
spark:master$ ./build/mvn -Pyarn -Phadoop-2.6 -Dhadoop.version=2.7.2 -Phive
-Phive-thriftserver -DskipTests clean compile
...
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 03:38 min
[INFO] Finished at: 2016-04-07T10:29:20-07:00
[INFO] Final Memory: 76M/871M
[INFO]
------------------------------------------------------------------------
```
After that, just `package` also works fine.
```
spark:master$ ./build/mvn -Pyarn -Phadoop-2.6 -Dhadoop.version=2.7.2 -Phive
-Phive-thriftserver -DskipTests package
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 06:02 min
[INFO] Finished at: 2016-04-07T10:50:44-07:00
[INFO] Final Memory: 79M/853M
[INFO]
------------------------------------------------------------------------
```
The real root cause of this error occurs during Scala doc generation by
**doc-jar** plugin. Is it possible to solve the real root cause by changing
`pom.xml` to reorder the plugin execution stages or something else? I've
already changed my another PR #12185 (`DESC FUNCTION` implementation)
according this PR's approach, but it's a little too limited approach for me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
