IIRC it didn't seem to be picking up runtime-scope dependencies in the classpath. It could be a plugin rather than scalac issue. Easy to check if you like by uncommenting, but I expect that it will have the same result. It is not so harmful; just means there classes are visible at compile time in that module when they shouldn't be used directly. On Mar 28, 2014 5:39 PM, "markhamstra" <[email protected]> wrote:
> Github user markhamstra commented on the pull request: > > https://github.com/apache/spark/pull/259#issuecomment-38940216 > > That should be all of them now, but there is a 2.10.3-specific comment > in the root pom.xml that could use some investigation @srowen > ```xml > <dependency> > <groupId>org.slf4j</groupId> > <artifactId>jcl-over-slf4j</artifactId> > <version>${slf4j.version}</version> > <!-- <scope>runtime</scope> --> <!-- more correct, but scalac > 2.10.3 doesn't like it --> > </dependency> > ``` > > > --- > 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 [email protected] or file a JIRA ticket > with INFRA. > --- >
