Skip to content

Anorm JAR includes Joda and the Scala library #658

@gaeljw

Description

@gaeljw

Originally raised at scala/scala3#22890 (comment) by @ThomasGrt and identified by @aamiguet:

I suspect the issue in https://github.com/ThomasGrt/scala-3.7.1-reproduce-cap-error comes from anorm 2.8.1, its jar contains the Scala library (checking with jar -tf anorm_3-2.8.1.jar | grep ^scala).

This seems to be fixed in 2.9.0-M1 as the jar is much leaner and the project compile just fine without warnings.

Content of the Anorm 2.8.1 JAR:

$ unzip -l anorm_3-2.8.1.jar | grep "scala/"
        0  01-01-2010 01:00   scala/
     1227  01-01-2010 01:00   scala/$times$colon$.class
     1380  01-01-2010 01:00   scala/$times$colon.class
     1463  01-01-2010 01:00   scala/$times$colon.tasty
     3679  01-01-2010 01:00   scala/CanEqual$.class
      755  01-01-2010 01:00   scala/CanEqual$derived$.class
     2543  01-01-2010 01:00   scala/CanEqual.class
     3968  01-01-2010 01:00   scala/CanEqual.tasty
      214  01-01-2010 01:00   scala/CanThrow.class
     1261  01-01-2010 01:00   scala/CanThrow.tasty
...

Content of the Anorm 2.9.0-M1 JAR:

$ unzip -l anorm_3-2.9.0-M1.jar| grep "scala/"
# Nothing :)

As mentionned above, this is already fixed in version 2.9.0-M1. I couldn't pinpoint the commit that fixed this though or maybe it is cbde028 🤔

The concrete consequence of this (as mentionned in scala/scala3#22890) is that users of Anorm can not upgrade to Scala 3.7+ because there was an incompatible change in the Scala library and having both Scala 3.3 (embedded from Anorm) + Scala 3.7 in the classpath creates a conflict.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions