Large projects compilation broken?
I've been fighting with a problem recently, which can drive anybody crazy. I suspect the problem stems from the way ExternalCompiler generates the command for javac. On large project with a complex classpath it runs well over 5 KB (see http://intellij.net/forums/thread.jspa?threadID=270426&tstart=0 ) for attachments with more info.
I've tried to create a test project reproducing it, but got very strange results and couldn't nail it down (really need a loooong classpath). So, I figured it could be the problem in latest IDEA builds. So, try this to reproduce (run under JDK 1.4, there's a validation on the build for the correct JDK) and remember it's a large project and will take a while to prepare on a clean machine:
svn co http://svn.codehaus.org/mule/tags/mule-2.0.0-M2/
mvn -Dmaven.test.skip.exec=true
mvn idea:idea
Open the project and hit compile and watch it. I came to a conclusion it's not any plugin's fault, as even removing half of the default plugins (and all user ones) still give an error.
Needless to say, IDEA became merely useless :((
Andrew
Please sign in to leave a comment.
Just a blind shot - it could be the difference in the way javac processes '-classpath' in Java 1.4 and 6 (1.4 accepting only around 2KB length). If that is true try to extract classpath into a file reference via @filename.
I think everything above applies to win xp only.
Sad to see no reaction to this report. Is it because of the release hype. Then it's even more astonishing that some last-minute change has such a severe effect and goes into a final release. Yes, I'm pissed off, but try to understand - this always worked up to around 3 last EAP releases before final.
Can someone try the steps to reproduce the problem? I found no way to reproduce it in a small project.
To reiterate why this is important - you cannot compile, you cannot run a test from IDEA (because you need to compile classes first) and it just becomes a fancy editor.
Andrew
i did not try, but did try opening the pom directly from idea ?
IDEA 7 now has pretty good maven integration, and the idea:idea maven plugin was written for idea 6. As there have been a number of changes to ipr/iml files for the 7.0 release, it's possible that it would work better this way
Hello Andrew,
Creating a JIRA issue with testcase dramatically increases the chance for
a fix, in my experience.
Nagging in forums helps as well, but only when JIRA ticket has been created
in the first place :)
-tt
Oh, opening a 90 module project in IDEA with maven plugin kills it, it's just not usable, and then the generated tool projects are broken (there are some classes generated for a couple of tools project, and none of the available plugin settings fixed it). Works fine when generating project files directly by maven.
Hi Taras,
I'm involved with a huge project community as well, and understand those very clearly. In this case, however, I failed to produce a testcase (tried for a whole day), you may have noticed the original thread in JetGroovy forum.
Filing another JIRA without complete info is no better, we always try to confirm the bug in forums/lists first, I'm trying to save JetBrains folks some headache.
If the above scenario is really confirmed, JIRA will be filed, definitely ;) And I'm not whining, I'm desperately calling for a dialog.
Hello Andrew,
Ah, I missed that thread :)
I agree that the issue is pretty serious.
-tt
I narrowed it down to a single module which can be used to reproduce the problem: http://www.jetbrains.net/jira/browse/IDEA-15817