cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <>
Subject Re: Reduce the references to SNAPSHOTs
Date Fri, 11 Apr 2008 06:06:49 GMT
Reinhard Poetz wrote:
> Vadim Gritsenko wrote:
>> On Apr 10, 2008, at 4:01 PM, Carsten Ziegeler wrote:
>>> Vadim Gritsenko wrote:
>>>> On Apr 10, 2008, at 3:31 AM, Carsten Ziegeler wrote:
>>>>> Hi,
>>>>> as we plan to have independent releases of all the blocks, the core 
>>>>> modules etc. we should reduce the number of dependencies refering 
>>>>> to snapshots to a minimum.
>>>>> Especially for the parent poms and references to apis - there is no 
>>>>> need to always release all parent poms, the api etc. just to fix a 
>>>>> bug in the impl. And if we refer to released versions from within 
>>>>> the poms, building Cocoon or parts of Cocoon gets much much easier.
>>>>> (And I think we already discussed this nearly a year ago and agreed 
>>>>> to that :) )
>>>> Will there still be a way to somehow build "all trunk" versions in 
>>>> one command? Like today's 'clean install'?
>>> In fact it will get easier! As you can check out a single module and 
>>> build it as all dependencies are deployed artifacts.
>> For a single module, I understand. But I meant trunk version of all 
>> blocks. If you are working on a cross-cut feature (and I tend to do 
>> this sometimes), you need to build all blocks from trunk, and if the 
>> only choice is do it by hand (50+ maven commands?) that would be too 
>> much work...
> You can still build all modules. The only difference is that if you have 
> API changes, you have to manually _change_ the version number to the 
> SNAPSHOT version.
Exactly - the build will still work - the final result of the build 
might be the webapp and this webapp should have the references to the 
latest and greatest snapshots.


Carsten Ziegeler

View raw message