Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/10014#issuecomment-160587382
Thanks @srowen !
---
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 f
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10014
---
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 ena
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10014#issuecomment-160586135
Merged to master/1.6
---
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 f
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/10014#issuecomment-160583952
According to the SO post this warning is added in recent versions of
assembly plugin. So I think it was not a problem before, even now it just fixes
that warning.
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10014#issuecomment-160572723
@ScrapCodes I'm pretty happy to merge this, but how did this work before,
if it was interpreted as absolute? that seems to be what the warning says.
---
If your projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10014#issuecomment-160187760
**[Test build #2124 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2124/consoleFull)**
for PR 10014 at commit
[`6e9a37b`](https://
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10014#issuecomment-160175326
**[Test build #2124 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2124/consoleFull)**
for PR 10014 at commit
[`6e9a37b`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10014#issuecomment-160155455
Merged build finished. Test FAILed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10014#issuecomment-160155458
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10014#issuecomment-160155418
**[Test build #46813 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46813/consoleFull)**
for PR 10014 at commit
[`6e9a37b`](https://g
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10014#issuecomment-160129296
Seems OK, but the warning indicates it was interpreted as an absolute path
before, but it wasn't. Hm.
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10014#issuecomment-160111896
**[Test build #46813 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46813/consoleFull)**
for PR 10014 at commit
[`6e9a37b`](https://gi
GitHub user ScrapCodes opened a pull request:
https://github.com/apache/spark/pull/10014
[SPARK-12023][BUILD] Fix warnings while packaging spark with maven.
this is a trivial fix, discussed
[here](http://stackoverflow.com/questions/28500401/maven-assembly-plugin-warning-the-assembly
13 matches
Mail list logo
