Community
Participate
Working Groups
this is good for, e.g., handling jsp files: i have tomcat compiling my jsps on-the-fly, i'd like to make changes in some jsp so they will be saved both under my source tree and under tomcat's webapps folder. this feature is available in dreamweaver and is very useful
I assume you are looking for more than just File > Save As... I guess you want the file to be saved to multiple places every time it is saved? One approach is to use linked resources. See Help > Contents > Workbench User Guide > Tasks > Working with projects, folders, and file > Creating linked resources. This feature allows you to link a file to another file in the file system (much like Unix symbolic links). In fact, since you are running on Linux, you can use Unix symbolic links instead of Eclipse linked resources.
about the symlinks suggestion. this will not work for me since the build takes the source jsps and copies them to the webapp's folder. if both are the same, things will fail. furthermore, the build puts other things in the webapp's folder (classes, configuration files), so i cannot just symlink it as a whole to my source folder
i also checked linked resources, and it seems (from the help at least) this is not good, since eclipse doesn't recognize a linked resource as two physical entities, rather as one pointing to the other. and about 'save as..', yep. i'd like the file to be saved in two places every time i save it. mirroring best describes this i think. also, because there are a lot of files, i wouldn't want to configure this per-file. rather, per folder, so i would tell eclipse that one folder mirrors another. thereafter, every change to the latter will be saved also in the former.
This RFE is now 2 years old. Is there any chance of anyone noticing (fixing) it?
Currently there are no plans to address this.
"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.
