cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew C. Oliver" <acoli...@apache.org>
Subject Re: [Proposal] Cocoon Organization
Date Wed, 31 Jul 2002 20:02:53 GMT
Konstantin Piroumian wrote:

>An alternative proposal:
>    - Cocoon 2 Micro Edition (C2ME): basic functionality/components
>    - Cocoon 2 Standard Edition (C2SE): most frequently used
>functionality/components
>    - Cocoon 2 Enterprise Edition (C2EE): complete suit, including flow
>control, form handling, DB-stuff, etc.
>  
>
dunno about that...smells like sun's crappy scheme...then again...it 
sells. . . . (thats no indication of
quality)

>But this does not require any sub-projects, but a more sophisticated build.
>
>I don't think that development of Cocoon itself will be any easier if it'll
>be split into subprojects. How would you syncronize all of them? Are there
>any really big parts that can be separated and developed independently?..
>  
>
Completely agree with that!

-Andy

>Konstantin
>
>From: "Leo Sutic" <leo.sutic@inspireinfrastructure.com>
>  
>
>>    
>>
>>>From: Gianugo Rabellino [mailto:gianugo@apache.org]
>>>
>>>Berin Loritsch wrote:
>>>
>>>      
>>>
>>>>We should split Cocoon into core development and component
>>>>        
>>>>
>>>development
>>>      
>>>
>>>>efforts, much like Avalon does with Framework and Excalibur.  That
>>>>will allow the components to be packaged in jars that serve
>>>>        
>>>>
>>>a similar
>>>      
>>>
>>>>purpose.
>>>>        
>>>>
>>>Yes, +1, go for it, hippy-ya-ye-o! This is badly needed.
>>>
>>>The problem is how to split actually. Based on functionality (i.e
>>>cocoon-sql.jar, cocoon-xmldb.jar, cocoon-ldap.jar), by Cocoon role
>>>(cocoon-generators.jar, cocoon-actions.jar), by status
>>>(cocoon-stable.jar, cocoon-scratchpad.jar, cocoon-beta.jar)
>>>or by what?
>>>      
>>>
>>By functionality and status:
>>
>>cocoon-sql.jar
>>cocoon-sql-scratchpad.jar
>>cocoon.jar
>>cocoon-scratchpad.jar
>>.
>>.
>>.
>>
>>I agree, it is a big job... But *badly* needed.
>>
>>/LS
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>>For additional commands, email: cocoon-dev-help@xml.apache.org
>>
>>    
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>  
>




---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message