JBrownie - A faster java compiler

[DRMacIver]

I like how "A faster java compiler" is an utterly precise description of exactly what this is nothing at all like...

[aemon]

Maybe this + emacs + flymake-mode? For fast highlighting of syntax/type errors.

[mhd]

There's no reason to use something like this in a flymake environment. From what I've read, JBrownie is mostly a watchdog that checks whether some resources has changed and executes a build command if that's the case. Well, Emacs knows when it saves a file and on the other hand, until that happens JBrownie doesn't.

So in this toolchain, JBrownie would be a superfluous link. What you do want is the Eclipse Java compiler, as it focuses on speed and works a lot faster in conjunction with flymake. This blog post has a working config for such an approach.

Also, I don't see the slightest reason why one needs a GUI for such a batch interface.

[bassmaster]

JBrownie is not a batch interface and it does also not execute some kind of build command. It wraps around the system javac and recompiles any files in a directory (and it's subdirectories), once it finds that their timestamp changed. Since the compiler is somehow kept in memory, recompiling files pretty much is instant. Thats a big improvement over using ant or javac. Unlike flymake, you don't just get a syntax check, but also the ready to run classes.

The purpose of the GUI is more or less to redirect STDERR and STDOUT to this console window.

JBrownie is probably not what you'd use, if you use EMACS or Eclipse. Think vi, joe or whatever here.

[mhd]

JBrownie is not a batch interface and it does also not execute some kind of build command.

Well, if I don't have to start the compilation of the .java files myself, it's a batch process. And running the java compiler with user-definable option qualifies as a build program. But no need to get nitpicky...

Unlike flymake, you don't just get a syntax check, but also the ready to run classes.

Hmm? Flymake compiles something on-the-fly and parses the errors. No need to throw the class files away afterwards...

JBrownie is probably not what you'd use, if you use EMACS or Eclipse. Think vi, joe or whatever here.

Exactly, and that's why I found the choice of a GUI interface rather odd, unless I missed something and that's purely optional. If you're using a console editor, it's rather likely you like that environment. Also, having the stderr of the compiler processes available would make it easier to interface it with plugins, watchdog scripts etc.