I tried to reproduce the problem but couldn't. As far as I can tell when I configure a grails install via sybmolic link, it works completely transparantly.
Here's what I did.
- create a folder called 'linked' (from a terminal window in the os)
- in this folder:
ln -s <some-other-folder-with-a-bunch-of-grails-versions>/grails-1.3.4
This creates a link from linked/grails-1.3.4 to where the real grails-1.3.4 install lives.
I then opened the Grails preferences page, removed all grails installs I had there and added a new one, pointing it to linked/grails-1.3.4
I then created a new grails project for testing and looked inside its Grails Dependencies class path container.
I see that a jar like 'grails-core.jar' has attached source and when I click on a .class file in the .jar it indeed opens the correct source file.
I also see that a lot of other jars do not have source attachements(jars like 'org.springframework...').
This seems to be the exact same behavior I'm getting when I configured the grails install in a 'non-linked' fashion.
Konstantinos, are the steps described above similar to what you did to get the problem? If not, could you try to give a more detailed description of the steps needed to produce the erroneous behavior and precisely what goes wrong?
I'm certainly willing to give it another shot to try determine what the problem is and try to fix it.