Re: Best Practice for large customizations

On 4 Dec 2008, at 05:06, jiveforums-ecm@... wrote:
> Am about to start a project using nuxeo where we will be adding a  
> significant number of new content types, workflows etc etc...
>
> I've played quite a bit with the sample project and that structure  
> seems like a valid approach for one or two content types but I could  
> imagine over time this structure could become heavy and hard to  
> maintain especially with a team of developers working on that some  
> project.
>
> I'm looking for some feedback on the best way to structure a large  
> nuxeo customization. Such as maybe structuring like the sample app  
> but separate projects for each content type or maybe a content types  
> project a separate workflow project etc.

A separate project seems way overkill to me. Just split the type,  
schema etc. definitions in several files maintained by different  
developers. You can contribute several times to the same extension  
point, be that in one or several files, in the same or in different  
projects.

Florent

--

-- 
Florent Guillaume, Head of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com   http://www.nuxeo.org   +33 1 40 33 79 87