IntelliJ 2017.1.3 Eclipse Compiler throws NullPointerException

When make large sweep code changes across our portfolio, we often make use of the automatically build project option in conjunction with the Eclipse compiler in order to see in the IDE what files have compiler failures.  Unfortunately, after upgrading to 2017.1.3, this seems to no longer function and aborts with a NullPointerException.

The stack trace:

Information:Eclipse compiler 4.6.2 was used to compile java sources
Error:java: Internal error:
java.lang.NullPointerException
at org.eclipse.jdt.internal.compiler.tool.EclipseFileManager.concatFiles(EclipseFileManager.java:167)
at org.eclipse.jdt.internal.compiler.tool.EclipseFileManager.handleOption(EclipseFileManager.java:619)
at java.compiler/javax.tools.ForwardingJavaFileManager.handleOption(ForwardingJavaFileManager.java:99)
at org.jetbrains.jps.javac.JavacFileManager.handleOption(JavacFileManager.java:99)
at org.jetbrains.jps.javac.JavacMain.compile(JavacMain.java:85)
at org.jetbrains.jps.incremental.java.JavaBuilder.compileJava(JavaBuilder.java:483)
at org.jetbrains.jps.incremental.java.JavaBuilder.compile(JavaBuilder.java:339)
at org.jetbrains.jps.incremental.java.JavaBuilder.doBuild(JavaBuilder.java:256)
at org.jetbrains.jps.incremental.java.JavaBuilder.build(JavaBuilder.java:214)
at org.jetbrains.jps.incremental.IncProjectBuilder.runModuleLevelBuilders(IncProjectBuilder.java:1263)
at org.jetbrains.jps.incremental.IncProjectBuilder.runBuildersForChunk(IncProjectBuilder.java:940)
at org.jetbrains.jps.incremental.IncProjectBuilder.buildTargetsChunk(IncProjectBuilder.java:1012)
at org.jetbrains.jps.incremental.IncProjectBuilder.buildChunkIfAffected(IncProjectBuilder.java:903)
at org.jetbrains.jps.incremental.IncProjectBuilder.buildChunks(IncProjectBuilder.java:736)
at org.jetbrains.jps.incremental.IncProjectBuilder.runBuild(IncProjectBuilder.java:384)
at org.jetbrains.jps.incremental.IncProjectBuilder.build(IncProjectBuilder.java:192)
at org.jetbrains.jps.cmdline.BuildRunner.runBuild(BuildRunner.java:138)
at org.jetbrains.jps.cmdline.BuildSession.runBuild(BuildSession.java:295)
at org.jetbrains.jps.cmdline.BuildSession.run(BuildSession.java:125)
at org.jetbrains.jps.cmdline.BuildMain$MyMessageHandler.lambda$channelRead0$0(BuildMain.java:236)
at org.jetbrains.jps.service.impl.SharedThreadPoolImpl.lambda$executeOnPooledThread$0(SharedThreadPoolImpl.java:42)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1161)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:844)

Is there some type of workaround or patch that we can apply to get this functionality workable again?