You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@pekko.apache.org by "pjfanning (via GitHub)" <gi...@apache.org> on 2024/03/07 14:46:01 UTC

[I] migration module is not published for Scala 3 [incubator-pekko-persistence-r2dbc]

pjfanning opened a new issue, #83:
URL: https://github.com/apache/incubator-pekko-persistence-r2dbc/issues/83

   https://github.com/apache/incubator-pekko-persistence-r2dbc/blob/main/project/Dependencies.scala#L100
   
   pekko-persistence-jdbc is a test dependency - this does not support Scala 3 yet and when it does it will be a 1.1.0 release
   
   I think the simplest is just to upgrade to pekko-persistence-jdbc 1.1.0 when released.
   
   Alternatives include testing a Scala 3 build but use the pekko-persistence-jdbc_2.13 jar.
   
   `cross CrossVersion.for3Use2_13` in sbt
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org


Re: [I] migration module is not published for Scala 3 [incubator-pekko-persistence-r2dbc]

Posted by "raboof (via GitHub)" <gi...@apache.org>.
raboof commented on issue #83:
URL: https://github.com/apache/incubator-pekko-persistence-r2dbc/issues/83#issuecomment-1985392557

   I might not have all context, but from what I've seen I'd lean towards upgrading to pekko-persistence-jdbc 1.1.0 when released. Is there any particular downside to that approach?
   
   `CrossVersion.for3Use2_13` is great for 'leaf' projects but can lead to problems 'downstream' when used in libraries: for example when the transitive library releases a version for Scala 3 but the library using `for3Use2_13` is still using the cross-built version, a project could get in trouble trying to load both. Also I'm not sure how moving from using `for3Use2_13` to not using `for3Use2_13` in a later version might impact binary compatibility.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org


Re: [I] migration module is not published for Scala 3 [incubator-pekko-persistence-r2dbc]

Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #83:
URL: https://github.com/apache/incubator-pekko-persistence-r2dbc/issues/83#issuecomment-1983661799

   wdyt @mdedetrich @raboof @He-Pin @Roiocam @samueleresca @gmethvin @nvollmar ?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org