I think Eclipse is smart enough to recompile only those classes that you actually somehow changed (even if other classes cannot be compiled). Therefore, if you turn on automatic assembly, edit the class and save it, Eclipse will recompile just that. I doubt that Eclipse will recompile the entire code base if, for example, you rename one of your variables to this class.
The bottom line is: stick to an automatic building.
If you have a special use case, then it would be nice to know what it is. Other than that, James's answer may be your best shot.
I created a small Maven project for myself in Eclipse (although this is a Maven project, the automatic build of Eclipse works fine, like in a Java project, without magic).
. |-- pom.xml |-- src | `-- main | `-- java | |-- A.java | `-- B.java // B contains erroneous "stuff" `-- target `-- classes |-- A.class // A compiles without a word `-- B.class // even though it contains errors // B compiles too ... weird
(Note that nothing is displayed under the destination folder in the package / project browser window. I may be representing things, but usually the classes and other things are listed there ... not sure.)
source share