repository

I am using FluentValidation to validate my service operations. My code looks like: using FluentValidation; IUserService { void Add(User user); } UserService : IUserService { public void Add(User user) { new UserValidator().ValidateAndThrow(user); userRepository.Save(user); } } UserValidator implements FluentValidation.AbstractValidator. DDD says that domain layer have to be technology independent. What I am doing is using a validation framework instead of custom exceptions. It's a bad idea to put validation framework in the domain layer? Just like the repository abstraction? Well, I see a few

I have forked a repository on github some time ago, made a small change and pushed the change back to my github fork. The original repository has changed since. I would like to merge the changes from the original repository to my fork. I am new to both git and github, and I need specific commands how to do it. git remote add {name} {Public Clone URL} git pull {name} master git push Example: git remote add bret git://github.com/bret/watir.git git pull bret master git push Simply add original repo as a remote and merge your fork with it; then push merged fork to github. There's also a ruby gem

I have a "docs" folder in a Subversion repository named "project". I've come to the conclusion that it should really be kept under a separate Subversion repository named "project_docs". I'd like to move the "docs" folder ( and all of its revisions ) to the "project_docs" repository. Is there a way to do this? Samuel If you have access the repository itself (not a working copy), you should be able to dump the current repository, filter it to only include information about the docs folder, and load it into the other repository. Would be something like this: svnadmin dump /svn/old_repos > .

First, I know about this: How would you organize a Subversion repository for in house software projects? Next, the actual question: My team is restructuring our repository and I'm looking for hints on how to organize it. (SVN in this case). Here's what we came up with. We have one repository, multiple projects and multiple svn:externals cross-references \commonTools /*tools used in all projects. Referenced in each project with svn:externals*/ \NUnit.v2.4.8 \NCover.v.1.5.8 \<other similar tools> \commonFiles /*settings strong name keys etc.*/ \ReSharper.settings \VisualStudio.settings \trash /

I'm converting everything over to Git for my own personal use and I found some old versions of a file already in the repository. How do I commit it to the history in the correct order according the the file's "date modified" so I have an accurate history of the file? I was told something like this would work: git filter-branch --env-filter="GIT_AUTHOR_DATE=... --index-filter "git commit path/to/file --date " --tag-name-filter cat -- --all Chris Johnsen The advice you were given is flawed. Unconditionally setting GIT_AUTHOR_DATE in an --env-filter would rewrite the date of every commit. Also,