Community
Participate
Working Groups
I am working on a Java project with more than 20000 Java files. Not surprisingly, it takes a LONG time to build this project from scratch. We do integration builds weekly and the class files and other artifacts produced are installed by individual developers. Each individual developer typically modifies only a few files. Often these files depend on many classes in the larger codebase but the larger codebase does not depend on these changes. So, setting up an Eclipse workspace/project(s) for this application is quite time-consuming because of the initial, complete build. This would perhaps be tolerable except for the fact that, for no apparent reason, during development Eclipse appears to repeat the full project/workspace build. As far as I can tell, this is not triggered by large numbers of java files being newer than their class files or by large numbers of class files being dependent on a modified Java file. What's needed is a mechanism to insure that builds include *only* the strictly necessary Java files. It would be very desirable if a mechanism could be found to speed up initial creation of very large projects like these. Failing that, however, Eclipse needs to treat the information gleaned from the initial build as a "precious" resource.
"This would perhaps be tolerable except for the fact that, for no apparent reason, during development Eclipse appears to repeat the full project/workspace build." If this is true, then its a bug & we need your help to track it down. Are you sure builds are not failing & reporting errors on the project? If this happens, the next build is a full build since the previous one did not complete.
> Are you sure builds are not failing & reporting errors on the project? > If this happens, the next build is a full build since the previous one did not > complete. Yes, it is possible that the previous build failed. Let me make sure I understand what you are saying. Are you saying that if there are compilation errors with a single Java file in the project, the next time I do a "Build Project", the Java builder will try to recompile all Java files in the project? This doesn't seem like a desirable strategy does it?
"Are you saying that if there are compilation errors with a single Java file in the project..." No, normal compile errors do not cause builds to fail. But if a major error is detected (such as a bogus classpath or missing prereq project), then the build of the project is aborted since we would likely generate 1000's of errors for missing types, etc. Just keep an eye out for errors on the project & see if they are attached to the project itself. When this happens you should fix the problem before trying to do anything else.
Please reopen once you know that the full builds are not caused by 'failed' builds due to classpath errors, etc.
