Community
Participate
Working Groups
Build 3.2m4 File > Import > General > Existing projects into Workspace When importing & copying, there could be an option to ignore derived files. Copying the entire output folders from Java projects can take a lot of time, considering the build states will be gone anyway, and first build will trigger a full build...
I just ran into the same problem. Copying jdt.ui from source must have taken over 10 minutes. Using the windows explorer this takes less than a minute.
I also noticed the poor performance. It took hours in my case to import several (big) source plugins. I doubt it only has to do with copying derived files though.
Which plugin(s) are you importing that take so long?
This would be a good option to have available. It would likely also be a useful option to have for the file system and archive wizards, and perhaps for the export wizards too. That being the case, an API change would be required to properly implement this for all the import wizards.
I am not sure how we can ignore importing derived files since they are being imported from the file system or an archive file, which do not have the concept of derived files like the workspace does. Am I misunderstanding what you are requesting? However, I could see how ignoring derived files on export might be a nice feature to have.
I also would like to have an option to ignore derived resources when exporting a project. It would be very convenient for emailing a project, for instance.
As ignoring derived files while importing is rather impossible, then at least (as Thierry said) there should be a possibility to export the project without the derived files. Then this option should be available in following export wizards: - Archive file - File System - Jar file anywhere else?
Actually I also think there should be possibility for excluding linked resources when exporting. In my main project I use linked resources pointing on other projects of the workspace, and I generally don't wish to export the linked projects along with my main project.
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
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.
