-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
r20948 introduced 2 problems:
1) Old symlinks are no longer removed.. the "if exists" check that was added
does not account for the baseDir, so it always thinks the symlink does not
exist. Creation of the symlink then fails because of the conflict with existing
link. (this applies to overwrite of "latestStable", "latestSuccessful" links, etc.)
2) Creation of symlinks via PosixAPI does not work because it does not account
for the baseDir.
The targetPath parameter does not need to be absolute.. at least, I don't know
of any system where symlinks can't be relative.
Example: ln -s somefile /tmp/testlink
This creates /tmp/testlink as a symlink pointing to "somefile" in the same
directory (so /tmp/somefile).
The fix in this issue was making sure the 2nd param is an absolute path, so
the symlink is created in the right location.
If you have other clues as to why symlinks weren't created on your setup, please
let us know.. can you share your environment details?