Collecting Feature Matrices... Continued. Game Engines CMS

Now it's time to extend my collection of Feature Matrices.

First of all, there will be the List of Game Engines from English Wikipedia. It just includes a wiki table with rows for engines and columns for features. There are also a few versions of this page for other languages. But some of them (Russian and Ukrainian, for example) do not include columns for specific features, only textual descriptions.

Then, there is an old-time CMS Matrix which allows you to Compare Content Management Systems. This is a site similar to the WikiMatrix, but based on a CMS system rather than a wiki engine.

Collecting Feature Matrices... Started, or Feature Matrix of Feature Matrices

Now I am starting my collection of feature comparison matrices. The main feature of this post is that I am going to compare features of helpful feature matrices I've found in the Internet. This is a kind of research, but its intermediate result should always be accessible, shouldn't it? Eventually, I am going to start somewhere a project named "Feature Matrix Engine" (OK, I stated this idea here, so it won't escape now). Of course, if it still does not exist.

The descriptions of matrices will be placed on this blog's separate page which will glow in the main menu of this blog. Suggesting new items for the collection is welcome in the comments to the page or to this post.

Today Continuous integration FM, Wiki Engines FM and Game Engines FM have just been added and partially described.

(Early) subversion 1.7 does not copy URLs with externals to working copy

Issue

Basically, subversion 1.7 Windows command line client cannot make svn copy URL -> WC if the URL contains externals. It adds it to the working copy index, but cannot finish the operation due to fail like this:


svn: E720005: Can't move 'C:\svncopy-tools\svncopy_2pgsxIK_6s\stable1\.svn\tmp\svn-256CA474' to 'C:\svncopy-tools\svncopy_2pgsxIK_6s
\stable1\ExternalsContainer': Access is denied.

Here you can find the zipped reproducing script I have constructed according to recommendations.

Versions that have the issue: 1.7.1, 1.7.2.
Versions that do not have the issue: 1.6.*

UPD:  The issue is acknowledged in dev@subversion.apache.org. But there is still no any estimate when it will be fixed. At the moment, it is being discussed if they have to include the code of the fix into Windows client only, or into all clients supported.

Solution.

Regrettably, I found no solution at the moment. As a workaround, you can use subversion 1.6 client, if you really need this workflow. I really need it, because this command workflow is used in svncopy.pl contribution script, and this script is used in my environment.

I think, we have to report the bug and wait for fix. I have reported it to users@subversion.apache.org, as recommended on http://subversion.apache.org/docs/community-guide/issues.html, and then it has been moved forward with reporting this issue to subversion development team.

Subversion 1.7, file & folders manipulation and Checksum mismatch error

Issue
In Subversion 1.6, we have got accustomed to manipulating working copy sub-directories as we wish, having a way to easily restore broken folder working copy. We performed it by deleting the problem folder and getting it fresh again by running svn update command.

After upgrading to 1.7, during such manipulation, we often encounter error like this:

svn: E155017: Checksum mismatch for 'D:\project\Aggregation\Service.cs':
   expected:  c446841fc97da2f6399ac77e334f2be2
   recorded:  0a896afb3a1923f11ef3794e2aae428b

Any attempt to remove folder and get it updated again does not fix the problem. Checksum mismatch appears on commit, revert or other operations with the working copy.

Cause
Subverion 1.6 stored the working copy cached repository information, like base revision files and their hashes, in every directory. Owing to this, a lot of folders .svn were located in the working copy, and we had to deal with them if we tried to copy or move parts of our working copy without exporting them. But this allowed such manipulation as I described above.

Subverion 1.7 stores this stuff in the working copy root only (for externals, it stores it in the root of an external working copy too).


Solution (workaround)
Instead of just deleting folder and then updating it, you perform a hack with the depth of the problem folder, setting it first to empty, then to infinity:


D:\project\Aggregation\> svn update --set-depth empty
D         Service.cs
Updated to revision 156.


D:\project\Aggregation\> svn update --set-depth infinity
A         Service.cs
Updated to revision 156.

It will remove the cached information about the problem directory from the working copy "cash-hash", and then restore it again with the actual information from the repository. So the error should disappear.

Related links

• http://glob.bushi.net.nz/glob/2007/02/14/subversion-checksum-mismatch-easy-workaround/

This link is about Checksum mismatch error too, but it seems to solve another problem, and not related to 1.6-1.7 upgrade issues.

here's how we check out a second copy of the relevant directory, and swap it in. optionally then copying over any other corrupted files etc. you may need to add salt or sugar to suit your specific situation (ie, in my example, there are no subdirectories blocked by the corrupted file)

1. PROBLEM: i can't check in the file 'lib/objects/blah.ext' because i get the error:
   

   svn: Checksum mismatch for '.svn/text-base/blah.ext'; expected: 'f8d45250f7df5561635854165862fdd8', actual: '644f85c4befa671150c5c6ec5fad9885'

Target framework for test project

Issue

After upgrading Visual Studio solution from 2008 (10.0) to 2010 (11.0) version, all test projects are automatically upgraded to using .Net Framework 4.0. If you try to set it to other values (3.5 or 2.0), it prevents this action by showing the following message:

---------------------------
Microsoft Visual Studio
---------------------------
Attempted re-targeting of the project has been canceled. You cannot change the specified .NET framework version or profile for a test project.
---------------------------
OK
---------------------------

Cause

Issue is reported to Microsoft Connect and closed as Won't fix. They did not explain why in the discussion, but I think this is due to some difficulty with Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll library compatibility.

Solution/Workaround

It works if you created your testing project by Visual Studio, but did not actually use VS testing engine and included other testing engine (e.g. NUnit). You just need to remove the guid for Test projects ({3AC096D0-A1C2-E12C-1390-A8335801FDAB} - see list) from ProjectTypeGuids property of the project file (*.??proj). This project type is not required for unit testing by other engines.

Otherwise, if you use Microsoft Visual Studio unit testing, try using some combination of workarounds described here.

Used links:

• INFO: List of known project type Guids (=>)
• Other solution (workaround - exclude from solution)
• More workarounds