> > I have no idea what the "Apache" way is regarding this. But, checking in >> the Flash Builder /Eclipse project files will make it insanely easy for >> anyone--who uses Flash Builder--to share the project. They just "import >> projects from another workspace" and it works. It's much easier than >> creating a new project. > > > That's exactly the thing, that it doesn't work like that - everyone has their source code in a different place, different project settings... if you do this in a team you will get infinite war of minor similar changes of the same property being set by one committer to X, while another committer will set it to Y and so on... that is even if everyone on the team is using the same editor... I mean, if I import your project files now I need to modify them, (.actionScriptProperties) because library location is different for me. idk...
Just another wild guess... what if your SVN client actually uses Subversion 7? They are compatible on update, but incompatible on commit with 6 (i.e. you can't commit a repository created with 7 into 6). Although I see you said it's v 6. Can you try it with --verbose option? I would very much like to hope it's not any server problem. Just having a "good" memory of how updating from Adobe SVN was usually broken :( Oh, actually, those errors in Adobe SVN were b/c of HTTP server arguing with SVN server about file path resolution. So, aren't you by any chance trying to commit a change over a file that could've been deleted recently. Especially if it was deleted manually through some thing like Tortoise repobrowser? Probably, if that is the case, you could try to do some dummy commit, and then the real commit? Best. Oleg
