Scala compile errors downstream of Spark 2 Scala 2.11 artifacts #1218

Closed
heuermh opened this Issue Oct 18, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@heuermh
Member

heuermh commented Oct 18, 2016

As in #1217, not sure if this is an issue or something that we knew would happen.

When updating a downstream application dependency from ADAM version 0.19.1-SNAPSHOT to ADAM Spark 2 release version 0.20.0, scala-maven-plugin reports new compiler errors:

[ERROR] bad symbolic reference. A signature in package.class refers to type
compileTimeOnly in package scala.annotation 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] adam-commands/src/main/scala/c/g/h/a/commands/ADAMCommandsMain.scala:29:
Reference to constructor ADAMMain in class ADAMMain should not have survived past type
checking, it should have been processed and eliminated during expansion of an enclosing
macro.
[ERROR]     new ADAMMain(defaultCommandGroups.union(commandGroup))(args)
[ERROR]     ^

[ERROR] adam-commands/src/main/scala/c/g/h/a/commands/CountAlignments.scala:39:
Reference to variable inputPath in class CountAlignmentsArgs should not have survived past type
checking, it should have been processed and eliminated during expansion of an enclosing
macro.
[ERROR]   var inputPath: String = null
[ERROR]       ^

[ERROR] adam-commands/src/main/scala/c/g/h/a/commands/CountAlignmentsPerRead.scala:39:
Reference to variable inputPath in class CountAlignmentsPerReadArgs should not have survived past type
checking, it should have been processed and eliminated during expansion of an enclosing
macro.
[ERROR]   var inputPath: String = null
[ERROR]       ^
[ERROR] four errors found

Don't have a fix yet.

@ryan-williams

This comment has been minimized.

Show comment
Hide comment
@ryan-williams

ryan-williams Oct 18, 2016

Member

JFWIW I ran in to similar looking problems recently when publishing artifacts for one scala version, where the uploaded POM did not have its maven properties / dependencies set to that version, resulting in downstream compilation invocations with 2.10 and 2.11 classes on the classpath.

Member

ryan-williams commented Oct 18, 2016

JFWIW I ran in to similar looking problems recently when publishing artifacts for one scala version, where the uploaded POM did not have its maven properties / dependencies set to that version, resulting in downstream compilation invocations with 2.10 and 2.11 classes on the classpath.

@heuermh

This comment has been minimized.

Show comment
Hide comment
@heuermh

heuermh Oct 18, 2016

Member

Yep, this is not an issue with ADAM, rather an issue with move_to_scala... scripts.

Fixed in heuermh/adam-commands@7ced78a

Member

heuermh commented Oct 18, 2016

Yep, this is not an issue with ADAM, rather an issue with move_to_scala... scripts.

Fixed in heuermh/adam-commands@7ced78a

@heuermh heuermh closed this Oct 18, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment