Should Crtl + Shift + F9 Compile / Package File also makes module/project?
In Idea 8.1.3 and 9.1M1 - Windows XP, java 1.6 - compile also starts build of whole module/project with all validations, should it behave like this?
IMO compile should only compile file with its dependencies and move classes to project compile output path and maybe also to exploded dir without buiding war or jar and making all validaions
Building whole module can be really time consuming and annoying, especially then You have validaion on build turn on and You have changed only few lines of code in one class.
Please sign in to leave a comment.
Certainly there must be more than two of us experiencing this, no? This is maddening. It's vexing enough that I need to manually compile my unit test after changing or creating it before I can successfully run the test case (I would think that executing a test case would be able to determine whether compilation is required), but when I switch to the test case's target and try to compile it, my _entire project_ is rebuilt. As far as I can tell, this is completely broken and is a huge disruption to flow. This doesn't _always_ happen, but frequently enough to be quite disruptive. I have not been able to determine what makes it do this versus the occasions when it does not.
I'm using Maia EAP 10624. I have background compilation enabled. I have toggled the setting to consider dependencies when compiling, but it doesn't seem to make a difference: the entire project is frequently rebuilt when Icompile a single file.
I figured that I'm doing something wrong, and this possibility still exists, but I've investigated settings, and searched the web and haven't found anything that really helps. If anyone can point out something that I'm missing, or else corroborate that this is actually a problem, I'd love to hear it.
So, after venting in the above post a bit, I determined something that helped much more, which was to not generate WAR files for my Web Facets, and instead use the exploded directory for IDEA-managed deployment. This keeps the WAR files from having to be rebuilt. A lot of time is still spent "copying files," but it's better than it was at least. I'm beginning to think that the legacy code base with which I work has some strange interdependencies that IDEA is detecting in certain circumstances.
If anyone has additional tips and tricks to reduce the pain of the required manual compilation, I'm still interested. I have read about the Eclipse-mode auto compile plug-in, which might be of interest, but which is not exactly what I'm looking for, though I suspect it would keep me from having to manually compile my unit tests before I can run them from within the source file with Ctrl+Shift+F10.
Hey Ian,
I'm sure we are not the only 2 suffering from this, all Idea users are
I've made issue for this:
http://www.jetbrains.net/jira/browse/IDEADEV-39262
please add your comment to it and hopefully it will by fixed soon.