Hey All,
Just a heads up. I merged this patch last night which caused the Spark
build to break:
https://github.com/apache/spark/commit/397d3aae5bde96b01b4968dde048b6898bb6c914
The patch itself was fine and previously had passed on Jenkins. The
issue was that other intermediate changes merged sin
Sounds like this is pretty specific to my environment so not a big
deal then. However, if we can safely exclude those packages it's worth
doing.
On Sat, Nov 15, 2014 at 7:27 AM, Ted Yu wrote:
> I couldn't reproduce the problem using:
>
> java version "1.6.0_65"
> Java(TM) SE Runtime Environment (
I couldn't reproduce the problem using:
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)
Since hbase-annotations is a transitive dependency, I created the following
pull request to exclude
Sorry for the late reply.
I tested my patch on Mac with the following JDK:
java version "1.7.0_60"
Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)
Let me see if the problem can be solved upstream in HBase hbase-annotations
modu
FWIW I do not see this on master with "mvn -DskipTests clean package".
I'm on OS X 10.10 and I build with Java 8 by default.
On Fri, Nov 14, 2014 at 8:17 PM, Patrick Wendell wrote:
> A recent patch broke clean builds for me, I am trying to see how
> widespread this issue is and whether we need to
I think in this case we can probably just drop that dependency, so
there is a simpler fix. But mostly I'm curious whether anyone else has
observed this.
On Fri, Nov 14, 2014 at 12:24 PM, Hari Shreedharan
wrote:
> Seems like a comment on that page mentions a fix, which would add yet
> another prof
Seems like a comment on that page mentions a fix, which would add yet another
profile though — specifically telling mvn that if it is an apple jdk, use the
classes.jar as the tools.jar as well, since Apple-packaged JDK 6 bundled them
together.
Link: http://permalink.gmane.org/gmane.comp.java
A work around for this fix is identified here:
http://dbknickerbocker.blogspot.com/2013/04/simple-fix-to-missing-toolsjar-in-jdk.html
However, if this affects more users I'd prefer to just fix it properly
in our build.
On Fri, Nov 14, 2014 at 12:17 PM, Patrick Wendell wrote:
> A recent patch bro
A recent patch broke clean builds for me, I am trying to see how
widespread this issue is and whether we need to revert the patch.
The error I've seen is this when building the examples project:
spark-examples_2.10: Could not resolve dependencies for project
org.apache.spark:spark-examples_2.10:j
