Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Replacement of symbolic links is no longer working #610

Closed
ufroehling opened this issue Feb 4, 2015 · 4 comments
Closed

Replacement of symbolic links is no longer working #610

ufroehling opened this issue Feb 4, 2015 · 4 comments
Milestone
20150226

Comments

@ufroehling
Copy link

I have a symbolic link with name=XyTeam and path=.MyApp/XyTeam/TrunK. Now i try to replace it i by entering the existing name and the new desired path = .MyApp/XyTeam/ReL11 and click on the Create/Replace button. I then get the error message "... already has a child named XyTeam ".

Version is the latest from 20150114.
In our live version 20131110 the replacement is still possible and used regularly.
@mwarhaftig
Copy link
Contributor

Hi Ufroehling, thanks for the detailed info on the bug, was able to recreate and will look into the cause.

mwarhaftig added a commit to mwarhaftig/fitnesse that referenced this issue Feb 18, 2015
@mwarhaftig
Issue unclebob#610 - Allow Sym Link rename/replace on existing Sym Link.
c4238a5
@mwarhaftig
Copy link
Contributor

Commit b47bea tightened the Symbolic Link behavior but also introduced the bug you encountered. Submitted pull request to resolve.

@mwarhaftig
Copy link
Contributor

Did a little more research and don't think b47bea introduced the issue. Most likely it was later changes to FileSystemPageFactory.createSymbolicPage (bug only started happening with release 20140630). The fix remains the same.

amolenaar added a commit that referenced this issue Feb 19, 2015
@amolenaar
Merge pull request #639 from mwarhaftig/issue610
97692a1 
Issue #610 - Allow Sym Link rename/replace on existing Sym Link.
@amolenaar amolenaar added this to the Next release milestone Feb 23, 2015
@amolenaar
Copy link
Collaborator

fixed by Matt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
20150226
Development

No branches or pull requests
3 participants
@amolenaar @mwarhaftig @ufroehling