After two months of background thinking and after reading this
article (http://www.theserverside.com/articles/content/
ManagingSourceCode/article.html) today, I think I have finally
understood the current structure.
The different set of modules is actually exactly what is needed, to
break down in small manageable pieces the whole system. And to have
knowledgeable people on each part. I like it.
A bit of IoC in there would actually make the dependencies easier to
manager, and if you had 100 engineers to work on the project it'd be
good. :P
Also, a 20 lines introduction on how to build magnolia using maven 2
and why it's done this way before the next release could boost your
sales (hum maybe..) and the number of contributors !!
By the way, who said french people would not change their mind ?
haha ...
Thanks a lot,
Nicolas,
On Oct 4, 2005, at 2:06 PM, Nicolas wrote:
As a side note, the breaking into small pieces will greatly prevent
external contribution, as you really have to keep the developer
documentation up to date.I was afraid Magnolia would go the same
way as Jackrabbit...
Someone said on the list, keep it simple and it's working don't
break it.
Anyway, I guess it's none of my business and if it's makes the life
of the magnolia devs easier then all is good. My 2 yens ...
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
