My feeling is that it's a bug in horn: it does not handle switching a working copy from svn to git, I had to remove revision.horn and the working folder manually.
On Tue, Mar 2, 2010 at 6:24 AM, Paul Cowan <[email protected]> wrote: > Hi, > > Thanks for updating the descriptors. > > Most of the castle packages failed last night because castle.core is > failing. > > I get the following msbuild error message: > > error MSB4019: The imported project > "C:\hornget\.horn\ioc\castle.core\Working\Settings.proj" was not found. > Confirm that the path in the <Import> declaration is correct, and that the > file exists on disk. > > Cheers > > Paul Cowan > > Cutting-Edge Solutions (Scotland) > > http://thesoftwaresimpleton.blogspot.com/ > > > > On 2 March 2010 04:49, > <[email protected]<castle-project-devel%[email protected]> > > wrote: > >> Today's Topic Summary >> >> Group: http://groups.google.com/group/castle-project-devel/topics >> >> - GitHub Migration is Done... Starting the Castle Svn >> Shutdown<#1271d54ce69cbfea_1271d358f4b6c4c8_group_thread_0>[5 Updates] >> - TemplateEngine repository >> anomaly<#1271d54ce69cbfea_1271d358f4b6c4c8_group_thread_1>[4 Updates] >> - Re-tagged DynamicProxy >> 2.2<#1271d54ce69cbfea_1271d358f4b6c4c8_group_thread_2>[3 Updates] >> - Which wiki are we >> picking?<#1271d54ce69cbfea_1271d358f4b6c4c8_group_thread_3>[3 Updates] >> - Git line endings <#1271d54ce69cbfea_1271d358f4b6c4c8_group_thread_4>[7 >> Updates] >> - Git Migration (+ >> MsBuild)<#1271d54ce69cbfea_1271d358f4b6c4c8_group_thread_5>[2 Updates] >> - horn descriptors for >> github<#1271d54ce69cbfea_1271d358f4b6c4c8_group_thread_6>[1 Update] >> >> Topic: GitHub Migration is Done... Starting the Castle Svn >> Shutdown<http://groups.google.com/group/castle-project-devel/t/542e5c49fa5d2fee> >> >> "Henry Conceição" <[email protected]> Mar 02 12:14AM -0300 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> Hi guys, >> >> The migration from svn to github is complete and from now and on the >> Castle Svn Repository is read-only. >> >> Should take it offline right now or should we wait for some reason? >> >> Cheers, >> Henry Conceição >> >> >> >> >> John Simons <[email protected]> Mar 01 07:42PM -0800 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> Trying to find a reason to keep it, but I can't find any. >> +1 to turn it off now >> >> >> >> >> >> ________________________________ >> From: Henry Conceição <[email protected]> >> To: [email protected] >> Sent: Tue, 2 March, 2010 2:14:54 PM >> Subject: GitHub Migration is Done... Starting the Castle Svn Shutdown >> >> Hi guys, >> >> The migration from svn to github is complete and from now and on the >> Castle Svn Repository is read-only. >> >> Should take it offline right now or should we wait for some reason? >> >> Cheers, >> Henry Conceição >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Castle Project Development List" group. >> To post to this group, send email to >> [email protected]. >> To unsubscribe from this group, send email to >> >> [email protected]<castle-project-devel%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/castle-project-devel?hl=en. >> >> >> >> >> Jonathon Rossi <[email protected]> Mar 02 02:17PM +1000 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> +1 for leaving it read-only for a while. >> >> Has the experiments/attic directories been migrated somewhere. Will >> Castle >> contrib stay in svn, or will we just get people to move the projects >> into >> their own github trees? >> >> >> -- >> Jono >> >> >> >> >> "Henry Conceição" <[email protected]> Mar 02 01:33AM -0300 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> The experiments and attic trees are under the castle repo. >> >> By Castle Svn Shutdown I meant it only for svn/castle. svn/contrib >> will be up and running until we decide the destiny of contribs repo (a >> subject for another thread, in my opinion). >> >> Cheers, >> Henry Conceição >> >> >> >> >> >> >> >> Jonathon Rossi <[email protected]> Mar 02 02:45PM +1000 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> 2010/3/2 Henry Conceição <[email protected]> >> >> > The experiments and attic trees are under the castle repo. >> >> OK, that's good to know. I see those and all the branches and tags at >> http://github.com/castleproject/castle. I've been a little slow on >> following >> the changes lately, sorry. >> >> Since everything is migrated and horn has been updated, I agree with >> John >> that I can't find a reason to keep the castle svn repo available, >> unless >> users still wanted to be able to find things by svn revision (to debug >> a >> production issue for example). >> >> By Castle Svn Shutdown I meant it only for svn/castle. svn/contrib >> > will be up and running until we decide the destiny of contribs repo >> (a >> > subject for another thread, in my opinion). >> >> A separate thread, agreed. >> >> >> >> -- >> Jono >> >> >> >> Topic: TemplateEngine repository >> anomaly<http://groups.google.com/group/castle-project-devel/t/d317a7b8a581cdb1> >> >> Mauricio Scheffer <[email protected]> Mar 01 07:38PM -0800 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> There's something weird in the TemplateEngine repo. There is a merge >> ( >> >> http://github.com/castleproject/Castle.Components.TemplateEngine/commit/127963fa7aaebd4c32a4448164ceb9883b60475e >> ) of two trees: one of them leads to the first commit (r1 of SVN) >> while the other leads to r338 of SVN : >> >> >> http://github.com/castleproject/Castle.Components.TemplateEngine/commit/1ce264313d5557beb1dc9015ccbe49e3171a8d81 >> >> If it's ok with everyone I'll rewrite the last couple of commits to >> remove this merge, leaving only the tree that comes from r1. >> >> Cheers, >> Mauricio >> >> >> >> >> John Simons <[email protected]> Mar 01 07:42PM -0800 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> Mauricio, go ahead (have no idea what you are talking about but it >> sounds right :) ) >> >> Cheers >> John >> >> >> >> >> ________________________________ >> From: Mauricio Scheffer <[email protected]> >> To: Castle Project Development List < >> [email protected]> >> Sent: Tue, 2 March, 2010 2:38:40 PM >> Subject: TemplateEngine repository anomaly >> >> There's something weird in the TemplateEngine repo. There is a merge >> ( >> >> http://github.com/castleproject/Castle.Components.TemplateEngine/commit/127963fa7aaebd4c32a4448164ceb9883b60475e >> ) of two trees: one of them leads to the first commit (r1 of SVN) >> while the other leads to r338 of SVN : >> >> >> http://github.com/castleproject/Castle.Components.TemplateEngine/commit/1ce264313d5557beb1dc9015ccbe49e3171a8d81 >> >> If it's ok with everyone I'll rewrite the last couple of commits to >> remove this merge, leaving only the tree that comes from r1. >> >> Cheers, >> Mauricio >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Castle Project Development List" group. >> To post to this group, send email to >> [email protected]. >> To unsubscribe from this group, send email to >> >> [email protected]<castle-project-devel%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/castle-project-devel?hl=en. >> >> >> >> >> John Simons <[email protected]> Mar 01 07:45PM -0800 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> Btw, >> >> Is there any way to get rid of "forked from >> mausch/Castle.Facilities.ActiveRecordIntegration" on all projects? >> eg >> http://github.com/castleproject/Castle.Facilities.ActiveRecordIntegration >> >> Cheers >> John >> >> >> >> >> ________________________________ >> From: Mauricio Scheffer <[email protected]> >> To: Castle Project Development List < >> [email protected]> >> Sent: Tue, 2 March, 2010 2:38:40 PM >> Subject: TemplateEngine repository anomaly >> >> There's something weird in the TemplateEngine repo. There is a merge >> ( >> >> http://github.com/castleproject/Castle.Components.TemplateEngine/commit/127963fa7aaebd4c32a4448164ceb9883b60475e >> ) of two trees: one of them leads to the first commit (r1 of SVN) >> while the other leads to r338 of SVN : >> >> >> http://github.com/castleproject/Castle.Components.TemplateEngine/commit/1ce264313d5557beb1dc9015ccbe49e3171a8d81 >> >> If it's ok with everyone I'll rewrite the last couple of commits to >> remove this merge, leaving only the tree that comes from r1. >> >> Cheers, >> Mauricio >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Castle Project Development List" group. >> To post to this group, send email to >> [email protected]. >> To unsubscribe from this group, send email to >> >> [email protected]<castle-project-devel%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/castle-project-devel?hl=en. >> >> >> >> >> Mauricio Scheffer <[email protected]> Mar 01 08:03PM -0800 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> Done. I'll remove my repos later so it doesn't show up as "forked from >> mausch..." >> >> -- >> Mauricio >> >> >> >> >> Topic: Re-tagged DynamicProxy >> 2.2<http://groups.google.com/group/castle-project-devel/t/9d998fc17cb2cfb0> >> >> Mauricio Scheffer <[email protected]> Mar 01 06:49PM -0800 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> Just fixed the tags for 2.2.0-beta1 and 2.2.0, they were pointing to >> other trees, so don't worry if you see some "forced-update" message >> when fetching. >> Also, it's weird but I couldn't find the 2.1.0 tag ( >> >> http://fisheye2.atlassian.com/browse/castleproject/tags/dynamicproxy-2.1.0 >> ) >> >> -- >> Mauricio >> >> >> >> >> "Henry Conceição" <[email protected]> Mar 01 11:56PM -0300 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> The tags were supposed to be automatically migrated right? Or did I >> screw it? >> >> >> Cheers, >> Henry Conceição >> >> >> >> On Mon, Mar 1, 2010 at 11:49 PM, Mauricio Scheffer >> >> >> >> >> Mauricio Scheffer <[email protected]> Mar 01 07:23PM -0800 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> At least in DynamicProxy, I think somehow they stayed where they were >> before filter-branching. I'll check other repos. >> >> >> >> >> Topic: Which wiki are we >> picking?<http://groups.google.com/group/castle-project-devel/t/a4f1866f50b90821> >> >> "Daniel Hölbling" <[email protected]> Mar 01 01:10PM +0100 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> I also like STW a lot. It also happens to be a .NET solution so if >> changes >> are needed they should be fairly straightforward to implement. >> >> 2010/2/23 Henry Conceição <[email protected]> >> >> >> >> >> >> "Henry Conceição" <[email protected]> Mar 01 11:44AM -0300 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> No. My castle's top priority is the git/msbuild migration. >> >> >> Cheers, >> Henry Conceição >> >> >> >> >> >> >> >> "Henry Conceição" <[email protected]> Mar 01 10:27PM -0300 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> Here it is: http://stw.castleproject.org/ >> >> @committers: If you want to be an admin, send me a pm for me after the >> registration. >> >> Cheers, >> Henry Conceição >> >> >> >> >> >> >> Topic: Git line >> endings<http://groups.google.com/group/castle-project-devel/t/de27675cd7f08259> >> >> "Daniel Hölbling" <[email protected]> Mar 01 01:14PM +0100 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> I suggest disabling the core.autocrlf feature completely. It really >> screws >> up your commits if for some reason tools modify the line-endings. >> Nothing is more annoying than having a commit where you get a >> deletion/insert for every line in the document although you only >> changed 2 >> LOC.. >> In fact, I got so annoyed about this that I even blogged about that: >> http://www.tigraine.at/2010/02/03/disable-autcrlf-in-msysgit/ >> >> I still have no real explanation how inconsistent file endings started >> to >> occur on a Windows-only environment, but it happened a lot to me in >> the >> past, and I've seen too many commits being completely unreadable due >> to >> this. >> >> greetings Daniel >> >> On Sat, Feb 27, 2010 at 4:16 PM, Mauricio Scheffer < >> >> >> >> >> Roelof Blom <[email protected]> Mar 01 01:47PM +0100 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> +1, just leave the line endings as they are. >> >> I have a feeling that inconsistent line endings could be caused by R#, >> at >> least the current EAP seems to have something to do with this. Note >> that you >> can set VSNET to warn you about inconsistent line endings: >> Tools|Options|Environment|Documents => Check for consistent line >> endings on >> load. >> >> -- Roelof. >> >> >> >> >> >> "Daniel Hölbling" <[email protected]> Mar 01 02:44PM +0100 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> R# may have something to do with it. Hope they fix it. But as long as >> the >> build scripts and our tools can cope with different line endings in >> different files I don't feel like we should at all care about them in >> our >> repos. >> >> >> >> >> >> Roelof Blom <[email protected]> Mar 01 02:55PM +0100 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> It's a problem with some of the unit tests. >> >> >> >> >> >> Mauricio Scheffer <[email protected]> Mar 01 06:32AM -0800 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> I do this on my git repositories at work and it works like a charm, >> but it doesn't seem to be the case with Castle. With autocrlf false, >> certain files are LF-only, like WindsorContainer.cs, while other files >> are CRLF. >> As I understand it, autocrlf true makes sure that everything is CRLF >> on Windows. >> >> Cheers, >> Mauricio >> >> >> >> >> >> Craig Neuwirt <[email protected]> Mar 01 08:31AM -0600 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> Henry, >> >> I was trying to work on WCF Facilities release over the weekend and >> noticed >> when I pulled from origin I had a bunch of files that always showed >> dirty >> files. Setting *git config core.autocrlf false* had not affect either. >> When I did a diff on the files it only show permission changes which >> led me >> to the conclusion that some recent commits have altered file >> permissions. I >> tried to tell git to ignore this global with *git config --global >> core.filemode false*, but it didn't work. However, setting this >> locally >> only did. So *git config core.filemode false* got things rolling >> again. >> >> -craig >> >> >> >> >> >> "Daniel Hölbling" <[email protected]> Mar 01 04:47PM +0100 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> I had the problem with autocrlf. Upon checkout of the tree it marked >> all >> files as dirty that had the wrong file endings. From what I understood >> msysgit will change the line endings upon checkout to be consistent >> with >> your setting. I'm still for just disabling autocrlf.. >> >> >> >> >> Topic: Git Migration (+ >> MsBuild)<http://groups.google.com/group/castle-project-devel/t/25d1e94eeeb89354> >> >> Patrick McEvoy <[email protected]> Mar 01 05:24AM -0800 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> Ok, build server has latest mono 2.6 branch as of today. I kicked off >> a Facilities - ActiveRecordIntegration build and unfortunately we're >> having the same issue... >> >> Cheers P >> >> >> >> >> >> Roelof Blom <[email protected]> Mar 01 02:54PM +0100 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> Many thanks for making the effort Patrick. >> >> I've checked the source of xbuild's Parameters.cs and it looks like we >> pass >> xbuild a parameter like this: '/p:' or '/property:', so no name at >> all. >> >> Is it possible for you to see what the complete commandline is that's >> passed >> to xbuild? >> >> -- Roelof. >> >> >> >> >> Topic: horn descriptors for >> github<http://groups.google.com/group/castle-project-devel/t/1b320d99fd85e4e0> >> >> Roelof Blom <[email protected]> Mar 01 01:51PM +0100 >> ^<#1271d54ce69cbfea_1271d358f4b6c4c8_digest_top> >> >> Just letting you know that my horn fork has git and msbuild support >> (with >> all modes that NAnt supported) for most of our projects: >> http://github.com/roelofb/hornget/tree/dev >> >> I've sent a pull request to Paul Cowan. >> >> -- Roelof. >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Castle Project Development List" group. >> To post to this group, send email to >> [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<castle-project-devel%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/castle-project-devel?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]<castle-project-devel%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. > -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
