+5 To join in rather late, I agree that selecting individual *files* for compilation should ignore exclusions, but selecting a *package* should not ignore exclusions.
G'day. cc Jon Steelman wrote: > The intuitiveness of IDEA is so strong for me that I wonder if the > designers were not my twins separated from me at birth! ;-) > However, since IDEA almost always works as I expect it to without any > need to consult documentation or for that matter even contemplate the > issue at length, I worry when something like this crops up that isn't > immediately intuitive to me (although it would be clear to someone who > followed the posted dialog you mention, but future users of IDEA won't > have followed those posts). It is intuitive to me that an explicit > request to compile just the file itself ignores its own exclusion. It is > not as intuitive that a request to compile a package hierarchy would > just ignore exclusions. I'm not at issue with the functionality-- seems > like you need a way (maybe an option?) to compile at a higher level than > file that ignores exclusions-- just at issue with the intuitiveness. > Maybe the upcoming documentation can make it as clear as you have, or > maybe a compile option on exclusions could make it clear. Per your > advice, I'll be using "Make project" more often now and to have my > exclusions honored. > > Thanks, > Jon > > Eugene Zhuravlev wrote: > > Well, actually this behaviour was introduced on purpose. Previously all > > "compile flavours" considered exclusions. > > However there was a post in the mailing list requesting the feature. The > > reason was that when user explicitly selects a number of files to be > > compiled, he/she most likely expects the files to be compiled (something > > like "forced compilation" ) Consider also the case: you have some library > > sources in your project and do not want to compile them every time you > > compile your application sources. When library sources change, you obviously > > would like to compile them. This feature is especially useful since you > > don't need to go and temporarily include the sources into compilation. > > Normally you use (and I recommend you to) "Make project" (ctrl-F9) and > > occasionally "Rebuild project". Using make is faster and more reliable since > > dependent files are also recompiled. > > > > Best regards, > > Eugene Zhuravlev > > JetBrains, Inc / IntelliJ Software, http://www.intellij.com > > "Develop with pleasure!" > > > > "Jon Steelman" <[EMAIL PROTECTED]> wrote in message > > news:[EMAIL PROTECTED]... > > > >>Thanks for the clear explanation. There isn't any way to do a package > >>level compilation that honors exclusions? Although your explanation is > >>helpful and clear, the current behavior regarding package-level > >>compilation is counter-intuitive without your accompanying explanation. > >>When someone sees "Exclude from Compile," won't they be confused when > >>package-level compilation doesn't exclude the file? > >> > >>Thanks, > >>Jon > >> > >>Eugene Zhuravlev wrote: > >> > >>>There are several types of compilation available. You may click on the > >> > > root > > > >>>icon (project) and invoke "rebuild project". > >>>In this case the filters are considered. Alternatively you may invoke > >> > > "Make > > > >>>project" (not available from the popup menu though). This will compile > >> > > all > > > >>>modified files with the dependencies. Excluded files are considered in > >> > > this > > > >>>case too. The third way to compile something is to invoke the > >> > > compilation on > > > >>>_concrete_ classes or packages. This will compile only selected items no > >>>matter have they been modified or not and have they been excluded or > >> > > not. In > > > >>>the other words, this works like "force compile". > >>>I suspect you invoke just this action on a root package which is > >> > > effectively > > > >>>almost the same as to invoke the "rebuild the project" action except > >> > > that > > > >>>the "rebuild" action pays attention to excluded files. > >>> > >>>Best regards, > >>>Eugene Zhuravlev > >>>JetBrains, Inc / IntelliJ Software, http://www.intellij.com > >>>"Develop with pleasure!" > >>> > >>> > >>> > >>>"Jon Steelman" <[EMAIL PROTECTED]> wrote in message > >>>news:[EMAIL PROTECTED]... > >>> > >>> > >>>>Eugene, > >>>> > >>>>I break a java file so that it won't successfully compile. I compile the > >>>>package containing it from the Project view. From the "Messages - Javac > >>>>Compile" pane I click on the uncompilable class and tell it to not > >>>>compile. When I compile the package again from the Project view, it > >>>>tries to compile the broken class. By the way, if I look in the "Exclude > >>> > >>>>from Compile" list in the Compiler section of Project Properties, the > >>> > >>>>class is listed. > >>>> > >>>>Jon _______________________________________________ Eap-bugs mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-bugs
