Olivier Mélois

Okay my logic is faulty, instead of "resolving" the imports recursively, I should amend the current pom's xml by replacing the "imports" by what the referenced pom contains, and then...

@cvogt is there ever a case where this [getOrElse](https://github.com/Baccata/cbt/blob/1959fd6adab985f80e55b59a4f8a9f041b24533d/stage1/resolver.scala#L390) is triggered ? I'm hitting a case where there are several artifacts with different groupIds, and therefore the computation of"dependencyVersions" creates...

Could this be achieved with something similar to [ammonite's router](https://github.com/lihaoyi/Ammonite/blob/ecaed30292d811b2140a83124450ea3b82cb4dbd/amm/src/main/scala/ammonite/main/Router.scala) ? IE, when compiling the build, a macro could take care of aggregating the callable methods into a router that...

I'm experiencing the exact same issue. Product and Version [VS/VSCode]: VSCode 1.67.1 OS Version[macOS/Windows]: MacOS Monterey (12.3.1) Live Share Extension Version: v1.0.5561

@fthomas, I don't think this ticket should be closed, considering the proposed solution seems to only be working for ammonite deps that are also mentioned in an sbt build 😿

This looks like it's related to https://github.com/lihaoyi/Ammonite/issues/956

@djspiewak it is not, because what do you do with the effect once when you get a successful outcome ? You still have to run it through the dispatcher to...

I suppose it makes sense, considering how function calls will be retried in the event of an exception. Oh well 🤷‍♂️

Scala actually has this solved, and different representations of numbers can be compared accurately with a lot less edge cases. In particular, Scala libraries tend that need to support several...

The LSP has an endpoint to apply formatting. Additionally, if we had access to a tokenizer, we could have much more accurate syntactic colouring, provided at the LSP level.