Community
Participate
Working Groups
My project is organized as follow: src/java <--- contains the java source code plugin.xml <--- plugin.xml file for my RCP application build.xml <-- created by right clicking by using the "PDE Tools-> Create Ant Build file" The created build.xml is created by PDE to automate building of an eclipse RCP application. So, I tried it out, and entered >> ant no problem so far. Then I wanted to clean the workspace, and made >> ant clean Then the build file created by PDE erased my src/java source directory, and I lost two days of work! This could have been evited if I the ${build.result.folder} property had an other default. It should not show into the src folder, which is often used to store user-edited sources.
What version of eclipse are you using? There were 2 bugs fixed in 3.2.0 for this kind of problem. See bug 126984 and bug 125432. If neither of these are the case for you, please give us the contents of your plug-in's build.properties file.
Created attachment 48097 [details] my plug-in's build.properties file.
I'm using eclipse 3.2, so both bug should be fixed. I attached my build.properties file, see comment #2 In the build.properties, the properties bin.includes and source.src/java both contains src/java. Note that I didn't create this file myself. Btw, I also choose to "Create a new Java Project" with different source and output folder then I created my Plug-in project.
This bug is also active on 4.0 RC2 when using the CDT tool in combination with ant build scipts. We also lost several days of typing. In CDT it can be avoided by making sure that the 'clean' selection in the 'workplace build behaviour' tab is not selected.
Let's target 3.4... hopefully someone grabs this for bugday adding context...
Created attachment 82629 [details] mylyn/context/zip
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.