Add asserts for warnings/notes about compile-testing HOT 3 CLOSED

Yep. That has always been on the radar, but we just hadn't needed it.

from compile-testing.

On my fork I created a draft to support warnings as I'm in need of it. This required quite a lot of refactoring in JavaSourcesSubject to avoid code duplication.

    ASSERT.about(javaSource())
      .that(file)
      .compilesWithoutError()
      .withWarningContaining("redundant cast to java.lang.String")
      .in(file).onLine(20).atColumn(16);

or

    ASSERT.about(javaSource())
      .that(file)
      .compilesWithoutError().andNoWarnings();

The latter currently allows for creating contradictory assertions like .compilesWithoutError().andNoWarnings().withWarningContaining(...). I'm not quite sure what would be the best way to integrate the chaining of those methods into the fluent API. Doing this properly would bloat the FileClause, LineClause etc. as they all would need to distinguish between normal compilations and compilations that yielded no warnings.

from compile-testing.

This shipped

from compile-testing.