Descriptors live in this github repo: http://github.com/dagda1/hornget In fact, horn is currently hardcoded to fetch descriptors from this repo only. Paul is the maintainer of this repo, but of course anyone can fork and make changes. About the stability of the builds, I'm +1 too for using fixed versions, but I'll ask on the Horn groups.
-- Mauricio On Dec 15, 7:19 pm, John Simons <[email protected]> wrote: > That's awesome news :) > > Who maintains the project descriptors? Should we maintain them and > host them in our svn? > > Reply to your questions inline > > On Dec 16, 1:39 am, Mauricio Scheffer <[email protected]> > wrote:> Paul Cowan and I have been working on the Castle descriptors for Horn. > > There are now individual descriptors for each project, like: > > > Monorail:http://hornget.net/packages/web/castle.monorail/castle.monorail-trunk > > ActiveRecord:http://hornget.net/packages/ioc/castle.activerecord/castle.activereco... > > etc > > > It needs a couple of minor adjustments (e.g. Spring being included in > > ActiveRecord) but it should work. Please check it out. > > > Now a couple of questions about this: > > > * Other than building things like Monorail + > > Facilities.ActiveRecordIntegration, what value would have a descriptor > > that builds all Castle projects? > > I myself do not see value in this, what everyone else thinks? > > > > > * Should we use fixed versions for our dependencies? > > Yes I think we should because we are now using binary dependencies and > that is the version of the dependency we support. > > Since Horn > > > > > builds do not run any tests (they could, but then they would take > > *forever*) things can break very easily. (even worse > > thanhttp://groups.google.com/group/castle-project-devel/browse_thread/thr... > > since we'd use external projects' trunks) > > > * On git migration: I added shallow clones to horn, so what I > > described > > inhttp://groups.google.com/group/castle-project-devel/msg/1fe66437349e8e46 > > would no longer be a problem. If everyone agrees, I'll duplicate the > > history in each project. It will make the transition easier and this > > way we don't need the git superproject (trunk) anymore. > > > Comments and questions welcome. > > > -- > > 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]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
