FYI, it appears that Castle.Facilities.NHibernateIntegration still hasn't been released in 2010 and someone who was looking for it was confused by the Castle website so they asked a question on StackOverflow:
http://stackoverflow.com/questions/3097901/where-do-you-download-nhibernate-castle-facility/ The projects page doesn't contain a live download link: http://www.castleproject.org/castle/projects.html And the downloads page doesn't even include the facility at all: http://www.castleproject.org/castle/download.html I answered the StackOverflow question, but I thought I would mention the Castle website issues here in case anyone cared to follow up. The HornGet website is my favorite way to answer these kinds of questions, but apparently that will be going away soon as the build descriptors aren't being kept up to date: http://groups.google.com/group/horn-development/browse_thread/thread/6e81c9cfc206a4ee Thanks. -Michael Maddox http://www.capprime.com/software_development_weblog/ 2010/4/1 Krzysztof Koźmic <[email protected]>: > 2010/4/1 John Simons <[email protected]>: >> Krzysztof, I agree with everything you said. >> >> All I was saying is that at the moment we do not have a well defined >> release manager role in Castle, and in order to ensure that releases >> are always compatible we do need one, otherwise releases may not be >> compatible all the time. >> >> So are you proposing to create a release manager role in Castle? And >> I'm talking about a single person looking after Castle releases (the >> same as project leaders). >> >>> For vNext I would like to release the projects in a more synchronized >>> manner. >> Assuming we ever get the left over projects released! > > What's left? > AR facility? Henrik's projects (what's up with that? I though he was > about to release them last week or more ago?) and NHFacility *cough* > Tuna *cough*. > >> >> Cheers >> John >> >> On Apr 1, 7:49 pm, Krzysztof Koźmic (2) <[email protected]> wrote: >>> John, what do you mean that they may be not compatible? >>> >>> The whole idea of releasing against current released version of the >>> dependencies is that they ought to be compatible. >>> For vNext I would like to release the projects in a more synchronized >>> manner. >>> That means release Core (incl. DP) and Windsor and as many facilities >>> as possible on the span of very short time (like 2,3 days) and in >>> addition to keeping them in separate .zip packages as it is now, >>> provide a Castle.zip that would like a snowball accumulate all the >>> other projects as they get released soon after that. >>> >>> Jan is not the first person to request that and I don't really see any >>> reason to not provide such package. >>> >>> Krzysztof >>> >>> On 31 Mar, 23:16, John Simons <[email protected]> wrote: >>> >>> > Hi Jan, >>> >>> > Thanks for your feedback/suggestions, very much appreciated. >>> >>> > > if I could just download the whole castle stack in one big package or >>> >>> > at least state that all released packages are version compatible. >>> > I guess the problem is that they may not be compatible! We are trying our >>> > best to keep the sf.net packages compatible, but because Castle projects >>> > are now independent we cannot guarantee that they are always compatible. >>> >>> > >Ideally, is there a place where I just can dl dlls build against the >>> >>> > release versions of core, dynproxy2 etc? >>> > You should be able to d/l the compiled assemblies for the projects that >>> > haven't been released yet from our build >>> > server,http://builds.castleproject.org/. >>> >>> > Regarding the projects that haven't been released yet: >>> > Castle.Facilities.ActiveRecordIntegration -> No one seems to care for >>> > this project, we are still looking for a project leader, do you want to >>> > be the leader for this project? >>> > Castle.Facilities.AutomaticTransactionManagement -> Not sure why it >>> > hasn't been released yet, Henrik any news on this front? >>> > Castle.Facilities.Logging -> This project is now released as part of >>> > Core, seehttp://www.castleproject.org/castle/projects.html >>> > Castle.Facilities.NHibernateIntegration -> Not sure why it hasn't been >>> > released yet, Tuna any reason to not release this facility? >>> >>> > Cheers >>> > John >>> >>> > ________________________________ >>> > From: Jan Limpens <[email protected]> >>> > To: [email protected] >>> > Sent: Thu, 1 April, 2010 6:30:47 AM >>> > Subject: dependencies and facilities >>> >>> > Hello, >>> >>> > I am trying to get my rhino.commons up to date in therms on what castle >>> > dlls it uses (among others). >>> >>> > By downloading each and every package from the sourceforge repository and >>> > checking each and every version number of every dll contained therein I >>> > found out, that all of those seem to combine. hurray! >>> > ... where I must say, you could have spared me this tedious work, if I >>> > could just download the whole castle stack in one big package or at least >>> > state that all released packages are version compatible. >>> > Being separate projects does not necessarily mean, they have to be >>> > (exclusively) placed in separate zip files. This can be of value, but for >>> > the typical user, I am pretty sure, it would be much easier to just get >>> > everything that was released and is compatible as on simple and single >>> > download. >>> >>> > What I am missing are the facilities... >>> > Castle.Facilities.ActiveRecordIntegration >>> > Castle.Facilities.AutomaticTransactionManagement >>> > Castle.Facilities.Logging >>> >>> > (and for my own projects Castle.Facilities.NHibernateIntegration) >>> >>> > commons mainly needs them just for it's tests to pass, but still - where >>> > are they? >>> > Ideally, is there a place where I just can dl dlls build against the >>> > release versions of core, dynproxy2 etc? >>> >>> > Thanks, and please don't be offended by my criticism, at least it does >>> > not come without a suggestion on how to make it better :) >>> > I suppose I will have to get the sources somewhere and build / fix it >>> > against the releases. You can be sure, I would be glad if I could save me >>> > that hassle... >>> >>> > Thanks for all the great software :) -- 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.
