cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <va...@reverycodes.com>
Subject Re: [VOTE] green light for flattening repo structure in trunk
Date Thu, 05 Jan 2006 18:00:00 GMT
Antonio Gallardo wrote:
> Jorg Heymans wrote:
> 
>> Vadim Gritsenko wrote:
>>  
>>> Jorg Heymans wrote:
>>>   
>>>> [ +1 ] flatten the structure and pave the way for a 2.2 release
>>>
>>> Minor point: does it have to be 'cocoon-core', 'cocoon-webapp',
>>> 'cocoon-<blockname>'; could it be 'core', 'webapp', 'block-<blockname>'?
>>> Not sure it will be easy to navigate among all those 'cocoon-foo's :)
>>>   
>>
>> Matching the directory name with the artifactId is recommended practice.
>> I can't exactly remember the benefits, but i know it saves extra
>> configuration in reactor builds eg when using continuum.
>>  
>>
> Should not be due name collision. ie: a core.jar released in another 
> project?
> Yes, I will prefer to keep a prefixed name as cocoon-core.jar. No matter 
> where we find this file, his names states it is the cocoon core.


I was talking about directory name only. cocoon-core.jar is fine.

Vadim


Mime
View raw message