Bug 544427

Summary:	How to watch/accept new files for incremental compilation
Product:	[Eclipse Project] JDT	Reporter:	Alexander Mills <alex>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	stephan.herrmann
Version:	4.11
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Alexander Mills

2019-02-13 20:06:46 EST

I was writing a lot of TypeScript, and it has `tsc --watch` for incremental builds. It builds everything and then holds all files in memory and then listens for changes to files. When a source file changes, it doesn't have to read all files into memory again, it already has them in memory.

I am looking for a compiler for java that can do what `tsc --watch` does. Is there such a thing? I was able to download and run the Java Batch Compiler from Eclipse, but it behaves like javac as far as I can tell - it builds and then exits. Is there a way to use it like a server and send it files that have changed?

Comment 1 Alexander Mills

2019-02-13 20:07:32 EST

An alternate title - is there a java compiler that can listen for file changes and hold all .class files in memory so it can compile more quickly that starting fresh each time.

Comment 2 Stephan Herrmann

2019-02-14 12:48:31 EST

(In reply to Alexander Mills from comment #1)
> An alternate title - is there a java compiler that can listen for file
> changes 

That's what JDT does within the IDE, isn't it?
This depends on a workspace where resource change events are broadcast.

> and hold all .class files in memory so it can compile more quickly
> that starting fresh each time.

.class files shouldn't be overly relevant here. Did you mean .java files?

Granted: JDT does compare .class files after compilation to compute how far code changes need to be propagated for recompilation.

Comment 3 Eclipse Genie

2021-02-04 14:48:34 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 4 Eclipse Genie

2023-04-12 11:49:44 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.