You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@pekko.apache.org by "raboof (via GitHub)" <gi...@apache.org> on 2024/04/28 11:27:39 UTC
[I] rethink `cassandra-launcher` approach [pekko-persistence-cassandra]
raboof opened a new issue, #192:
URL: https://github.com/apache/pekko-persistence-cassandra/issues/192
We're using `sbt-assembly` in an unusual way for cassandra-launcher - I'm not sure `sbt-assembly` really promised to do what we ask it to do here.
This causes trouble trying to update of `sbt-multi-jvm` or `sbt-assembly`.
--
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] rethink `cassandra-launcher` approach [pekko-persistence-cassandra]
Posted by "raboof (via GitHub)" <gi...@apache.org>.
raboof closed issue #192: rethink `cassandra-launcher` approach
URL: https://github.com/apache/pekko-persistence-cassandra/issues/192
--
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] rethink `cassandra-launcher` approach [pekko-persistence-cassandra]
Posted by "raboof (via GitHub)" <gi...@apache.org>.
raboof closed issue #192: rethink `cassandra-launcher` approach
URL: https://github.com/apache/pekko-persistence-cassandra/issues/192
--
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] rethink `cassandra-launcher` approach [pekko-persistence-cassandra]
Posted by "Roiocam (via GitHub)" <gi...@apache.org>.
Roiocam commented on issue #192:
URL: https://github.com/apache/pekko-persistence-cassandra/issues/192#issuecomment-2155792314
After some digging out in #206, `cassandra-launcher` has no users to `sbt-assembly`, but `cassandra-bundle` is used.
I think the `sbt-assembly` usage was in the "box", but the `launcher`build was a little problem.
Based on document: [https://www.scala-sbt.org/1.x/docs/ Classpaths.html# Unmanaged+vs+managed
](https://www.scala-sbt.org/1.x/docs/Classpaths.html#Unmanaged+vs+managed), Maybe we don't need to manage uber jar in the build
--
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] rethink `cassandra-launcher` approach [pekko-persistence-cassandra]
Posted by "raboof (via GitHub)" <gi...@apache.org>.
raboof commented on issue #192:
URL: https://github.com/apache/pekko-persistence-cassandra/issues/192#issuecomment-2154416094
hmm, this still seems to be brittle, breaking the build when plugins change (e.g. #205)
--
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