<<Warning: this is very off-topic>> Hi, as I say, I'm doing it because I'll find it useful.
I'll give you the standard scenario that I'm trying to address: - You're using a distributed version of a library. - Something's going wrong, and you're not sure what. - So you'd like to debug right into the library. Now, obviously there are ways of achieving that right now, but few of them are as low friction as being able to add the library directly to your solution. I'm assuming that's easy to do, which at the moment it isn't because there's no sensible way of updating references in an automated manner. Anyway, that's why I'm writing it. I've got a need for just that functionality, so I'm building it. However, it could certainly be used to, for instance, merge Castle Core and MicroKernel together, allowing you to make modifications which span the projects and split them apart again afterwards. Now, the last bit is on the theoretical side, because we've already got a solution to the all-trunk build, but ownership wouldn't really be an issue, because the mega-solution would be an intermediate result of your build process, not a file checked into subversion. For the avoidance of doubt, I'll repeat myself: we don't need this for what we're achieving. I mentioned it since what I'm working on tangentially touches on this and could provide a solution to a related problem in the future. J 2010/1/25 John Simons <[email protected]> > Julian, what's the requirement for that? > All we need is binary dependency replication, which is what Roelof has done > in TC. > How would be the owner of these mega solutions? > I really don't get the point of it, please enlight us. > > Cheers John > > On 26/01/2010, at 9:03, Julian Birch <[email protected]> wrote: > > Exactly. Put projects together, sort out the references. It's > actually marginally easier to add projects than remove them, but I'm doing > both. > > But I agree with Roelof, you don't need it for this. However, I'm sure > it'll prove useful (to be precise, I'm sure I'll find it useful :) ) > > J > > 2010/1/25 Krzysztof Koźmic <[email protected]> > >> what do you mean solution merges? getting projects from multiple >> solutions together under one uber solution? >> >> 2010/1/25 Julian Birch <[email protected]>: >> > Just so people know, I can't guarantee when this is going to be >> finished, >> > but I'm working on enabling solution merges on Solution Transform. >> This'll >> > be a nice way of achieving trunk syncs in a likeable manner. >> > >> > 2010/1/25 Krzysztof Koźmic <[email protected]> >> >> >> >> you could use Horn to download synced trunks. There's some nice >> >> development planned for vNext of Horn I'm really looking forward to >> >> >> >> >> >> On 2010-01-25 21:56, Roelof Blom wrote: >> >> >> >> It does not yet generate a downloadble artifact with all the 'synced' >> >> projects. >> >> >> >> On Mon, Jan 25, 2010 at 6:07 PM, Tyler Burd <[email protected]> >> wrote: >> >>> >> >>> Perfect timing! I just sent an email to the users list about how to >> get >> >>> multiple projects from the buildserver that are all in sync. Thanks, >> >>> Roelof; this will be very handy! >> >>> >> >>> On Mon, Jan 25, 2010 at 9:23 AM, Roelof Blom <[email protected]> >> >>> wrote: >> >>>> >> >>>> Hi, >> >>>> >> >>>> I've added the project 'All Trunks' to TeamCity. >> >>>> >> >>>> This project is triggered when one of the following projects >> completes a >> >>>> successful build: Core, Transaction, DP, Windsor, Components and >> >>>> ActiveRecord. >> >>>> It then builds all projects that depend on the previous projects, >> using >> >>>> their *latest* build artifacts. >> >>>> >> >>>> This project exists to give us an early warning for breaking changes. >> >>>> >> >>>> It's not entirely complete (mainly depedencies from the Components >> >>>> projects are not there) yet but it covers the most important >> dependencies. >> >>>> >> >>>> See >> >>>> >> http://builds.castleproject.org/project.html?projectId=project36&tab=projectOverview >> >>>> >> >>>> Feedback is welcome, as is configuring the project for more >> dependencies >> >>>> :-) >> >>>> >> >>>> -- 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]<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]<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. > > > ------------------------------ > See what's on at the movies in your area. Find out > now<http://au.rd.yahoo.com/movies/mailtagline/*http://au.movies.yahoo.com/session-times/> > . > > -- > 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.
