Comments on: Brand New Compiler Mode in IntelliJ IDEA 12 Leda

By: Jim W

Jim W — Tue, 18 Dec 2012 19:56:20 +0000

For projects with multiple modules containing source, the display of errors in the “Problems” tab populated by automake, and those files outlined in red in the project pane, only appear to take into account errors in the module where the error was originated.

For instance, if module A contains an interface that contains implementors in modules A, B, and C, and I change the interface in A to force an error with automake options turned on, the errors reported by the automake and those files outlined in red in the project pane only include the implementation in A. However, if I open the implementors in B or C, then those errors are immediately shown in the project pane. It’s as if the automake did compile the code in modules B and C, but fails to render them to the project pane or to the errors reported by the automake.

This of course makes determining quickly all the errors produced by a non-automated change (one not created by a refactoring) more difficult to determine.

Is there some view option I’m missing, or is this a feature that is coming soon?

By: stevo

stevo — Mon, 05 Nov 2012 22:34:12 +0000

hello, i have the same issue as Lukasz.
when I remove setter that is used in other classes, nothing happens. no red underscore on the affected classes / tree. but when I’ve added the setter back, the underscore disappears in few seconds..

(IDEA: 122.639)

cheers, stevo

By: Sebastiano Pilla

Sebastiano Pilla — Fri, 02 Nov 2012 10:26:53 +0000

@batto: I second Nick’s point, if some code is broken then the only sensible thing to do is to remove it or to fix it. The compiler/IDE should not make this decision for the developer.

By: Wesslan

Wesslan — Fri, 02 Nov 2012 04:41:47 +0000

I have version 122.694 but when I go to preferences->Compiler I can’t see \Use out-of-process build for project compilation\, just \Use external build\.

By: Joakim

Joakim — Wed, 24 Oct 2012 13:07:02 +0000

Wow, I’m late to the party as I just found this. Sounds like great news, though!

How do I hook up the AspectJ bytecode weaver to this new compiler mode?

By: Dave

Dave — Wed, 10 Oct 2012 20:17:11 +0000

I’d like to second the request for a remote compiler - being able to use the resources of a fast machine for compilation is a big benefit for us road warrior/telecommute types.

In addition, parallelizing the build (maven style or better) would be fantastic. Parallelizing the build across arbitrary remote backends would be bliss! (far quicker compile times, much better utilization of hardware in a dev team).

By: Christian

Christian — Thu, 04 Oct 2012 11:19:24 +0000

Hey guys,
I’m running 122.395 and I’m getting OOMEs from the new compilation process because it is always using the following (hardcoded?) settings

-XX:MaxPermSize=150m -XX:ReservedCodeCacheSize=64m -Xms350m -Xmx700m

The memory settings for javac at
Settings > Compiler > Java Compiler > javac > Maximum Heap Size (MB)
seem to be ignored by the new compilation process as I’ve set this to 2048.

is there any other way to overwrite the default memory settings?

Kind regards,
Christian

By: Stephane Nicoll

Stephane Nicoll — Sat, 04 Aug 2012 10:17:44 +0000

The rewrite of the annotation processor management in Leda still misses a very important point: you may want to trigger annotation processor in production code and in test code.

Right now, the UI allows you to specify ONE directory where the generated source files will be stored. That’s obviously not going to work in case you are in this case with a build tool, like Maven who generates this by default in two separate locations. Worse, the user experience is pretty bad since you easily get an error because you have a duplicated source file (idea generating in its own directory, maven in another).

There are also weird issue related to annotation processor. There is a sample project that reproduces these issues, please have a look at http://youtrack.jetbrains.com/issue/IDEA-60774#comment=27-366379

Thanks!

By: batto

batto — Tue, 24 Jul 2012 12:26:10 +0000

@Nick

> “Running with errors” feature is stupid. If the code does not run, it should be fixed; there is no point in being “intelligent” and running in half-broken way, wasting developer time by testing code which, for all practical purposes, runs non-deterministically, because it has been “patched” by the IDE.

Because some unfinished and UNREALTED code in your project doesn not compile doesn’t mean that you can’t compile & run COMPILABLE code. I like IDEA for being good all-purpose Java IDE that lets me write code how I like. On the other hand I hate doctrine tellers like you.

I’m working on some algorithm that depends on some common code. Friend sends me his version with tests in main() that depends on same common code. So I create a class in IDEA and paste it there. I try to run it but I can’t because my algorithm code is unfinished. So I add dumb things like “return null”, comment that, comment whole file, …

You enterprise folks and your doctrines…

By: Lukasz

Lukasz — Wed, 18 Jul 2012 14:26:27 +0000

Eugene I don’t see my answer I’ve posted last week (don’t know why ), so again:

I’ve enabled “automake” option and what I expect is to see errors when a class cannot be compiled (like the above example with setter). Right now I have to switch to other application (another window) and switch back to see red underscore on the affected classes. It looks like to invoke autocompile I must take an action (like it was with autosaving sometime ago).