cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <reinh...@apache.org>
Subject Re: Roadmap for Cocoon Blocks
Date Wed, 12 Oct 2005 04:52:20 GMT
Vadim Gritsenko wrote:
> Reinhard Poetz wrote:
> 
>>
>> So here is the roadmap and let's discuss it "officially" on the 
>> mailing list:
> 
> 
> I don't recall that m2 will be ready when 2.2 is out. If m2 is not 
> ready, it should not delay the release. So, I suggest slight change of 
> plan:
> 
>> - Cocoon 2.2 will not use OSGi but will support blocks as far as 
>> possible:
>>    - blocks protocol (= sitemap blocks)
>>    - a block gets its own component manager that contains all local 
>>      components
>>      and gets the block component managers of all wired blocks as parent.
>>    - blocks are distributed as binaries
>>    - blocks are *not* spread over different directories during deployment
>>    - a block can contain classes in [block]/BLOCK-INF/classes that are 
>>      added
>>      to the context classloader
>>    --> this means that everything, that real blocks promise, works 
>>        except the
>>        shielding of Java classes.
> 
> 
> 
> - Cocoon 2.3
>      - we use M2 as build and deployment tool (needs some special M2 
> plug-ins
>        for the deployment part)
> 

I understand that you don't want to base Cocoon on an unstable M2 release, but 
what's the alternative for 2.2? Ant? Maven 1?

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

Mime
View raw message