Tortoise SVN 1.5 and ANT SVN task – Format version mismatch
Caveat: I’m a Subversion newbie and probably aren’t doing things the ‘right’ way. I’m not running a Subversion server because we don’t have any Apache servers in-house and I was able to ‘just get things happening’ by creating repositories on our WIndows network using TortoiseSVN client.
Last week I upgraded my Windows Subversion client (TortoiseSVN) to the latest version (1.5.0) to see if it would play nice with our Eclipse/FDT/Subclipse setup. To begin with everything ran just fine against repositories created using TortoiseSVN 1.4.5 as well as repositories made with the new 1.5.0 client.
Today I ran an old ANT script that checks out the contents of a repository and copies a zipped version to a network location but it falied with the following message:
svn: Unable to open an ra_local session to URL
svn: Unable to open repository
svn: Expected FS format ’2′; found format ’3′
Googling found this explanation: Subversion Users: RE: FS Format Version Mismatch
So, Subclipse seems to run just fine with the new repositories but ANT doesn’t – I guess I need to look at the svnant java task and see what can be upgraded (if anything), or revert my TortoiseSVN to 1.4.1 so I’m not creating repositories that are too new for the ANT task.
I nipped over to the home of SVNAnt and got the latest release (svnant-1.1.0-RC2), then added the new files as External JARs in Eclipse’s preferences but (apart from a slightly different format to the Console output) there’s no difference in the error message.
So it looks like I’ll be reverting to TortoiseSVN 1.4.5 for the time being, unless a solution comes my way…
Note To Self: Next time this comes up, try configuring Eclipse to use the ‘system’ version of ANT by following these instructions.
[osflash] Fatal error: exception Invalid_argument("String.create")
Today I experienced a curious MTASC error using ANT to compile from Eclipse. Here’s someone else’s description of the issue…
[osflash] Fatal error: exception Invalid_argument(“String.create”)
The only solution offered (create a new Project in Eclipse and go from there) didn’t work for me at all. After a little trial and error I found that the problem disappeared when I stopped using the (client supplied) input SWF and replaced it with my own ‘known good’ input SWF.
I’m not sure of the specifics, but the client supplied SWF was full of issues. Originally it wouldn’t compile due to library ‘duplicate linkage name’ issues, and the code (all internal to the FLA) was a spaghetti nightmare. It also took about 90 seconds to ‘Test Movie’ – in my experience it’s a prime example of ‘worst practice’ Flash development.
Anyhoo, things seem to be working OK now, so I’m migrating their content into my SWF piece by piece, but at least I can compile using my ANT scripts again.
