mdedetrich commented on issue #986: URL: https://github.com/apache/incubator-pekko/issues/986#issuecomment-1903348948
> SBT currently can't download the sbt plugin sources, so I can't debug, or you can publish a new sbt-osgi which can print the detail of the conflict files. Everyone has this issue. The way that sbt-plugins are developed/debugged is by using manual log/println statements (see https://www.scala-sbt.org/1.x/docs/Howto-Logging.html#Log+messages+in+a+task for how to log in a setting/task) and using `publishLocal` to deploy the sbt plugin locally and then setting the version in https://github.com/apache/incubator-pekko/blob/main/project/OSGi.scala#L46 to see whats happening. Alternately you can write a sbt-scripted test for `packageWithJVMJar := true`, one does not [currently exist](https://github.com/search?q=repo%3Asbt%2Fsbt-osgi%20path%3A%2F%5Esrc%5C%2Fsbt-test%5C%2Fsbt-osgi%5C%2F%2F%20packageWithJVMJar&type=code) and since sbt-osgi has windows as part of its CI its likely it will pick it up. > I don't think that's a hack, it's a fix for Windows users/contributors. `MergeStrategy` is a feature of sbt-assembly. sbt-assembly is not used in any pekko module aside from `protobufV3` and the stacktrace you provided at https://github.com/apache/incubator-pekko/issues/986#issue-2090937917 is for the root `actor` module and not `protobufV3`. I would help but I don't have a windows machine on hand. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
