registerInputAndProcess should exist

[virtuald]

Looking at registerInputsAndProcess, it appears that it adds to the result set if the workspace is not in delta mode or if the resource is unmodified. This seems like an internal detail of sorts, would make sense to have registerInputAndProcess that contains that detail for single-input processing.

[ifedorenko]

I am not sure I understand the problem. Are you saying that BuildContext#registerAndProcessInputs returns unexpected (or at least "un-intuitive") results in some cases, or do you want similar register-and-process API that takes single File input?

If it's the former, please provide a unit test that shows the problem.

If it's the latter, I tried to introduce InputProcessor callback interface and registerAndProcessInput(File, InputProcessor) API, but that was not very convenient to use, at least without java8 lambdas. I also tried "fluent" builder approach, but did not like it either. And I do not see how to introduce registerAndProcessInput(File) without retuning null, which I believe will be inconvenient and error prone. Got other ideas?

[virtuald]

The latter.

The problem is that you have two types of workspace modes (here) -- and it seems like it would be nice for the caller to not have to know about this. Or, is the checking for delta mode just an optimization? Then in which case my complaint is less valid.

Alternative to null: You could have registerAndProcessInput(File) return an iterable? Return either empty collection or Arrays.asList(item). It's a bit weird, but less error prone.

Yet another alternative, allow registerInputs to work with a single file too, not just directories.

I agree that an inputProcessor interface would be annoying.