I'd certainly be a fan of Castle being built only on official NH releases, but I understand the desire for the Castle trunk to work off the NH trunk (they are, after all, "latest and greatest".
Perhaps some sort of tagging of the trunk based on changes in third- party libs? For example, let's say Castle 1.0 is built on NH 2.1 GA. When you reach the point where you are going to update the NH bits to something else, tag the trunk so we have a "Castle 1.0/NH 2.1 GA" trunk (or whatever naming strikes your fancy). Just a thought... - b On Dec 29, 9:40 am, "Markus Zywitza" <[email protected]> wrote: > We're still running on an old NHibernate trunk version with some private > patches by Hammett. While I understand that this NH version is required fro > Donjon (AFAIK), I am planning to replace our current NH with a fresh trunk > version. > > This is a requirement for an upcoming release of ActiveRecord 1.0 which I > plan to release when NH2.1 reaches GA. AR should then contain NH2.1 as a > stable release cannot be built upon an unsupported NH version. > > Are there any objections on updating NH to current trunk as a preparation > for this? > > -Markus --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
