FileSync plugin history
New in version 1.2.2 (Eclipse 3.1 and 3.2)
1) Fixed bug introduced in 1.2.1 where the project preferences timestamp would be changed each time FileSync was started for the project (thanks to Stefan Flick again for his bug report).
2) Updated JUnit test case
New in version 1.2.1 (Eclipse 3.1 and 3.2)
1) Added workspace relative mapping for *default* destination folder (idea and initial implementation contributed by Stefan Flick, thanks again).
2) Now it is possible to use Eclipse path variables for *default* destination folder. The rules are the same as described below.
3) Small bugfix, related to changing mapping file "on the fly" (old mappings could still exist in memory if not more specified in the new mapping file).
4) Fixed JUnit test case :)
New in version 1.2.0 (Eclipse 3.1 and 3.2)
1) Added workspace relative mappings for destination folders (idea and initial implementation contributed by Stefan Flick, thanks). If destination folder is workspace relative, then workspace path will be replaced through ':' char.
Example for two destination folders, one is relative to workspace:
2) Now it is possible to use Eclipse path variables for destination folders. This path variables should be defined under "Window ->Preferences ->General ->Workspace->Linked resources-> Defined path variables". Usage is restricted to the first path segment only (or to the whole string), see Javadoc for IPathVariableManager.resolvePath() on Eclipse site. For example, the SERVER_PATH could be a variable with content "E:\deploy\jboss":
3) For destination folders from inside of any known Eclipse project, automatic refresh of the destination project will be started after successful file synchronisation.
4) Added check for same source and destination folders location (no sync in this case).
5) Test plugin for JUnit testing of FileSync is available. Please if you extend FileSync, add additional test cases and send it with your contribution to me.
6) Discontinued any support for Eclipse 3.0.
7) If the %destination folder% is absolute, it should start with the device name on Windows (like "C:"), or with the slash ("/") for Linux
New in version 1.1.1 (Eclipse 3.1 and 3.2)
Fixed manual build command ("Force file synchronization"): if the autobuild was disabled for entire workspace, then it was not possible to sync files manually too.
New in version 1.1.0 (Eclipse 3.1 and 3.2)
Same codebase and same binaries for both 3.1 and 3.2 Eclipse releases.
*Removed* "auto-attach builder to project" feature from FileSync. Now project builder need be *manually* enabled (once) for each project (Project->Properties->File synchronization->Enable FileSync builder for project). The reason to remove this feature is that adding FileSync to the project means that the .project file will be modified and checked out. Usually there are much more projects which shouldn't be synchronized, so .project files should be modified only for required projects.
Fixed some smaller UI bugs.
New in version 1.0.0 (different binaries for Eclipse 3.1 and 3.2, but same codebase)
Recompiled separately for both 3.1 and 3.2 and fixed some smaller UI bugs (errors in pref.page if the setting file was deleted, missing warning if
the first source entry was added without any destination folder specified).
New in version 0.9.5 (Eclipse 3.1 only)
1) Added workaround for Java 1.4.2 bug with some 2.6.* Linux kernels (see
bug details at: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5056395).
2) added Eclipse update site.
New in version 0.9.4 (Eclipse 3.1 only)
1) Added "useCurrentDateForDestinationFiles" boolean property.
If set to true, then the current date will be set on all destination files,
instead of of the date of the source file. This value is false by default.
2) Added possibility to have multiple destination folders for one source
folder. Example property file:
#Wed Jul 27 19:02:03 CEST 2005
WARNING=DO NOT MODIFY THIS FILE IF YOU DON'T UNDERSTAND
New in version 0.9.2
Added support for Eclipse 3.1.
New in version 0.9.1
First public release. Different small GUI improvements.
Please send comments or suggestions to