Those of you who script regularly, probably have started to maintain scripts in an external config management system rather than inside of the medini project. To link scripts that live outside the medini project to a medini project, one can use Eclipse "Linked Folders" and use "Synchronize Documents" on the config folder, which was described in another article.
That works nicely for batch scripts. However, it does not work when scripts are loaded inside profile properties. The reason is manyfold and tricky to explain and even trickier to resolved. Fortunately there is an alternative solution and that is "Windows symbolic links", something you may know from Linux. The magic is done by the tool mklink.
Assume that my project Scripting is located at C:\workspaces\MyWorkspace\Scripting and my scripts are located at C:\temp\global-scripts\. I can create a symbolic folder by using
mklink /D C:\workspaces\MyWorkspace\Scripting\config\scripts C:\temp\global-scripts\
Mind the /D which makes sure we create a symbolic folder and not a symbolic file. Now you can use "Synchronize Documents" on the config folder and you will see all scripts from the global-scripting folder in your medini project. You can edit, see and execute them. You can also use them in scripted properties without any problem!
Happy Scripting
Jan
