cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Hochsteger <>
Subject Re: [RT] a simple release plan
Date Fri, 17 Mar 2006 09:59:45 GMT

Daniel Fagerstrom wrote:
> Ralph Goers skrev:
>> Andrew Savory wrote:
>>> Hi,
>>> Ralph Goers wrote:
>>>> 1. I'm pretty sure all the blocks have not been mavenized.
>>> Is there a list of blocks to mavenise anywhere, with instructions of 
>>> how to do it? I don't mind helping with this.
>> The easy way to tell I suppose is to check out trunk. There are a 
>> bunch of cocoon-whatever directories. Compare that list with what is 
>> in src/blocks in 2.1.  I believe the instructions are in README.m10n.txt.
> Actually all the trunk blocks 
> was Mavenized once. Then 
> two things happened:
> 1) We decided to change to change directory structure to something that 
> followed the Maven standard, and that had some other advantages: 
> All 
> blocks with the new structure are moved to the trunk.
> 2) We changed group id from apache-cocoon to org.apache.cocoon (in 
> trunk). As the later is the recomended structure for M2.
> Most of the blocks in 
> would probably build again just by fixing the group id.
> It would of course be nice to switch all to the new directory structure, 
> but that can be done one block at the time when someone feel the itch.

Is there something that persons without SVN access can help with?
The instructions for the m10n of Cocoon Blocks require SVN access for 
moving directories and files.

Nevertheless I'd be glad to help by providing patches via Jira, if 
somebody could tell me what might be doable for me.

I already was able to build the trunk with Maven and run the Welcome 
page - but without samples so far.


> /Daniel



View raw message