allow DirectoryDependencies on BuildBuilds

this fixes a bug where finalBuild would over eagerly go down all the way
down to the outermost build instead of stopping at the one requested.
Now it checks the new argument and stops there.

This is necessary to allow having one build depend on another build in
order to embed it in a type-safe way and have access to it’s tasks.

1 files changed, 6 insertions, 2 deletions

diff --git a/compatibility/BuildInterface.java b/compatibility/BuildInterface.java
index ebcfb99..eb60960 100644
--- a/compatibility/BuildInterface.java
+++ b/compatibility/BuildInterface.java
@@ -1,11 +1,15 @@
 package cbt;
 import java.io.*;
 
-public abstract class BuildInterface implements Dependency{
-  public abstract BuildInterface finalBuild(); // needed to propagage through build builds. Maybe we can get rid of this.
+public interface BuildInterface extends Dependency{
+  // needed to propagage through build builds. Maybe we can get rid of this.
+  public default BuildInterface finalBuild(File current){
+    return finalBuild(); // legacy forwarder
+  }
   public abstract File[] triggerLoopFilesArray(); // needed for watching files across composed builds
 
   // deprecated methods, which clients are still allowed to implement, but not required
+  public abstract BuildInterface finalBuild(); // needed to propagage through build builds. Maybe we can get rid of this.
   public abstract BuildInterface copy(Context context);
   public abstract String scalaVersion();
   public abstract String[] crossScalaVersionsArray();