dbuild
dbuild copied to clipboard
lightbend-labs
Multi-project build tool, based on sbt.
If: - You use ivy build system - You are resolving a `bundle` OSGi artifact from maven - You have a `set-version` clause. It appears that the republished artifact drops...
There seems to be a mismatch concerning compiler-interface, in certain cases. For instance, in one test case the sbt jar published after the compilation of sbt is: `org.scala-sbt/compiler-interface_2.11.0-dbuildx1317a1280278e3f43e6d797a110a8f1a71fe410e/0.13.1-dbuildx7efb24a03fb92a1fec9a58adf4d9f9ad17ff018e/jars/compiler-interface-src_2.11.0-dbuildx1317a1280278e3f43e6d797a110a8f1a71fe410e.jar` but the...
Make sure that the builds can be run in parallel. more info from @cunei on this.
This means we should be using the same mechanisms as sbt to prevent "which repository this came from" information from corrupting the cache. However, we should be able to share...
the failures look like: ``` [info] published ivy to /home/runner/.ivy2/local/com.typesafe.dbuild/build_2.10/0.9.18/ivys/ivy.xml [8396](https://github.com/lightbend-labs/dbuild/actions/runs/3569309105/jobs/5999133281#step:5:8397) java.lang.IllegalStateException: Ivy file not found in cache for com.typesafe.dbuild#dbuild;0.9.18! [8397](https://github.com/lightbend-labs/dbuild/actions/runs/3569309105/jobs/5999133281#step:5:8398) at sbt.ResolutionCache.getResolvedModuleDescriptor(ResolutionCache.scala:52) [8398](https://github.com/lightbend-labs/dbuild/actions/runs/3569309105/jobs/5999133281#step:5:8399) at org.apache.ivy.core.deliver.DeliverEngine.deliver(DeliverEngine.java:111) [8399](https://github.com/lightbend-labs/dbuild/actions/runs/3569309105/jobs/5999133281#step:5:8400) at org.apache.ivy.Ivy.deliver(Ivy.java:601) [8400](https://github.com/lightbend-labs/dbuild/actions/runs/3569309105/jobs/5999133281#step:5:8401)...
