Sorry Tuna... I must explain something more...What we wanted to achieve with NH-Contrib and NH-Forge was have a place where NH-Committers and NH-Community may work together and eventually increase the number of committers (well... I mean increase the number of good developers working in NHibernate). What I saw is projects, piece of code, extensions and so on all "out-side" NHibernate "main-stream". If a new user would start with NH need a code-hunter to find all useful things to work with NH. I had accept the situation for prj related with NH but not strictly related to core-stuff (for that I'm not insisting about NHibernate.ApplicationBlock project). What is more hard to accept, for me, is see extensions and NH-custom-compilation without a single notification to the NH development team (no post here nor JIRA). Well... hard to accept but I know that there is nothing to do... perhaps what we can do is find what is useful and implement it in the trunk directly.
About Artorius : as you know "Artorius" is only the code-name of a future piece of NHibernate core. I start the prj out-side NH only because I would like implement it as a real injectable QueryTranslator without touch, much as possible, the existing code. In Hibernate the AST parser is part of the core and, in some place, you have a "spaghetti-code"; I don't want do the same in NH. 2009/1/8 Fabio Maulo <[email protected]> > 2009/1/8 Tuna Toksöz <[email protected]> > >> >> What do you have in mind with "usefull stuff available in various diff. >> projects?" > > > Mean that I'm tired to see a lot of prj extending NH-Core when we can > extend it directly in the core it self. > This list is to talk about what is acceptable and what is not but in the > last few months even us (committers) are not using the list as expected > (expected form me...). > -- > Fabio Maulo > -- Fabio Maulo
