spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: compilation error in Catalyst module
Date Wed, 06 Aug 2014 20:54:04 GMT
Forgot to do that step.

Now compilation passes.


On Wed, Aug 6, 2014 at 1:36 PM, Zongheng Yang <zongheng.y@gmail.com> wrote:

> Hi Ted,
>
> By refreshing do you mean you have done 'mvn clean'?
>
> On Wed, Aug 6, 2014 at 1:17 PM, Ted Yu <yuzhihong@gmail.com> wrote:
> > I refreshed my workspace.
> > I got the following error with this command:
> >
> > mvn -Pyarn -Phive -Phadoop-2.4 -DskipTests install
> >
> > [ERROR] bad symbolic reference. A signature in package.class refers to
> term
> > scalalogging
> > in package com.typesafe which is not available.
> > It may be completely missing from the current classpath, or the version
> on
> > the classpath might be incompatible with the version used when compiling
> > package.class.
> > [ERROR]
> >
> /homes/hortonzy/spark/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/trees/package.scala:36:
> > bad symbolic reference. A signature in package.class refers to term slf4j
> > in value com.typesafe.scalalogging which is not available.
> > It may be completely missing from the current classpath, or the version
> on
> > the classpath might be incompatible with the version used when compiling
> > package.class.
> > [ERROR] package object trees extends Logging {
> > [ERROR]                              ^
> > [ERROR] two errors found
> >
> > Has anyone else seen the above ?
> >
> > Thanks
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message