Let me know if my answers make sense. See answers inline. Cheers John
On Apr 1, 9:20 am, Jan Limpens <[email protected]> wrote: > Hello, > > > 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. > > Fortunately it seems they are. But i think it should be an aim that any > component can only be released when all of its dependencies were already > released. Only this leads to a consistent state, I imagine. It seems it is > like that right now - if only out of luck and where I checked! Yes that is right, project are only released with released versions of their dependencies. > >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/. > > I assume they were build against trunk dependencies? No, there is no dependency replication, hence the project dependencies are whatever is in the lib folder for that project (which usually are released versions), and the lib folder is updated by the contributors, see http://github.com/castleproject/Castle.MonoRail/tree/master/lib/ for an example. > It would be great, if > this really is so, if there was an alternate build with released > dependencies. No big deal for a build server and the good test coverage > castle projects generally have, I assume... > > > 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? > > I have no idea about castle´s ar impl. never used it and I dislike the > pattern... not sure if I would be a good candidate ;) Fair enough. > > Cheers, > -jan > > > > > 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 :) > > > -- > > Jan > > > -- > > 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. > > -- > Jan -- 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.
