Community
Participate
Working Groups
Build 20020412 I have to change the project nature because I have to workaround a problem. 1. I have create a simple project SP1 2. Copy a Java project from Eclipse 1.0 and its files from another directory into SP1 3. Since the Java project does not contain the .project file from Eclipse 1.0, I have to manually change the .project and add the java builder and java nature. 4. The project does not get built even tried Rebuild Project and Build All. 5. Finally, I have to create a new java files and the project starts building.
John: Does the BuildManager perform a full or incremental build in this case? What other .metafiles should I look for deltas?
If autobuild is on, editing the .project file should trigger an incremental build. The very first build for a builder will have a null delta (eg, immediately after adding it to the .project file), but the build "kind" may still be incremental. If this isn't happening, please move the PR to me and I will investigate. The "Rebuild All" or "Rebuild Project" actions trigger full builds, and the "Build All" or "Build Project" actions trigger incremental builds. I'm not sure I understand your second question... I don't think the java builder needs to know about any .metadata files created by core.
Since the Java builder shouldn't have to look for .project changes... its all yours John. ;)
The builder gets invoked, but it is not configured properly (I guess because the .classpath file hasn't been created yet), so it doesn't build anything. Here are my steps: 1) Create a simple project S1 2) Add file A.java to S1 with valid java file contents 3) Edit the .project for S1, and change the buildspec and natures as follows: <buildSpec> <buildCommand> <name>org.eclipse.jdt.core.javabuilder</name> <arguments> </arguments> </buildCommand> </buildSpec> <natures> <nature>org.eclipse.jdt.core.javanature</nature> </natures> 4) Save this .project file. This triggers the Java builder to run, but it has not configured its build path, so it doesn't compile A.java. Philippe, I believe there was a discussion about this recently in another bug report. JDT Core should listen for changes to project descriptions, and then configure the .classpath correctly when the java nature is added to the description. The one wrinkle is if the JDT Core plugin isn't activated yet. In that case the creation of the java builder will cause the JDT Core plugin to be activated, at which point it is too late for a resource change listener to do appropriate initialization.
See also bug 12977.
This is a particular symptom of the general problem described in 12977. Once that is fixed, builders should run with no problem. *** This bug has been marked as a duplicate of 12977 ***
