cunei
commented
11 years ago That should not be a problem: 1) the binaries that are compiled by dbuild can optionally be published (in its own format) to a central repository, and retrieved from there. Therefore, once a certain version of Scala (or another project) is built from the source by dbuild, it can be published to that repository, and subsequent runs will just fetch the binaries and metadata from there, without the need to recompile. In addition: 2) I just added a new Ivy-based "build system" to dbuild: rather than compiling from source, you can also now specify that you want a certain library dependency resolved against the standard Maven/Ivy repositories: dbuild will grab the pre-built binary from there, while still checking and rewriting the various dependencies. This new feature is coming up in the next point release, due by the end of this week.
adriaanm
PR validation should be as fast as possible, so we only want to build scala once, and test various projects against it using dbuild or other build tools. Thus, it would be good to be able to just use a scala build and compile other projects using that.
Long term, this isn't really necessary, assuming our full validation will be one dbuild job, that does parallel builds etc, but that seems like a longer term thing.